

And it shouldn’t


And it shouldn’t


n, n, n, nn, nnnnnnnnnnnnnnnnnnn, n, nn, n, n,n …


Did anyone actually read this post and the links? None of these links confirm what this post claims
For what it is, a chat app, Teams should run without any problems on machines from 2005
Like every other Microssoft product Windows is not actually intended for usage
The cli because it is consistent everywhere and has all fearures


Ammm actually… ☝️🤓 most Rust evengalists claim that Rust prevents you from writing bugs


Sales already sold the kitten for one year ago
All people say it. Tremendous code. All the experts said “No, generating formatted random text is not working code” but we did it.
There is a third brother nobody ever even mentions … He is also named after an island


Bold of you to assume they will respect it
You dont. Thats why you write code that explains itself. For higher level info you write documentation.


Microsoft be like



I once heard that a major problem is that you have to disable or work around Rusts safety features once you write hardware interfacing code like a os kernel


Why would you say that Rust is made for low level hardware interfacing? I am generally curious.


All these concepts like optional markupfiles, identifying objects by id, creating objects from markupfiles and WYSIWG editors also exist for the xaml(which is a Dsl) and C++ stack. Its just that microsofts usage and tools are crap like every other microsoft software


Thats how every GUI which is not immediate mode works. Are there any examples where it works different?
If it works, it works


Zig is a modern C. Rust is a (modern) alternative to C++. So two different languages can exist alongside each other, just like C and C++.
My source is that I made it the f*ck up