3 ms·
This article would make a lot more sense if it was criticizing something more prevalent (e.g. JavaScript library churn, etc.) Point taken, but I see no reason
by zumu 6y ago
This article would make a lot more sense if it was criticizing something more prevalent (e.g. JavaScript library churn, etc.)
Point taken, but I see no reason to straw man Haskell and Rust. They have their uses and new successful features they explore get ported back into the boring languages. This is how technological development works. For a non-programming example, anti-lock brakes were used in Concorde jets before they were used in automobiles.
Also, one must consider that Java was a 'shiny' language once.
Honestly, if OP knows of many companies that are picking Haskell or Rust over the likes Java or Golang, please post links. I'll happily apply.
- ncmncm 6y agoI was there. Java was never a shiny language. It was many things. It was, most particularly, a ticket out of the world of the Microsoft sharecropper, needing to learn a whole new Microsoft Framework every second year, and discovering over again each time all the shit that didn't work, that couldn't be made to do what it was for, and cobbled-together ways to get around it instead. I managed to never need to code on Microsoft until a bit around 2010, so missed the appeal. I was amazed to discover that, even in 2010, nobody who had coded for MS their whole lives knew any better than I did how to get an MS OS to do any sensible thing. I would ask, and they would start rooting, trying random things until something seemed to work. The idea of a documented, stable, standard library component that actually did what it said without crashing was an absolute revelation, but the opposite of every shiny thing imposed on them before.