7,149 karma · joined April 4, 2013
Consider it a two lane road, where you give way when you merge into the other lane and you slow down behind slower traffic that's in your lane. Except that when both lanes are available each type of traffic prefers "their" lane due to the speed difference.
That speed difference is decreasing in the bigger cities recently. Ebikes drive 25 km/h and many shared streets are reducing from 50 to 30 km/h for cars. It probably helps that a lot of the bigger streets aren't shared, there are many separated bike lanes here.
I guess there is some built in spare capacity, but that may still qualify for the exemption?
Edit: Just to quote the official investigation on an Emirates fuckup: "The flight crew reliance on automation and lack of training in flying go-arounds from close to the runway significantly affected the flight crew performance in a critical flight situation which was different to that experienced by them during their simulated training flights."
That reflects exactly how the rest of the industry thinks about the gulf carriers and their crews. Combine that with non optimal CRM and you have a disaster waiting to happen. They already did this twice, not understanding automation and (nearly) flying a jet into the ground.
I've heard others had similar results with .NET/C#
And most of those influencers aren't even rich...
I think it provides ground track information not just heading? Which is far more valuable for aircraft navigation, because the main issue is unpredictable wind drift.
It keeps a repository with markdown files as the agent context, makes those available (via a simple search and summarise MCP) and when closing a merge request it checks whether the context needs updating based on the review comments. If it needs updating a PR is opened on the context repository with suggested changes/additions.
In aviation rules you can have passengers at 12k ft without oxygen for an unlimited amount of time. The crew needs to use oxygen if you're between 10k and 13k for more than 30 minutes. Above 13k both crew and passengers must use oxygen immediately (EASA rules, FAA is different).
So they seem to consider 12k to not be dangerous to passengers.
The place where it hurts is small VPSs, from AWS to mom and pop hosters, the cost of addresses is becoming significant compared to low cost VPSs.
Consider a circuit in a home, designed to carry 16A like a common EU/UK circuit, protected by a 16A breaker. Then plug in solar or a battery that delivers just a small 10A. Now in case some other thing on that circuit draws 26A, the breaker doesn't stop it and the circuit is overloaded.
If that same solar was installed as a fixed setup on its own circuit with no other loads on it, it would be safe and protected by the 16A breaker in the switchboard. It's the combination with other loads that causes issues.
It runs Claude in docker containers, listens for webhooks to see comments and CI status.
For aircraft it's very rare to receive control back from the autopilot in an upset-state. An exception is a trim-runaway, which is a very serious emergency that gets trained for.
In cars you don't have that luxury, it's much more likely that you have to act immediately with very short notice. That does not work for human drivers.
The project was great to work with, Daniel Stenberg (also the curl maintainer) was really good at helping newcomers like me participate. That may be a big part of why the project is still around 20 years later.