Sorry, I just realized that was worded ambiguously. I meant that it has two-thirds the population of any of those three countries individually. So I should have worded that as:

Mea culpa.

What? Canada's population *density* is much lower than the rest of the EU, but in terms of actual population, you're off by almost an order of magnitude. Canada has about 9.2% of the population of the EU.

Canada has about two-thirds the population of France, the U.K., and Italy, or about half the population of Germany. Canada has more population than any single country in Europe other than Germany, France, the UK, Italy, and Ukraine. With UK now out of the EU and Ukraine not yet in it, that would make Canada the fourth largest country in the EU if it joined. (And even if Ukraine joined, they're within the margin of error of having the same population as Canada.)

So if your argument holds true for Canada, it also holds true for the entire EU.

You might want to rethink your position here. Just saying. I'm not saying Canada should join the EU, since being the only country that's not even remotely in Europe might result in lesser treatment, but if that happens, the reason won't be because their population is too small.

Why do you think they would stop in their tracks every time there's a power or cell tower outage?

Yes, there have been some issues with widespread power outages causing the cars to get confused because things don't look right, but that's a bug, not expected behavior.

And although they won't have fares if they have no cell service, there's no reason to expect them to stop being able to drive. They will do whatever they normally do when they have no fare — find a place to park. Other than for learning about pickups and dropoffs, robotaxis use cellular networks only when they break down, to request remote driving assistance (i.e. relatively rarely).

Oh, yeah, I just realized that this is an expense on the Roku side, so the taxes would cancel out. Ugh.

Then yes, you're correct that there's no possible way for consolidating two businesses to save money without direct job loss, other than perhaps reducing payouts to external companies for things that they both do (e.g. accountants).

The biggest problem with advertising as a funding mechanism is that it creates incentives to *make the content worse*. It's no longer "what can I present that will help the user". It's "what can I present that will attract advertisers and keep the user spending time where I can further target them". There's the tracking thing, too, of course, and the scam propagation, and whatever else. As well as just the raw annoyance.

There's no incentive for anybody improve "bad ads" as long as they believe bad ads still work. Even if they *had* an incentive, it's not obvious how either the people producing the ads *or* the people serving them would actually do it. The producers are presumably already placing the ads they think are most likely to meet *their* goals. And as for the servers, they have very little leverage, because, in the end, their business is "you pay me to show the user whatever you want the user to see".

Sure, subscriptions suck. So come up with an alternative, say a truly privacy-preserving micropayment system. That's doable nowadays in a way it would *not* have been in the late 1990s... but it won't happen as long as it's possible to keep leaning on advertising. Nobody wants to be the first mover on something like that or eat the development costs alone. Advertising needs to die so that something better has space to grow.

It may not have been in the spec, but if it was widely known that the chip could do it, then it very well could be the case that people purchased the chip because of that, in which case the company unjustly benefitted from the widespread belief that it was supported, and is now seeking to further unjustly benefit by forcing those buyers to spend more money if they want to keep that feature.

Their failure to explicitly make clear that this was a bug and fix it in a timely manner is at least potentially an implied representation that could be subject to promissory estoppel.

In other words, they're probably doing something that violates the law, but we won't know for sure unless someone cares enough to sue over it.

Nope. You forgot the government factor:

($Fox + $Payment - (corporate_income_tax_rate * $Payment)) + ($Roku - $Payment = $Fox + $Roku - (corporate_income_tax_rate * $Payment).

So depending on what state the income is earned in, Anywhere from about 21% to about 30% of that could be going to taxes. So they could easily save $400M in taxes if that payment happens to be at least $1.3 billion or so. I doubt that's the case, of course.

The most critical skill is knowing when you're going into an AI rathole, shutting it down, and coding the relevant bits from scratch. There's nothing like wasting more time on iterative refinement than it would take to write the code by hand to sour an engineer on the use of AI.

The top 1% of the U.S. have $55 trillion dollars. The total U.S. national debt is only $38 trillion. That costs the government $1.4 trillion every year in interest alone. Leveling the playing field by capping everyone's total savings at 8 million per person would wipe out the national debt completely.

Mind you, wiping the national debt out still won't help as long as the Republicans keep overspending and undertaxing to the tune of two trillion a year, but even that should be easily fixable by more sound tax policy, coupled with laws mandating that the federal budget be revenue neutral or positive going forwards.

We've done the math. Have you?

I assume you're saying Pro is massively better for your workload. IMO, thinking is either good or bad, depending on whether it moves you closer to or farther away from correctness.

For example, I've seen certain types of workload (e.g. anything involving image recognition or image segmentation) be massively better with Flash, because Pro overthinks things and ends up changing perfectly correct answers to be wrong, either by coming up with creative ways to misinterpret the prompt or by screwing up the JSON image segmentation fragment so that it can no longer be parsed.

And I've also found that LLMs struggle to understand existing terms in a different context that they weren't trained on. As a result, I've had to substitute nonsense terms in place of terms based on common English words and phrases so that it won't ignore my definitions of those phrases in context and substitute its own understanding of their meaning and give incorrect results. The more thinking you allow, the more likely it is for that to occur.

I live in London. Can you tell me where I apparently canâ(TM)t go?

This just seems so short-sighted. You spend a bunch of money familiarising with the code knowing that youâ(TM)ll be forced to do it again after youâ(TM)ve forgotten it. This is an opportunity to eliminate an unnecessary upgrade step. Each step of course will risk new and different regressions. Never mind that people donâ(TM)t find working on old code and tooling very motivational.

Iâ(TM)m not so au fait with the Java world anymore, but in C++ land, there are some serious benefits from using new compilers in terms of code speed and better language features and compiler errors/warning they help you write better code. Every time we upgrade, the compiler finds something in our 25 year old code base that shouldnâ(TM)t have worked!

Our former colonies have all made the metric switch just fine. Canada's a bit confused because the building industry tends to be Imperial (or the US equivalents), but otherwise they're switched fine. As a Briton who emigrated to Canada as an adult and married an Aussie, before returning to the UK, I can attest to the fact that you can adjust. I don't do anything in miles anymore, even though I've been back in the UK almost 20 years. For a while I did low temperatures in celsius (I'd lived in Canada) and high temperatures in Farenheit (I'd live on a RAF base in Cyprus in the early 80s and later in the US in my 20s), but then I lived in Melbourne and experienced high temperatures and metric at the same time. It comes down to experiences.

Pints are defined in mls! Please don't go metric in the Aussie way: their beers are tiny ;)

But Ireland, Malta and Cyprus can continue driving on the on the left? Would the province of Northern Ireland be given a special exemption? Seems fair given that it's already got half a foot in the EU already due to Boris's Brexit deal that sold them out and undermined British sovereignty with a line down through the Irish Sea. Or would you force a switch of sides when crossing the border? That would all seem to undermine the Good Friday Agreement though.

Two decades seems a bit arbritary, maybe even spiteful. Maybe an absolute majority of the electorate rather than just of those who bothered to vote or perhaps a clear margin of 20% or more would be a better measure of suitability to rejoin the EU. Anything less risks reversal a few years later.

I don't think many people supporting rejoining actually realise or support the idea that rejoining won't be on the same terms as before. You're alluding to that in a spiteful and unrealistic way, but your comment is based in reality.

Can I run Homebrew on that? What about Linux, Windows and macOS VMs?