CoderKat

You did 200k years. You need to do 200k years as seconds (the 6.311e12 they mentioned). Their math is right.

Not sure why you're acting like they claimed to invent the logarithm, either...

Great to see such wide sweeping worker solidarity! Tesla can suck it for their refusal to even play ball with workers.

No, we are both dreaming butterflies.

Such a choom.

I have an idea. What if we attached a power line directly to the car, so we didn't need a battery? Of course, it'd only be able to run on specialized lines. To get the most out of those lines, we could chain cars together. And since the specialized hardware doesn't make sense to own, we could have municipalities own them and charge a fare (or better yet, just make it part of taxes).

I get what you're saying and that's obviously a concern, but at the same time... doesn't it have to be reasonably far in the future? We don't have either the infrastructure or even enough supply of EVs to change this too quickly.

That said, I wish they'd use a gradual approach. Start ramping up taxes on gasoline with the proceeds entirely going to EV infrastructure (and similar for purchasing new gasoline vehicles and licensing existing vehicles). Start small and increase as we get closer to the cutoff date. Start limiting gas station development and create zoning regulations for EV infrastructure (especially charging for apartments, which is a huge gap). Make all the laws ramp up gradually so that it's always small, incremental changes that are never too difficult to do at a time, but will get us in a better place in 10-15 years.

We are ridiculously inconsistent in Canada. I've seen all 3 of the most popular formats here (2023-11-22, 11/22/2023, and 22/11/2023) in similarish amounts. Government forms seem to be increasingly using RFC 3339 dates, but even they aren't entirely onboard.

Huh, I've never noticed how much bloat was in ISO 8601. I think when most people refer to it, we're specifically referring to the date (optionally with time) format that is shared with RFC 3339, namely 2023-11-22T20:00:18-05:00 (etc). And perhaps some fuzziness for what separates date and time.

I think the rat king would be a little bit insulted that you even had to ask.

I like the idea of having a regulated, living, backwards compatible standard. Which seems to be what USB-C is now, for phones. The EU has soon to be active regulation that will make it a requirement for many things. Yet, it's not a single, set in stone standard, but one that's constantly being expanded (eg, version 3.2 and PD).

Of course, the regulation has to also be living. Eg, at some point, maybe there'll be a strong enough reason to allow another standard (by no means do I think USB-C will always make sense). And the regulation has to very carefully choose the standard.

That way we get the benefits of standardization (from actually everyone using the same format), but we aren't unreasonably crippling ourselves to do it.

Yeah. There's literally nothing you can put on a prompt that will truly work. It's still a good idea to prompt cause it will reduce how many people approve the prompt, but there is a significant number of people who don't read prompts at all and just insta-confirm.

At best, I think you could design it so there's no way for an app to request certain permissions themselves. They'd have to be opted in from the system settings and apps could only tell you how to do it. But that's a usability nightmare that is quite frustrating for legitimate usages. There's already some super sensitive permissions that do this. I think the ability to install apps, ability to display over other apps, and password managers for android.

I think you can actually solve that one with enough C4 :p