C and its descendants does have a somewhat "broken" case statement. Pascal's was much less error prone. Putting in semicolons won't make the language NOT term

C and its descendants does have a somewhat "broken" case statement. Pascal's was much less error prone. Putting in semicolons won't make the language NOT terminate a statement if you split a line in the wrong spot. (I suppose one solution would be just to put everything on one giant line, and separate the statements with semis, but, YUCK) Repetitive boilerplate should indeed be pushed down a level or two in any language, so the top of your program reads in terms of the business logic / problem space, not a bunch of code management noise. This is less traumatic if your functions have actual documentation for an IDE to display when a symbol is clicked on, rather than buying into the "self documenting" fairy tale. However, 2 spaces per level isn't visually very much. I don't need to nest things so deeply that I begrudge a few spaces per level. - - - - Static OOP was the shizzle back in the 80s (when we were learning about clones, often bad clones, of Simula 67). The last 10 years or so, though, I have really started to appreciate much (if not all) of what Lisp offered back in the day. Javascript is an acceptable Lisp.