3 ms·
This is the way it’s always been though. First it was Java, then Ruby, then Clojure, then Go, then Node, and now Rust. As languages get popular, multiple projec
by mbreese 5y ago
This is the way it’s always been though. First it was Java, then Ruby, then Clojure, then Go, then Node, and now Rust. As languages get popular, multiple projects get rewritten in them. At first it’s a novelty, but it is often useful to see what the strengths and weaknesses are of a language to implement an existing project. Eventually, it becomes annoying to have “written in X” attached to articles and links, but soon, that will diminish.
The only time when I think it’s really appropriate for a mature language is when the language itself is a feature. But that is really rare for that to be the case.
Other languages (eg Python, Haskell and Erlang) are in the mix too, but more evenly distributed and less fad-ish.
This is just part of the hype cycle of languages. I’m not saying Rust is only a fad, but we are definitely in that part of the cycle for Rust.
- dgb23 5y agoI think it matters to communicate the language/tech in an open source project specifically.
- AnIdiotOnTheNet 5y ago> As languages get popular, multiple projects get rewritten in them. Lately I've been thinking, it's kind of funny how the modern development mindset is so all about code reuse what with its giant dependency graphs and reliance on cross-platform frameworks; and yet the favorite sport is still rewriting perfectly good applications in the new hotness.
- pjmlp 5y agoBecause as fashion driven industry that is the only way many will get experience on language X down on their CV or favourite source code repository for head hunters.