1,000 karma · joined April 29, 2015
Apple does, Google doesn't!
Beyond a certain network-density of other modes of transport, there are simply better alternatives to cars (in most cases).
Cars by themselves are the most inefficient (cost, space, fuel, economically) and polluting mode of land-based transport we have.
I know, it's a completely different thing in the US, which is full of car centric infrastructure and other modes of transport are either absent (passenger trains) or often impossible or outright dangerous due to the sheer danger caused by a lack of proper infrastructure for pedestrians/cyclists, public education/general behavior (road rage, drivers' education, ...) or even impossible to cover by bike due to the distances caused by urban sprawl/a lack of density due to zoning laws.
https://caddyserver.com/docs/caddyfile/directives/encode#enc...
https://discourse.nixos.org/t/the-nixos-foundations-call-to-...
The tvix project itself is quite fascinating and worth a look. It reminds me a bit of the Gentoo times when Paludis came around and blew Portage's performance out of the water - but tvix seems to care more about compatibility with the existing ecosystem instead of being a competitor.
In Germany, until recently the costs for a residential parking spot were capped at strong 35€/year or so.
The actual "market value" of the equivalent space in cities is often around 4000-6000€/year.
Getting cars out of cities and using the space more efficiently for pedestrians, cyclists and public transport is not only a way to drastically improve safety and quality of life in cities, but also a smart economical choice (and no, building tunnels like Musk dreams of it, isn't the solution to this problem).
Cars were a failure and I believe we'd all be better off if they'd never been invented or at least hadn't been met with the enthusiasm of petrol-financed politicians that turned our cities, infrastructure, housing policies and everyday life into something that largely depends on cars.
Looking at cities like Paris, Barcelona or Amsterdam that broke the dominance of cars makes it clear, that the quality of our lives drastically improves by not leaning into a car-centric design.
The good thing about it: it's quite unlikely to happen again, as you've also pointed out: one can become quite aware of factors (corporate culture, fear of disappointing others, perfectionism, ...) which might contribute to the death spiral leading to it.
I also wonder about the energy footprint for heating that much water... My intuition screams "far too much to be a reasonable scalable alternative".
This encodes region-specific assumptions as part of the code logic.
This might even differ due to dialects/regional differences in pronouncation and will fail at latest when it comes to completely different languages (for which one doesn't even have to leave the US, given e.g. the huge Spanish speaking community).
I don't know whether Uber Eats is available in other countries than the US, but this would bite them in the ass as soon as they're expanding internationally.
This term seems to be reserved (with an often racist/classist connotation) for people from the global south.
[1] https://www.golem.de/news/origami-des-todes-ukraine-setzt-pa...
- die See (fem.), alt. das Meer (neutr.) - the sea (a saltwater ocean)
- der See (masc.) - the lake (an inland freshwater lake)
But then again, "das Meer" is sometimes used for freshwater lakes when connotated with some context, e.g. "das Schwäbische Meer" as an alternative name for "Lake Constance".
In an environment built on "traditional" SQL you'd have a history table, where you first and foremost would have to maintain records for those values: - ticket ID - time of state change - type of state change
But for the stats to be actually valuable, you might need additional history context (different per type), such as the user ID, the state, criticality, etc for which either an additional table per history type item type would be required or the data could be stored as serialized value with a metadata column of the history table. One requires complexity on the DB level, the other requires application level logic and slows down report generation tremendously.
Temporal tables to the rescue to remove all this complexity.
The full state of a ticket record including it's related entities at the given time of an UPDATE is fully preserved by the DB natively, so all you'd have to do to retrieve historic records at a given time is to append "AS OF $TIMESTAMP" to your query.
In the end, there's no need for extra history tables, much better performance when building reports, no need for application level data wrangling, ...