2 ms·
Nothing really disappears, the question is how strong the ecosystem is in ten years and how good the support for the code you write today. Rust will not go awa
by uecker 2y ago
Nothing really disappears, the question is how strong the ecosystem is in ten years and how good the support for the code you write today. Rust will not go away but I doubt that the code written today still works without hassle or that all the 1000 crates it depends on still exist. That there are dark corners using C89 or K&R is not a weakness, it demonstrates how strong the C ecosystem is. If you write something in Zig or Rust now, you need to realize that in 10 years it might also be considered ugly legacy code, even if you think it is shiny modern code today. The question is then if it is as easy as using "gcc -std=c89" to work with it.
- ay 2y agoA piece of anecdata: my Rust code from 8 years ago still compiles fine, though compiler complains about not having the defined edition set.
- uecker 2y agoNews such as this one do not build confidence though: https://internals.rust-lang.org/t/type-inference-breakage-in-1-80-has-not-been-handled-well/21374 https://internals.rust-lang.org/t/type-inference-breakage-in...
- ay 2y agoAh. Apparently I didn’t use that crate, so happily missed that footgun, thanks for the info! That is an unfortunate case. Though I suspect it’s fair to say the entire settlement is built of glass houses here :-) https://news.ycombinator.com/item?id=43798312 https://news.ycombinator.com/item?id=43798312 I suppose if one wants absolutely no surprises, they will need to lock the entire toolchain as well, regardless of the language…
- uecker 2y agoMaybe, but this GCC change would affect only code that is already broken and then there is even a compiler flag to fix it.