"at those temperatures"
well, to a heat pump even -40° is still 230K, which is plenty of energy to move around and work with. It may be cold to you, but to a heat pump it's not.
justJanne
joined 1 year ago
Typical high speed tracks aren't shared with cargo trains. Frankfurt-Siegburg for example is only usable by high speed passenger trains.
And regarding the max speed, I'd suggest to look at china. The chinese railways run the Siemens Velaro CN, which is the local version of the Velaro D (DB Br407) at 380km/h in regular use.
I posted this comment already elsewhere in this thread, but lemme quote myself:
The ICE's max speed depends on model and variies from 250km/h to 300km/h. These speeds can be reached on:
- Hannover-Würzburg (280km/h)
- Mannheim-Stuttgart (280km/h)
- Oebisfelde-Berlin (250km/h)
- Siegburg-Frankfurt (300km/h)
- Köln-Düren (250km/h)
- Rastatt-Offenburg & Schliengen-Haltingen (250km/h)
- Nürnberg-Ingolstadt (300km/h)
- Ebensfeld-Leipzig/Halle (300km/h)
- Wendlingen-Ulm (250km/h)
There are more of these tracks currently under construction:
- Stuttgart-Wendlingen (250km/h)
- Bashaide-Rastatt (250km/h)
And many more are currently in the planning stage:
- Hamm-Bielefeld (300km/h)
- Oebisfelde-Berlin (300km/h)
- Ulm-Augsburg (300km/h)
- Gelnhausen-Fulda (250km/h)
- Frankfurt-Mannhein (300km/h)
- Bielefeld-Hannover (300km/h)
- Nürnberg-Würzburg (300km/h)
No, driving a moving truck (that's small enough to not full under the separate speed limit for trucks) at 200km/h is insane. Seen that before ^^
The ICE's max speed depends on model and variies from 250km/h to 300km/h. These speeds can be reached on:
- Hannover-Würzburg (280km/h)
- Mannheim-Stuttgart (280km/h)
- Oebisfelde-Berlin (250km/h)
- Siegburg-Frankfurt (300km/h)
- Köln-Düren (250km/h)
- Rastatt-Offenburg & Schliengen-Haltingen (250km/h)
- Nürnberg-Ingolstadt (300km/h)
- Ebensfeld-Leipzig/Halle (300km/h)
- Wendlingen-Ulm (250km/h)
There are more of these tracks currently under construction:
- Stuttgart-Wendlingen (250km/h)
- Bashaide-Rastatt (250km/h)
And many more are currently in the planning stage:
- Hamm-Bielefeld (300km/h)
- Oebisfelde-Berlin (300km/h)
- Ulm-Augsburg (300km/h)
- Gelnhausen-Fulda (250km/h)
- Frankfurt-Mannhein (300km/h)
- Bielefeld-Hannover (300km/h)
- Nürnberg-Würzburg (300km/h)
Often enough, the old code is so badly intertwined that it's impossible to actually test. Those are the moments where all you can do is nuke it from orbit.
The neat part about the fediverse is that no matter how badly behaved a dev may be, there'll be enough people to fix their behaviour and work around it. Look at mastodon, gorgon made a few questionable choices but glitch and all the other forks work around it and enough community servers exist that you could block mastodon.social and never miss a thing.
Just like with Lemmy there's already kbin and countless other alternatives that all integrate with each other and enough community servers.
But with browsers that's stopped being a thing a long time ago as the modern web is far too complex for small groups of indie devs to make their own browsers.
Yeah, I'm spending thousands of dollars on a single lens to get rid of chromatic aberrations and yet when I game, I'm somehow supposed to like that very same thing, emulated badly?
There's no provider that's going to be more safe than Hetzner, tbh.
If a provider doesn't comply, you'll just get special services raiding their DCs instead.
And if you switch to a VPS provider, you're even more exposed.
Set up CAA with proper restrictions, enforce CT for your clients and use proper full disk encryption to prevent them from placing implants on your server itself.
It would be, if you use macOS on an intel CPU with an AMD GPU.
But porting it to an entirely different CPU and GPU architecture with entirely different graphics API (Metal) makes no sense whatsoever.
Honestly, with high quality USB A plugs you could feel the logo on the side that was "up", and if you knew which side your motherboard or front panel considered "up", it'd be easy to always plug devices in correctly.
Just that the vast majority of manufacturers stopped caring relatively early on, which meant you couldn't rely on it anymore.
Sadly even Resolve Studio doesn't support h264 all-intra as used in Sony's XAVC-I and XAVC-S-I on Linux, which sucks.
With XAVC-I CineEI Slog footage the metadata is enough that Resolve treats it as Raw (in fact, it's more flexible than braw). So losing this functionality really hurts.