> Well, they could add speakers that make vroom-vroom noises.
And you could have typed this comment into notepad and saved it on a file on your desktop, but instead you shared it with a world that considers it irrelevant.
Not quite. Originally, the tighter length limits were intended to give trucks a disadvantage compared to freight trains. But engine technology caught up and more efficient smaller engines negated that limitation.
Not really. A regular truck & trailer is way too big to fit in space-constrained city centers. When it gets really tight they'll just send a box truck, often with a trailer they can leave behind outside the city center for some extra capacity when it's a multi-stop trip [0]. The fancy ones even have doors in the front of the trailer, making it quite easy to move freight from the trailer into the box truck itself.
On the other hand, the highway infrastructure has plenty of space for large trucks. If the roads to & from the main highway network can handle it, some countries will give you permits for all sorts of fancy combinations[1] up to 83 ft long. Considering that it'll still be pulled with a regular cab-over truck, that's a lot of space for freight. They are now even trialing the "Super EcoCombi", which is essentially two full semi-trailers[2], for a total of 105 ft!
Well, there's libraries like this one, which is the point here.
And even in JS, Temporal won't be available broadly for a good while yet (it will probably be rolling out in Firefox in a couple of months' time, but in Safari it's still behind a feature flag, and I don't think there's even a feature-flagged implementation for Chrome yet). In the meantime, it makes sense to use a polyfill — again a library.
By all means choose your dependencies wisely, but the point I'm trying to make is that very often a sensible use of dependencies will reduce your technical debt, and attempting to use bad approaches to complex topics just because they're built into the standard library will cause so many problems down the line.
I fully agree with that. Just a bit disappointed that Python is not even considering to fix/replace it's problematic datetime library (as far as I know). Excellent third-party library is good, but an excellent standard library is even better!
In Temporal's case, it takes significant inspiration from several existing datetime libraries in Javascript. Those were all stepping stones (among others) that led to Temporal.
