That’s a bit of a strawman argument. Most journeys don’t consist of three children and all their sporting equipment.
As a practical example, in the UK, on average a young g child lives 1.7miles away from their school.
That is an easily walkable distance for most children, yet lots of parents choose to drive it because they feel the streets aren’t safe to walk on in rush hour.
If by redesigning streets to make active travel more appealing, you could reduce the number of cars on the school run by 10%; it would improve the traffic situation for the ones who still need to drive. Win-win
>This article gave an LLM a bunch of health metrics and then asked it to reduce it to a single score, didn't tell us any of the actual metric values, and then compared that to a doctor's opinion. Why anyone would expect these to align is beyond my understanding.
This gets to one of LLMs' core weaknesses, they blindly respond to your requests and rarely push back against the premise of it.
I've come to the opinion that for the vast majority of apps I've built, it could all be built using HTML + CSS (all built server side). I can sprinkle in little bits of interactivity using something like HTMX. And I'll have a website that is very easy to optimise, has phenomenal backwards compatibility, and gets rid of a whole class of issues associated with SPAs.
I often regret in my career not pushing back more on "requirements" that ended up requiring a more complicated app, whereas the customer would have been happier with a simpler solution.
From a customs perspective, flying from one EU country to another EU is treated like a domestic flight.
If I (a British citizen) flew from London to New York, then on to Chicago; I'd expect to go through customs when I arrived at New York, but not when I arrived at Chicago.
What you’re describing sounds like it was the customs check. Pre-brexit, if you were arriving from the EU, then there was no customs check since we were all part of the same customs union.
I've come to the opinion that for the vast majority of apps I've built, it could all be built using HTML + CSS (all built server side). I can sprinkle in little bits of interactivity using something like HTMX. And I'll have a website that is very easy to optimise, has phenomenal backwards compatibility, and gets rid of a whole class of issues associated with SPAs.
I often regret in my career not pushing back more on "requirements" that ended up requiring a more complicated app, whereas the customer would have been happier with a simpler solution.
>All told, four of these stations had roughly 90% the throughput of the four real humans
Probably about 1% of the cost of the humans though...
>Kiosk based stuff is great until it fails. Spend an hour in the checkin area of a major airport and you'll see any number of interesting failure modes.
A robot would be less reliable than a kiosk, so if you're going to have some kind of machine replace the human, you might as well have a kiosk.
The ideal model (IMO) is a hybrid model, where you have lots of kiosks for the 90% of cases where there are no issues, and a few humans on standby to drop in and assist people who are having issues.
Or better yet, do away with the check in desk, and let people check in on their phone (some hotels already do this, and you tap your phone on the door to unlock)
With self hosting email, if the digital sovreignty aspect is more important to you than the privacy aspect...
What I do is use gmail with a custom domain, self host an email server, and use mbysnc[1] to always be downloading my emails from gmail. Then I connect to that email server for reading my emails, but still use gmail for sending.
It also means that google can't lock me out of my emails, I still retain all my emails, and if I want move providers, I simply change the DNS records of my domain. But I don't have any issues around mail delivery.
I never sign up for subscriptions anymore without using a virtual card. Once I've paid the yearly fee, I immediately cancel the card. When it comes to renew, they'll be very keen to let me know that my card needs updating.
The use cases in their videos are interesting, I suppose the world we live in is build for humans, so it makes sense to build a robot that is human shaped. So we don't need to buy new washing machines and redesign our house to get a robot maid.
The hotel reception use case seems ridiculous though, if you get rid of a human receptionist, you lose the human element of the check in process, which people like. If you're getting rid of the human and losing all the benefits of that, then just replace it with a kiosk (or mobile check in), which will do a far better job than a robot.
One Login is an "authentication" system, an oAuth provider with identity added on. This means you can prove your identity once (to various levels of confidence, as defined in GPG45 [1]), and use that same verification across different government services.
When people talk about a national ID system, they're often talking about some form of "authorization", i.e. proving that you are entitled to certain things.
There currently isn't a system in the UK that can definitively prove that you have access to every service. For example, even being a British citizen and having a British passport doesn't automatically entitle you to access the NHS.