One point not covered in the SE post is that aviation engines are designed for a different and more demanding regime than auto engines. Aviation piston engines are used at or near 100% power for minutes, and 60% or more power for periods of hours.
Sorry, I don't see any place where the difference in operating conditions is addressed. No auto engine is designed to operate at more than 60% rated power continuously.
I've used Unix since 1978 and in my career have developed on and for Windows, Unix/Linux and Mac, though Unix/Linux is what I prefer because I think it's a better environment for programming. I recently bought a mid-range laptop which came with Windows 11 and I immediately installed Linux Mint as a dual-boot. I don't usually boot into Mint as I use Windows to play Steam games and I have another laptop where I work. I _do_ run Windows in airplane mode to inhibit all the automatic install/upgrade action that, in the past, destroyed my dual-boot setup. If that ever happens I just trash Windows and install Mint as a standalone.
Everything that doesn't need to be secure is in gitlab.com. When I used github.com I started a repository that I called "etudes" which were code and explanatory notes that went into a separate wiki repository. I used etudes for notes to myself and larger multipart explanations for others. After switching to gitlab.com, which doesn't really do wikis, I amalgamated code and notes into one repository and that works better.
For more secure information that I want to be more portable I use tiddlywiki on a USB stick.
Testing _your codebase_ written in Rust and C++ is really the only way to answer your question. There are many factors beside raw speed that should be considered when choosing a language. If speed were the only consideration we would all be writing code in assembler.
I don't fight it. I recently bought a new laptop that came installed with 11. I installed Linux Mint alongside 11. I only use 11 to play steam games and I always boot into airplane mode, so never get annoyed with Microsoft nagging, never get an update that destroys my dual boot arrangement, etc.
I would like to test the site, but I'm not going to create an account just to test. If I test it and like it, maybe I would not have a problem creating an account, so why not move the "create an account" step to later in the process?
Absolutely, we understand your perspective. The option to create an account upfront was initially available, but due to a large volume of users, we've temporarily disabled it.
> The option to create an account upfront was initially available
It's still there!? I _won't_ create an account for anything until I can road-test it and see if it offers anything beyond that available in my current toolset.
Or you could just wait a while. Things move fast in this computing racket.
In 1978, the Cray-1 supercomputer cost $7 million, weighed 10,500 pounds and had a 115 kilowatt power supply. It was, by far, the fastest computer in the world. The Raspberry Pi costs around $70 (CPU board, case, power supply, SD Card), weighs a few ounces, uses a five watt power supply and is more than 4.5 times faster than the Cray 1.
https://m.youtube.com/watch?v=w3_0x6oaDmI&pp=ygUaZWxlY3Ryb25...
https://m.youtube.com/watch?v=LkH2r-sNjQs&pp=ygUaZWxlY3Ryb25...