But that's not something with only approved microSD cards work with save games. The Switch will not write save game data to any microSD card, regardless of features/manufacturer/branding/royalty payments/whatever. It's just not a supported feature, at all.
The GGP comment makes it sound like Nintendo only supported proprietary microSD cards at launch. While they did sell and recommend their branded microSD cards, one could use any brand of microSD card with the system and have the same functionality.
> Crashes would be avoided by having every train know about the train ahead and behind, and unable to make any move which would cause a collision (ie. it is not allowed to slam the brakes on if there is a train right behind you).
You are assuming that a train will never have to suddenly stop. This will never fly in the real world. Even if you consider a completely closed railway system with no possibility of external obstructions, there are many kinds of failure that would cause modern trains to apply emergency breaks due to fail-safe designs.
If you remove the bit about not allowing to slam on the breaks, then you just described SelTrac. Even the first version used on the Vancouver SkyTrain (opened in the 80s) is capable of running trains closer than braking distance from what I remember reading. I don't believe it is actually enabled on many SelTrac systems though, because you still need to have safety margins. There is always the possibility that the train in front may decelerate at a rate higher than its emergency braking rate, like if it derailed or collided with external obstructions.
Qt 5.15 at this point has been out for 4 years, already out of "normal" commercial LTS and will reach the end of extended commercial LTS next year. They don't have any incentive to do this kind of change.
I don't know if it is the case on Windows 11, but I have surely been bitten by CMD batch files using LF line endings. I don't remember the exact issue but it may have been the one bug affecting labels. [1]
Every once in a while, navigating with the keyboard in Explorer will cause the window thread to hang up in a busy loop and I have to kill it. I have no idea if this is an Explorer bug or caused by other stuff.
How does this compare to ANGLE or the MetalANGLE fork, assuming I have some renderer code that already works on both OpenGL 3.2 core profile and OpenGL ES 3.0? (We are already using ANGLE on Windows with the D3D11 backend and might consider using something similar to stop relying on the "deprecated" native OpenGL implementation on macOS.)
Railway is a different problem space than road vehicles. Trains run on fixed tracks, has long braking distance, are much heavier, and accidents can be much more devastating. While self-driving cars may use cameras, lidar and radar for detection and brake on sight, trains need to know exactly how far they are allowed to go and what speed restrictions are ahead in order to brake in time.
Traditional lineside signals and signs do give enough information to drive a train by a computer, but the rail industry has already chosen decades ago to integrate signalling and automation with the infrastructure, which is a completely different approach than today's self-driving cars. As a result, heavy rail and metro trains will not be "self-driving" in the same way as self-driving cars.
Now, if you say trams that run on streets, then possibly. Trams are often driven by sight and has stronger braking so it is possible to apply the same principles from self-driving cars. In fact, Siemens has been developing and testing one such tram. [1] Though I think the problem space is very similar to self-driving cars. There is no steering, but it still has to handle pedestrians and other road traffic.
What do you mean? From what I know it was bog-standard microSD(HC/XC) with the maximum supported speed being UHS-I with nothing proprietary.