bazelisk VS reactos

Finally someone mentioned Bazel which would be my primary choice as well given how intuitive, easy to use or extend. Handles very large codebases easily. Go with Bazelisk as launcher: https://github.com/bazelbuild/bazelisk

I have to take a complete stab in the dark as GP's comment is deleted, but I think they may have referenced bazelisk (as that fits the context of version pinning).

Bazel's single-binary distribution brings its own JVM, it has less dependencies than gn.

Most people use Bazelisk: https://github.com/bazelbuild/bazelisk

Now we have the minimum to build "nothing" with Bazel. So you need to install Bazel'cli. But I recommend you to install bazelisk, it will take care of installing the latest (or the project specific) version of Bazel. In the following articles, codes when you'll see bazel ... it could also be replaced by bazelisk ... (in fact some packaging of Bazel installs bazelisk and create an alias). For this step use your favorite way (distribution package system, download from github, homebrew,...).

https://reactos.org/ implement some of the windows API

You can use Rufus: https://rufus.ie/en/

To modify the ISO to turn off hardware check and TPM support for Windows 11 to install it on an unsupported PC.

https://github.com/pbatard/rufus/wiki/FAQ#user-content-Help_...

Besides Linux and BSD Unix there is: https://reactos.org/ https://aros.sourceforge.io/ https://www.haiku-os.org/ and https://www.arcanoae.com/arcaos/

I know some third-world nations still use DOS and the BORLAND DOS compilers because people donate old computers to their nations.

With the right OS, old computers are still usable. Please don't throw them away, e-cycle them so they get used by poor nations that cannot afford new PCs.

ReactOS is sometimes very disappointing. Take the issue with toolbar icons, for example. Toolbar icons in at least Office 97, Office 2000 and Visual Basic 6 were affected, as was some game [0]. Microsoft Office is a complex Win32 application, making it a good guinea pig for testing compatibility. And yet, this was fixed a few months ago, and the Office bug was reported in 2016 [1]. The bug with no text wrapping for tray balloons is also an embarrassing thing to have lingering for years (I assume it was like this since the balloons were first implemented in ReactOS).

Does the world really need a buggy Windows Server 2003 reimplementation? I think the efforts of the development team could be better spent elsewhere.

[0]: https://github.com/reactos/reactos/pull/5227

[1]: https://jira.reactos.org/browse/CORE-12377

Anyone tried ReactOS recently? Supposed to be a clean-room FOSS Windows NT compatible OS.

https://reactos.org/

It's still on my TODO. Mostly cause my parents want XP back.

> It's whitespace. There's wayyyy too much god damn whitespace in modern UIs, and it's awful.

I wanted to see how LibreOffice would compare on my netbook, and frankly it's better than the new Word, but still "worse" than the old version: https://i.imgur.com/cWGYh3M.png

That said, at least LibreOffice lets you have your custom themes and actually offers a variety of different interface layouts, which I think is a nice touch: https://wiki.documentfoundation.org/Videos/User_interface

> Windows 7 with the Classic theme (which really was just a slight evolution over Win2K) was peak UI/UX, and you'll never change my mind. It's been downhill ever since, getting worse and worse with each generation.

To be honest, I'm inclined to agree with this. That's also why I rather enjoyed the Redmond theme even in *nix distros. There's just something so very usable about the old Windows look and more modern attempts, such as SerenityOS https://serenityos.org/ and even ReactOS https://reactos.org/