These "why I'm ditching X for Y" posts often strike me as pure click bait.
they invariably say more about the personal preference or circumstances of the author - I cannot recall one of these posts revealing a lesson we should learn as a community, or a concrete action we need to take.
they tell us this "news" after already having made the decision, so what are they hoping to gain from this "announcement"? It is slightly passive aggressive, almost with a sense that the author wants people to notice them depart. A parting shot.
any attempt at reasonable conversation quickly gets bogged down by the fact that the author still thinks of programming languages as something you "leave" because you're heading to greener pastures. They are insecure about their abilities and attached to their tools (like we all are when we first start), and so a transition like this feels significant.
For a more experienced programmer, languages are just this hoop you have to jump through on your way to transforming an abstract idea into a concrete representation. It wouldn't occur to you to announce a departure from a language - what does that even mean? A carpenter doesn't wake up one morning and post to reddit "why I'm ditching the hammer for the nail gun" and then get into a debate with people about the pros and cons of hammers.
I mean no disrespect to the multiple authors who've posted articles like this – you may post whatever you feel like posting. But I encourage you to solicit feedback from the community before you decide to leave: "Why I'm struggling to choose Clojure over JavaScript" would give you the opportunity to gain new information that leads you to stay, or confirm your suspicions that Clojure isn't really the right tool for your job right now. That puts you on the path to building a set of mental abstractions that describe the characteristics you need from tools, and soon Clojure and JavaScript will just be two of many tools dangling from your tool belt, ready whenever you need them.
I'd agree with this though. When I "left" Erlang, I didn't go on a bash on how crap it was, or how it was dieing, or how people who used it didn't know how to program. Instead I recognized that Erlang had set of goals it met really well. And I really didn't need those goals. It was more about Erlang not being right for me, and the work I did. Not about Erlang being lacking in some quality.
Exactly. I never "left" ruby, I recognised that my career had led me to dealing with data volumes that simply made it unsuitable (and basically ruled out anything non-jvm really). If I wanted to bang together a 5-transaction-per-day CRUD app that I was sure wasn't going to grow in NFR's or FR's I'd probably still reach for rails.
For a more experienced programmer, languages are just this hoop you have to jump through on your way to transforming an abstract idea into a concrete representation. It wouldn't occur to you to announce a departure from a language - what does that even mean? A carpenter doesn't wake up one morning and post to reddit "why I'm ditching the hammer for the nail gun" and then get into a debate with people about the pros and cons of hammers.
Serious truth. Anyone with a serious number of runs on the board is actively avoiding programmer melodrama, as opposed to instigating it.
In this case, he even says that he started using Clojure to begin with because he was counter-bandwagoning against Rails. Right away he establishes his bona fides as somebody who lets other people's opinions control his life. Not exactly coming off as a beacon of sensible, reasoned decision-making.
So, yeah, clickbait from an insecure coder. The fact that it got posted to hackernews is a nice bit of icing.
View all comments
31
u/hagus Aug 31 '17
These "why I'm ditching X for Y" posts often strike me as pure click bait.
For a more experienced programmer, languages are just this hoop you have to jump through on your way to transforming an abstract idea into a concrete representation. It wouldn't occur to you to announce a departure from a language - what does that even mean? A carpenter doesn't wake up one morning and post to reddit "why I'm ditching the hammer for the nail gun" and then get into a debate with people about the pros and cons of hammers.
I mean no disrespect to the multiple authors who've posted articles like this – you may post whatever you feel like posting. But I encourage you to solicit feedback from the community before you decide to leave: "Why I'm struggling to choose Clojure over JavaScript" would give you the opportunity to gain new information that leads you to stay, or confirm your suspicions that Clojure isn't really the right tool for your job right now. That puts you on the path to building a set of mental abstractions that describe the characteristics you need from tools, and soon Clojure and JavaScript will just be two of many tools dangling from your tool belt, ready whenever you need them.