divingdragon

Really, as an East Asian language user the rest of the comments here make me want to scream.

UK ring circuits are typically protected by 30A or 32A circuit breakers.

I use the rule

    ||youtube.com/shorts/*$uritransform=/shorts\/(.*)/watch\/\$1/`

in uBlock Origin.

(Except that it doesn't work if you click on a short from YouTube's interface - it loads with JavaScript which bypasses the redirection.)

> They did this to micro sd cards on the first switch.

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.

> 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.

There is an official way to completely disable and remove Computrace (which I did on my T480), but I don't remember anything that allowed removing ME.

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 do this all the time.

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.

On Linux you can use `lsusb` to get a cleaner list of all connected USB devices.

You can try KiCad.

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.)

I would rather have my program hard crash on unexpected null than to have it silently ignore potential logic errors. I have never used a language with nil punning, but to me Option<T> still feels to be the best approach.