So about like every other autoland — right on the runway marker, hard enough to break teeth.

Incorrect. We had an election. About one third of voting-age citizens preferred Trump. A little less than that preferred Harris. Almost that many didn't care enough to vote for either one.

Any one of those cases could potentially have been insurmountable if a judge had found in their favor. Like I said, there were fundamental questions of law regarding whether that permit was lawfully issued in the first place.

They took apart the portions that were already built. It was shut down. Spin it however you want; the project was dead at that point.

They would fight it if they thought that him rescinding the permit was unlawful, because the only alternative was losing the money they had already spent building parts of it. They did not, because they believed that given the circumstances, rescinding the permit was lawful. They were potentially correct because of the way that the permit was issued.

Again, they did not. They stopped construction and started tearing it down. There are no plans to try again.

It actually is far off.

A legally issued permit is binding on the government. An illegally issued permit is not. The offshore wind farm permits were legally issued. The Keystone XL permits likely were not.

The legal difference between a permit issued through the usual decades-long approval process and a permit issued in an expedited fashion under executive orders to rush the environmental review to make the project happen is substantial. The legality of that executive order was in question, and the expedited environmental review created serious questions about whether the review met the standards required by federal law. At that point, it became the states' right to challenge the permitting, and they did.

Had they won, the permits would have been rolled back by the courts.

Let me stop you right there.

You presuppose that we know what a good desktop is. I don't think we do. I think trying many different variations to find out is exactly how we some day will.

In which parallel universe? Windows has shown what a barely passable desktop needs, one that is just about good enough to stop people from escaping from the lock-in.

We agree.

But it is not a problem the Linux crowd can solve. Because it's not a technical question.

Pulling that permit might have been legally questionable, but the real story is way more complex than that, because the legality of the permit was in question and had been under scrutiny by the courts for the entire period in question. Their decision to start building in spite of the permit potentially being illegal was a mistake, and the losses from such a mistake were entirely their responsibility.

I find it difficult to imagine how they could have come to such a dubious conclusion. Oil sands are some of the dirtiest oil you can get, and encouraging the use of oil sands refining before other, cleaner sources of oil is not sound environmental policy. And making that oil easier to import into the U.S. would doubtless encourage more extraction.

A permit, once denied, isn't generally eligible for being reinstated without correcting the issues noted in denying it. They did not correct anything. Instead President Trump issued a permit himself outside of normal regulatory channels, overriding the decision of those regulatory channels, with a complete lack of environmental review, likely violating dozens of federal laws. The legality of such a presidentially issued "permit" is dubious at best, and that legality was being actively contested in the courts at the time, precisely because there's no precedent for a president having any legal authority to circumvent regulatory authority and issue a permit that violates environmental protection laws just because he wants to.

There's a reason that the oil companies did not bother to fight the Biden administration's decision to rescind the permit, and simply shut down the project. They knew that the legality of the entire project was highly questionable, and that they had spent money building parts of it with full knowledge that the permits were being challenged in court and could be found invalid, at which point they would have to tear it all down. They baked that risk into their calculations and decided to go forward anyway in hopes of a windfall, and they lost.

Nothing like that is the case for offshore wind farms, to the best of my knowledge. They were permitted through the usual regulatory channels, and there was no plausible reason to expect that such legally issued permits would be illegally rescinded on the whims of a wannabe dictator.

So it's not really the same thing. It's not even close.

IMO, given the amount of money involved and the patent absurdity of the government's behavior, the only rational thing to do is ignore their order and continue to build the wind farm anyway. The government has no legitimate legal right to take back a long-term contractual agreement like that. Once they signed on the dotted line, the lease is valid. Any national security concerns, if legitimate, should have been settled before the government entered into the agreement. Now, it's too late. Tough s**t, Donald Duck.

The government has only one option at that point, and that is to take the wind farm company to court. At that point, keeping the reasoning secret from the judge will not be possible, and the judge will see right through the farce and order them to do what the judge ordered them to do before — live up to their agreements. Realistically, national security concerns are implausible, and more to the point, even if a national security concern does exist, that's the government's problem to figure out how to prevent it from being a national security issue. They have no legal right to coerce a corporation to act on their behalf in doing so, absent a law being passed by Congress, which they have not done.

The only alternative is to waste years in court trying to get a judge to overturn the executive order and then wait for them to file another one in six months, resulting their use of the land being a constant yo-yo. The only rational thing to do, IMO, is to force the government's hand by making it clear that you won't be bullied, and making it clear that every future interaction along similar lines will end the same way — with you continuing to operate under the terms of your existing agreement and the government repeatedly and expensively failing to compel you to do otherwise.

Well... maybe. Tesla premium connectivity costs $10 a month or $99 per year when purchased annually ($8.25 per month equivalent). My Apple watch uses a fraction of the bandwidth by comparison, effectively doing nothing more than receiving text messages and notifications. (Phone calls on a watch replace a cell phone on the same line, so they really don't increase usage.) Yet service for my Apple watch costs $15 a month.

So judging by the state of the market today, buying service from a phone company is likely to cost considerably more than buying it from a car company, assuming the car company doesn't use it as a profit center, because car companies get a deep discount by buying service in bulk for a million cars.

Whether you can safely assume car companies won't use it as a profit center is another question, but there's always mobile hotspots if they do, so there are limits to how much they can overcharge.

We had this discussion in 2023. And in 2021. 2020, 2019, 2017, 2015, 2013, 2011, 2009, 2008, 2007 and I think 2005. Or so.

Oh dear, poor users don't know where to start. I'm sure that is the one and only thing that stops the entire world from switching to Linux. Certainly not the lack of games, business applications or compelling reasons to switch from the shit that they currently run and know is shit but at least they know that shit.

Linux has won the server OS wars. When's the last time anyone had a serious discussion of using whatever the last windows server OS version is for anything critical? When's the last time you logged into a Solaris machine?

The desktop is a different game, always has been, always will be. It's a game run not by technical excellent. I mean, exhibit A: DOS and Windows, who were never, ever, the best OS - just the most popular one. But on the desktop, what matters is if the users can use it (it's right there in the word) and that hinges on two things: a) familiarity and b) availability of applications.

a) is a lot more serious than most of us nerds realize. Think about any random corporation. Let's say 5000 office employees currently using Windows. Re-training them to use Linux instead might take just a few hours for the tech-savvy ones, and let's say a day for the less so. Add twice that as a period where productivity is at least somewhat hampered by them having to look up again or ask a colleague how to do X. Suddenly you're looking at something like 30-50 thousand hours of lost productivity. And these are not minimum-wage people. So your bill is what, half a million?

b) this is the applications the business actually uses, not some Open Source alternative. If the graphics designers use Photoshop, they need that, not Gimp. Tons and tons of enterprise software is windows-only. And there we are with the chicken-and-egg problem.

Seriously, "the Linux desktop is too fragmented" is bullshit. All things considered, that's the least worry of anyone. And one of the greatest strengths. I know that I would've given up completely on Linux a lot sooner than I actually did if there had only been KDE and Gnome, and not Enlightenment and other interesting options pushing the boundary of the possible. Heck, E would still run circles around almost all UIs today.

Only when something goes wrong, which one hopes occurs with declining frequency. Of course, this past weekend probably cancels out the last five years in one day... :-D

It doesn't necessarily indicate that. You're speculating.

It is entirely possible that Waymo Driver truly doesn't know how to handle that edge case. That's probably not the sort of thing that you'd have a lot of training data for, after all. However, I can think of at least five other possible explanations that are also plausible.

Option 1: In the interest of safety, they required the cars to phone home to report a traffic light down and confirm before proceeding, but because so many lights went down all at once, the remote operator team became overloaded.

Option 2: Some human driver did something significantly unexpected, and the Waymo driver software concluded that a wreck was imminent and assumed that it did something wrong, and stopped rather than risk making the problem worse.

Option 3: Those intersections were in areas that were covered mainly by secondary cellular towers that lacked proper battery backup, and the network went down. The remote operators were unable to take control over the vehicles to get them started again after one of the two possible explanations above.

Option 4: The network went down and the software has a bug that causes it to fail in some unexpected way when the car can't communicate with the central servers.

Option 5: The network went down and the underlying cars have disabling technology that causes them to shut down when they lose communication (for theft prevention reasons). However, I think that one would also require satellites to be unavailable, which is not too likely.

We won't really know for sure until someone at Waymo analyzes the data and publicly provides an explanation for what happened, which probably won't be until next year, because I suspect that a majority of Waymo employees are probably gone for the holidays this week and next. :-)

No, because Waymo cars are actually autonomous and thus don't have a human driver in them. The only thing they can do is phone home and ask a human to plan a path for them or otherwise tell them what to do. And that takes longer than if a human were in the car driving. There's no real-time remote driving (for obvious safety reasons).

It's very relevant. It means that they don't have to care about safety. They can drive through the down light without stopping and trust a human to intervene. They can stop without going and trust a human to intervene.

But more than that, they have the luxury of treating it as a stop sign without worrying about whether the traffic light really is out or just not being detected because of a regression in their image recognition model, because if they are wrong, a human will intervene.

So having a system that is human-supervised relieves Tesla and Cruise of a lot of the responsibility for mistakes and makes them able to enable riskier features.

Apparently you have never driven in San Francisco. These aren't freeways, and these aren't suburbs. They're mostly dense urban streets a la Manhattan. You either have a continuous row of cars parked along one side or both, or you'll have driving lanes. There are no shoulders. If you get very lucky, there might be one spot free, but not enough spots for four cars at a single intersection — probably not at any time, day or night, realistically.

So in situations where stopping in the middle of the street is safer than continuing, then it is, in fact, a safety feature, because there is rarely (if ever) a third choice.

The safe fallback on the freeway is typically to pull over onto the shoulder. Unfortunately, city streets in SF do not have those. If they did, they would have been turned into a parking lane or another driving lane already.

Let's get real here. I live near a light rail line, and that's still a 15-minute walk, plus five minutes at the other end. And the closest light rail stop to my office is about a ten-minute drive on city streets, and it takes twenty or thirty minutes to get there on the light rail. So add it up and yeah, I could walk for 20 minutes, then take public transit for 20 minutes, then take some kind of shuttle for 10 minutes.

Or I can spend fifteen minutes, ten of which are on the freeway, and drive myself. The walking portion of the trip alone exceeds the total length of my commute.

Rail only makes sense if traffic is so bad that cars are completely infeasible. Otherwise, they're the wrong tool for the job.

I'm not the person you're replying to, but for me, it depends on where I'm going. To a scheduled appointment? No. I plan it out. On a long trip? Also, no. To the grocery store? Yes, of course. It's a five-minute drive on city streets. I'm sure not going to spend a minute on Google Maps to see if traffic is bad and I could save one or two minutes by waiting an hour. That wouldn't make sense.

My last shopping trip involved stopping at three different Lowe's and Home Depot stores because the website availability was so detached from reality that they had zero of something that they supposedly had 16 of in one instance. It's not random, but that doesn't mean the plan doesn't have to change at a moment's notice. Doing it by car took an hour. Doing it by public transit would have taken the better part of a day, because the second and third stores would have closed before I could have gotten to them.

So yeah, having to make unexpected changes to your plans is more common than you think.

And for long trips, food stops and restroom stops tend to also be random (though long-distance train systems often have those onboard, making that not a particularly interesting point). On the flip side, for long-distance trains, the interval is usually anywhere from several hours up to a whole day, so if you do have a planned stop for some other reason, it's going to be a long stop, and will usually require a hotel stay.

Sadly, that's not most places with trains. Subways, maybe, but surface trains tend to be more like every 15 minutes or more.