>>615
>For a large portion of usecases Linux is more than enough.
Then why aren't they using Linux over Windows?
>What are you going to do next, mention flat earth out of nowhere or some shit?
Anon, claiming that the only reason that Windows is being used in governmental and education facilities is because the government has made backroom deals with Microsoft is literally the definition of a conspiracy:
"Conspiracy: a secret plan by a group to do something unlawful or harmful"
>No, but if people weren't manipulable and operated completely rationally and chose the most optimal products, the world would be much different.
I agree. Alas, the majority of the world shall for the next foreseeable future remain inhabited by normalfags.
>>617
In my anecdotal experience, there are three major reasons why businesses and schools rather make use of Windows over Linux:
1. A network of Windows PCs is easier to configure by people who have no experience managing networks.
2. Microsoft will deal with ensuring your machines are always up-to-date and secure against exploits, as opposed to having to do so yourself.
3. If you have an issue that you cannot resolve yourself, you can call Microsoft for support.
In other words, it is a service issue. It's not the OS, it's the service that Microsoft provides besides the OS.
>>618
>do you really think that copying the entire compiler and adding one feature (aka forking) is allowed?
Yes. That's precisely what it means. If you do not believe me, you're more than welcome to create an issue over at
https://github.com/rust-lang/rust and ask if you are allowed to fork the entire or specific parts of the project.
>Do not accuse me of random shit you crazy.
I asked you three questions:
>what parts of rust are not free?
>are you not allowed to fork any part of the project?
>are you being forced to pay a free for using any part of the project?
You then proceeded to accuse me of not being aware of the two different meanings behind the term "free" (not freedom) and ignored 2/3 questions.
>this simply doesnt work at runtime, do you even program?
Do you even know what you're talking about? The runtime doesn't care about the code it's executing, because it assumes the code is correct.
It is the compiler that ensures that the executable code it is compiling your Rust code into cannot cause a memory bug of any type.
Once again: you literally cannot write a program that causes a memory bug in Rust unless you explicitly label a part of your code as "unsafe".
>the rust environment is proprietary
How is it proprietary? Seriously, show a single example of any part of the Rust project that is proprietary and I will gladly concede.