While the "BBM" tends to work alone and be frustrated at artiface at every corner, when you get a few or more working together, some really great things can come together. I've experienced that firsthand.
I might be in the minority here, but "fighting unfamiliar syntax" seems like a lazy argument to me. I've played around with many languages, and after getting used to the first non-c family syntax (in my case, Scheme) it never bothered me anymore.
There are valuable lessons I've learned from other languages and I don't think I could have learned them if I would have stayed in the language I was comfortable in at the time. It's much more difficult (in my mind) to try novelty when you have ingrained habits already.
I'm not so sure. I started (technically) with C++ and Java in miscellaneous summer camps and an independent-study highschool class, but my first serious course in a language (instead of just toy problems + messing around) was in Racket... I got the hang of it during the class, but I couldn't hold onto it the way C-family syntax just stuck, and when I last tried to pick up something Lisp-family a few months ago (Common Lisp) it was like I'd never seen Racket.
Unless that actually is "ingrained habits," I suppose, but in that case I had the habits before I ever hit college or knew that other syntaxes existed.
Indeed. Syntax is not an issue beyond your first exposure to a non-C family syntax language (and come to think of it, I learned programming with Basic, so I'm not even sure the C-like syntax thing even applies in the first place).
well for one, it's being used in the industry quite a lot. Citi, Walmart, Amazon, CapitalOne, Facebook, and Spotify are just some of the names from this list.
I'll agree that clojure doesn't enforce control of side-effects. But with the recent work on clojure.spec, your first complaint has become (even more of) an asset.
> Other Nevada solar companies with higher cost structures than SolarCity are expected to collectively lay off thousands of additional Nevadans in the coming months.
One thing I've noticed is depending on how your code is being compiled/transpiled, having smaller defn's over them being nested in a let can lead to better performance since inlining becomes an easier problem.
This is particularly true in clojure, since it's being compiled to java byte-code, and the jvm has a few default settings for how deep it'll look into the call tree for inlining. See https://www.youtube.com/watch?v=0tUrbf6Uzu8 for a talk that mentions this.
I've noticed the complete opposite. There's less of an emphasis on unit tests, but that's because the nature of FP enables you to need less of them. Instead of needing to check (at least as often) if objects behave correctly, you can write the few tests necessary to give you some regression abilities later on.
I've noticed a huge emphasis on testing the sytem, specifically through means of generative/property-based testing.
I have tried it and it's not horrible. The difficulty is that the chrome is styled one way, and the text inside the editors is styled another way. And neither of them are quite able to style everything!
I found the dark themes to look great with certain, staged screenshots. But then when you use it, the scrollbars are blaring white. Or the bar that shows your code blocks can't be styled (controlled by the OS). So you wind up with a mostly dark theme that has 2 or 3 blaring, ugly, mismatched elements that defeat the purpose.
Styling the editor window is something I've spend days tediously trying to tweak a nice pastel color pallet (that pretty much every app with a dark theme uses). But all the included ones are bright neon colors or just radically weird color choices. I've been able to get my code window 95% the way I'd want, but then all of the other windows like the explorer or the console don't match! The settings are all over the place and sometimes take a restart of Eclipse to if you got the right setting or not.
Basically I just gave up with the dark theme because it seems there's no way to get it consistent.
As someone that suffers from mental illness (depression), it's not completely off to mark to say that it isn't all bad--I seem to do better than peers in many creative endeavors--but I would immediately give up the benefit it gives for the freedom of a more stable mind. I wouldn't have a second thought.
I couldn't help but notice that quote, either. I wonder why the author found it necessary to put that in on an article about the pixels of the Apple Watch? I don't see that information doing much besides inciting a flame war.
It's a footnote. I guess the author is going for a "stream of consciousness" around Apple watch pixels. (Don't get me wrong, I don't think this is a positive contribution to the article)
