At least go through the effort to screenshot the whole comic next time
Funny Comics
A space for sharing funny comics and cartoons.
Looks better uncropped and has the artist's signature.
Bad crop and cuts off artist signature
If you think that anyone can write CSS correctly that's pixel perfect, responsive and portable across browsers, it means you've never been done enough front end work.
Web Standards and CSS is hard, much like Haskell and the analogy of jazz: extremely versatile and flexible but pretty hard to appreciate the beauty of it if you're a beginner
Bad crops... Bad crops everywhere! What is Ruby?!! Japanese Noh music? Simple sounding, Rigorously stuck in it's ways, but incredible complex underneath?
I'm not an actual programmer but I've dabbled in enough languages to be able to get a gist of what basic code does - or at the very least, quickly understand the syntax the language uses.
LISP, however...what the fuck is going on here?
It's confusing because lisp isn't a language, it's a text syntax for trees. You don't write lisp code, you directly write the abstract syntax tree that most language are converted into.
Various flavors of lisp offer a selection of macros and functions to create a useful programming system. Thats how you get Racket (more functional style), Common Lisp (with object system for more OOP style), or Clojure (with other kinds of brackets and free Java built in). Plus the hundreds of others.
Consider something like a loop or an if-else ladder. In a c-like language:
if (condition == test) { call_function(x,2,"aaaa"); }
else if (condition < test) { print("woah"); }
else { throw new Error(); }
In a lisp-like language:
(if (eq condition test) (call-function x 2 "aaaa")
(if (lt condition test) (print "woah")
(throw (Error new))))
In lisp, "if" is a function that takes 3 params: the condition, the do-if-true block, and the do-if-false block. In c-like, "if" is an expresssion in the language, with a similar structure. Notice how the lisp structure is fully nested. I left off a pair of optional curly braces on the second line of the c version, but technically there's no "else if" construct (well, there is in some languages, but bear with me) but rather an "else {}" block which contains a second if-else expression. The lisp version makes this nesting explicit.
Other stuff like prefix notation for everything is optional (Clojure has infix operators and other kinds of braces) or you just get used to it (like open parens going in front of function names instead of after them.)