Unfortunately, he did not move to x64.

I wish there was something like RISC-V for CPU Peripherals.

A standard architecture and monitoring interfaces so that more OSes could be easily booted.

These exist. See SBI, BRS, etc. RISC-V standards.

Lots of effort actually goes into these.

Thank you

Virtio

Any Hope for HaikuOs + Winlibs. GDC would be greatly appreciated.

Nice one. It needs maintenance.

I agree.

I also hoped Arca Noae goes down this road, but they are still 32bit.

This is what we need, a better kernel, better Win32 API and less Microsoft.

The rest we can install with package managers and develop ourselves.

And WSL2 is good only for Podman and Rancher.

"everything you did on your PC but that it was a rushed"

Why it was rushed? without any respect to the consumers, especially when consumers did not want it!

This is a very dangerous situation and even more dangerous is the fact that now they take a step-by-step approach to reintroduce it.

The solutions are not practical.

In what way? Other than the cost of a 5 pack volume license.

It did mention that vendors may be willing to negotiate for single-machine licenses.

Congratulations!

I wished for an upgraded mingw64 toolchain, but it might be more difficult and take a bit longer.

The main problem for me is maintainability. There is a graveyard of FOSS because of hastily made hobby software that is not maintainable.

The recent Winamp fiasco is a textbook example.

What is the incentive to maintain something that is free (in both senses of that word)? Even if it is just out of the kindness of their heart, is that even a kind thing for them?

Most open source projects are people who have dumped their unfinished project online, but it's hard to know whether or not it is finished until you use it, or worse, use it for a long time and find the gaping holes.

And without being paid, there is the issue that the maintainer doesn't work on the important things, since there is a lack of (price) signal to state what to work on.

> Most open source projects are people who have dumped their unfinished project online, but it's hard to know whether or not it is finished until you use it, or worse, use it for a long time and find the gaping holes.

Mostly agree, but what should people expect when it's free? Arguably, there should not be any expectation of a "polished" product. If it is good, that's likely from community support, and general need.

> And without being paid, there is the issue that the maintainer doesn't work on the important things, since there is a lack of (price) signal to state what to work on.

After stumbling upon this thread and article, by itself, most might think there is nothing wrong with the statement, and that it makes some notable points. Upon reading up on the history involving other projects, however, it then comes across as bizarre in an hard to explain way.

Be that as it may, do agree that all FOSS projects have the right to receive donations or be financially supported to compensate and thank them for their work. It's up to the public how important they think supporting it is, and that part looks fair.

maintainability is for others and self.