• 0 Posts
  • 157 Comments
Joined 2 年前
cake
Cake day: 2023年7月16日

help-circle
  • The original code remains available under the original.

    Any proprietary code would have to be code that was added on top of that.

    You always have the ability to keep using the Own Source code. That is a freedom you have.

    If you decide that proprietary version is “better” and choose to use that, well that is a freedom you have. But now you have accepted a proprietary license. Your choice.


  • So, you had to choose between the code that was still Open Source and the code that was now proprietary.

    If you stick with the Open Source, what you describe does not happen.

    If you moved to the proprietary, well, there you are. You clearly decided that the new features were more important than it being Open Source.

    Remember, it is only the new features. All the old code remains as open as it ever was.


  • What could be the possible incentive to:

    1. move core utils to a closed license if you are a company

    2. for a Linux distro to choose that version over the already existing Open Source version

    Remember companies cannot take Open Source code bases closed. They can fork an Open Source project and close their fork. But all that means is that their “future” changes are not Open Source

    The original Open Source code still exists and we can all keep using it.

    For a real world example of companies not closing their userland, Apple still releases the source to their userland even though the BSD license does not require it.

    For a real world example of the community continuing on with the Open Source code and ignoring the closed fork, look at Valkey and Reddis.

    GNU is completely dominated by Red Hat. The alternatives, like uutils, are far LESS corporate.

    Fear and feelings over facts.







  • 32 bit Windows is probably no big loss. The real headline is this:

    “The *-windows-gnu targets currently do not have any dedicated target maintainers. We do not have a lot of expertise for this toolchain, and issues often aren’t fixed and cause problems in CI that we have a hard time to debug.”

    That means 64 bit Windows support as well. That is a pretty big deal. How is it possible that Microsoft uses Rust in Windows now and yet there are no Windows maintainers? Isn’t their new Edit written in Rust too?

    This is where is shake my head at corporate support. Microsoft has 200,000 employees. They cannot spare one for Rust?