Sure, here's 2 off the top of my head: Package management is a non-thing in SBCL. It just doesn't exist. Have fun downloading 6-to-12 year old zipballs. The basic HTTP server, hunchentoot IIRC, crashes after it serves its first request. Hope your favicon.ico was a good one!
Yeah, it's almost surely a case of remembering the handful of times when the clocks were inaccurate because they caused you trouble, while forgetting the hundreds of times when they worked correctly. They do work correctly most of the time, and the A division works even better than the B division, as you'd expect. (the opposite of what OP claimed.)
I, and many others I'm sure, would appreciate it if you would actually put some effort into your half-hearted America slams. All the subways I've been in, EU and US, have plenty of both ads and maps.
You must be one of those hipsters who lugs around a typewriter to cafes.
- They are very slow compared to digital.
- They aren't versatile, they can't display arbitrary information. Each message has to be crafted individually and fit in among the rest. Which makes it nice for station lines since there are a small number that never change. Anything else? Not so much.
- The noise is not intentional, it's more of a bug than a feature for sure. In a busy train station they change every minute or more so as an alerting mechanism it's near useless.
Ok, I know we like to dump on Americans with impunity, and I'm not even going to get into whether it's deserved or not, but have you driven in much of the rest of the world?
Where I work, one of the benefits of Clojure is precisely how concise and accessible storing densely layered business logic is. We're able to have a faith that the code does what it looks like that just isn't approachable in any other language I know of.
You must not be in SF or NYC. Python and Ruby (and even Node, to an extent) have supplanted Java as the language of fungible mass-market headcount du jour.
I and a few others in my workplace are Clojure beginners. It's really not hard to pick up once you suck it up and stop bitching about parentheses. I don't think the language owners are terribly concerned about picking up beginners though, for all it seems they may actually like Clojure's reputation as belonging to Serious Programmers.
My biggest beef is actually with all the lisp true believers who wax on about their moment of clarity when all the pieces fit together and they realized that the universe is written in lisp. So far for me, it's just code.
Is SBCL winning in anything? One of my acquaintances, a Lisp zealot, convinced me to jump in and make my next project in SBCL. Short story, it was a joke. Nobody seems to have done any serious work in SBCL in over a decade. Basic things are either completely missing or broken. Clojure I can at least make working software in. The fact that you are putting SBCL up there with Clojure makes me wonder if you've ever used SBCL.
JavaScript has commonly used 2 spaces for years before "StandardJS" (which is now out-of-date because certain es7 features necessitate line-terminating semicolons, but I digress).
CoffeeScript was a big catalyst, and I think Rails was as well, but it probably would have happened anyway. Of the languages I use regularly, the only ones for which 2 spaces is not accepted as normal are Python (which uses 4, probably because it was set in stone decades ago, before people even knew how to write code) and Go (whose auto-format uses tab characters, probably because Rob Pike is a stubborn prick).
Really, 4 spaces is an awful lot, unless your eyesight is failing.
Only with services like Instacart where they literally pay people to go and do your shopping for you. Real, end-to-end grocery services like FreshDirect do not.
From an American perspective who is familiar with that usage, it's not that great. And it really doesn't do justice to the actuality of the situation. "Lets" means "permits" or "allows", but this is an obligatory deal here.
I love how he characterizes what developers do as "just writing code" -- the whole article is basically a whinge: don't make me do ops, don't make me write tests, don't make me think about the problem, don't make me re-use existing solutions, don't make me pick the right tool for the job, don't make me use sustainable processes -- I just wanna "write code". Code is basically the poop that results after you digest the problem. The best code is as little code as possible, but this guy just wants to make code poop for a living. Sorry guy. Time to grow up.
Author doesn't understand the DevOps skillset. The average developer can hack things together, but they don't have an appreciation for operational principles. DevOps is actually higher on the totem pole than dev, because DevOps requires you to be skilled in both operations and dev. A traditional ops person couldn't cover for a dev, but neither could a regular, even "full stack" developer stand in for a sysadmin.
Really? You put a dozen people on the same _project_? I find it hard to believe that your project is so unique that A) requires 12 devs and B) is also deployable by all 12 of them (without relying on automation) in a way that doesn't throw off any of the other 12.