3 ms·
Yep, and everyone still uses all the stoftware written in C/++, and the stuff written in ruby/(and soon go/rust/...) doesn't even run anymore.
by ajsnigrutin 5y ago
Yep, and everyone still uses all the stoftware written in C/++, and the stuff written in ruby/(and soon go/rust/...) doesn't even run anymore.
- wongarsu 5y agoPlenty of people still use Ruby, there's a ruby project on the HN front page right now [1]. It just isn't mentioned anymore. The world pretty much runs on C, Java and C# but you won't hear about either, because what's normal isn't exciting. HN isn't a reflection of normalcy, it's a reflection of the unusual and the cutting edge. 1: https://news.ycombinator.com/item?id=28634831 https://news.ycombinator.com/item?id=28634831
- mywittyname 5y agoGetting old, forgotten C/C++ code running can be a job. It's really a matter of how well written the make files were and if one still has the original tool chain sitting around. C/++ code written for a paid, closed-source compiler can require a lot of changes to get running under something like GCC. Not sure how Ruby's backwards compatibility is, since I don't use it, but I have to imagine it's like most other scripting languages in that getting the correct major version is all you need.
- ajsnigrutin 5y agoI'm not talking about old, forgotten code. I'm saying that, every time, there is a "${old-existing-thing} in ${current-language-of-the-day}", people upvote it, start it on github, and continue using the old one, written in c/c++. A few months will go buy, and people will continue using mgba/visualboy/vbam or whatever was popular before.