No need for rewrite, just banning new codecs, etc. that aren't written in a memory safe language and migrating slowly.
-
-
There's so much churn that a lot of this problem will solve itself if rewrites of components are done in a safe lang.
1 reply 0 retweets 0 likes -
Maybe there wasn't a good low-level choice in 2008. Google made Dart and Go though... covering needs that were met.
1 reply 0 retweets 0 likes -
It would be nice if there were low-level safe languages other than Rust, perhaps choosing simplicity over performance.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @fugueish
IMO the biggest problem is that most people who want "low level" don't know or agree on what they mean by that...
1 reply 0 retweets 0 likes -
A plausible alternative to safe langs is safe impls of well-known unsafe langs (i.e. C).
2 replies 0 retweets 0 likes
For example you can use fat pointers carrying bounds info and a signature.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.