Re: Return Journey
Also, SpaceX is becoming expensive and inefficient now that it is the de facto NASA replacement
The googlification of SpaceX is eventually inevitable and inexorable if the competition disappears
12 publicly visible posts • joined 29 Sep 2021
Your mention of the device tree parser reminded me that on Windows, disabling the Microsoft Device Association Root Enumerator is reported to fix many Elden Ring microstutters...
I have no idea what that thing is actually doing in the background, but kernel interrupts being somehow involved would not surprise me
That's one thing that never makes sense to me (except from a company looting perspective)
Stock buybacks should only be allowed if management compensation is *not* tied to the performance of the stock, neither directly nor by explicit bonus metrics.
Otherwise you create an absolutely massive moral hazard. For a long term investor, it seems to me that any benefits pale in comparison to the hollowing out that clearly results over time because of this.
If you ask me, it would be kind of pointless to upgrade the OS on some embedded system on a 30 year old train with 20 more years of expected service life from Windows 3.11 to, say, Windows 11. Even without considering the ISA cards and such, there would be at least another major OS upgrade required to keep the OS supported anyway.
Although on the upside, an OS upgrade *would* create an opportunity to insert the DRM that bricks the trains if not serviced by the original manufacturer, allowing Siemens trains to keep up with Newag in innovative fleet monetization... sorry, I meant modernization, strategies. And you could always explain the intentionally-created issues away with the complexity of maintaining Windows 11!
Simplifying timezone database handling by introducing a compile time option to build a different database, one for normal use and one for historians that need actual accuracy?
What genius - now there are two databases to maintain! Ok, it's not so bad - you just have to run the full test suite twice, as well as making sure to have test cases that separate the differences. Uh... there *are* suitably complete test suites for something as important as this, yes? Especially with the sources obviously complicated by global compile flags that change the behaviour all over the place, and with the project goal of merging some of the timezones apparently touching quite old stuff with most every release, the expected results will also change with every release?