This could have been good news, however, Microsoft’s insistance on using AI, and general incompetence even without it, makes me very doubtful this will be successful.
They are going to try and replace C and C++ written by actual experts a few decades ago, with Rust written by idiots. Expect tons of logic bugs, and very little measurable difference in memory corruption.
Isn’t React technically safer for memory ? I was only talking about memory corruption, Rust’s actual main strength.
Don’t get me wrong, it is absolutely terrible that they shoved JavaScript in the start menu. It’s buggy as hell, but I don’t think it can ever segfault.
perhaps… i guess the single directional execution model would help to prevent memory leaks, and components would help keep things relatively contained… and also javascript in general avoids whole classes of c/c++ bugs… but it’s also incredibly slow. imo it’s just not something you should write core system components in
to be clear, it’s not react that’s the problem here: its execution model is an excellent way of structuring UI… but something as core as the start menu just really isn’t something you should fuck around with slow languages with
and also, that’s not to say that FOSS shouldn’t do it - they’re open, and thus something like react makes it easier for devs to write plugs and extend etc… but that’s not an engineering concern for windows: they don’t get the luxury of using extensibility as an excuse
This could have been good news, however, Microsoft’s insistance on using AI, and general incompetence even without it, makes me very doubtful this will be successful.
They are going to try and replace C and C++ written by actual experts a few decades ago, with Rust written by idiots. Expect tons of logic bugs, and very little measurable difference in memory corruption.
little measurable difference? the last time they rewrote something they replaced the start menu with fucking react
the difference will be measurable and enormous
Isn’t React technically safer for memory ? I was only talking about memory corruption, Rust’s actual main strength.
Don’t get me wrong, it is absolutely terrible that they shoved JavaScript in the start menu. It’s buggy as hell, but I don’t think it can ever segfault.
perhaps… i guess the single directional execution model would help to prevent memory leaks, and components would help keep things relatively contained… and also javascript in general avoids whole classes of c/c++ bugs… but it’s also incredibly slow. imo it’s just not something you should write core system components in
to be clear, it’s not react that’s the problem here: its execution model is an excellent way of structuring UI… but something as core as the start menu just really isn’t something you should fuck around with slow languages with
and also, that’s not to say that FOSS shouldn’t do it - they’re open, and thus something like react makes it easier for devs to write plugs and extend etc… but that’s not an engineering concern for windows: they don’t get the luxury of using extensibility as an excuse
All the black hats are going to have a field day uncovering all manner of zero-day exploits…
No no no you see, they’re using rust, which is a ‘safe’ language. That means it’s not possible to have security issues…