4 ms·
Hah, well, right. I just meant from a longevity standpoint. What stack can I use today that is and will continue to be well supported for 30+ years?
by shireboy 4y ago
Hah, well, right. I just meant from a longevity standpoint. What stack can I use today that is and will continue to be well supported for 30+ years?
- canon123456 4y ago
- jhugo 4y agoC, C++, probably Rust, various other relatively boring languages. If Node.js is even still used in 30 years it won't look anything like today's Node.js.
- djbusby 4y agoI've converted some legacy apps into, not a joke, PHP3. In like 2006-8. So, PHP3 still works this many years later (in VMs). Currently working to migrate to PHP7. It's just moving business data into and out of, in many cases still file based records (but maybe we can upscale to SQL). So, if you can read the COBOl and implement correctly in the next blessed language (with tests). Harder part is to meet the folks that can get you those gigs than actually doing the gigs.
- goodpoint 4y agoCome on, are you serious? COBOL is still being used exactly because it does not have a high-churn ecosystem. Same for C and C++. Of all languages, js is by far the most volatile.