> Commissioning reactors that won't come online for 10-15 years makes no sense at all, economically and practically.
Because we won't need base load in 15 years? Or because you're arguing that we'll have so many batteries, and they'll be so cheap, and they'll be so over-provisioned regarding summer/winter variance, that we won't be able to sell excess nuclear power to the states?
Personally, I wouldn't make either bet, no matter what odds you give me
The fact that every 737 MAX was the samew design also means that, upon rcognizing the flaw, every one could be grounded and fixed properly. We did not have to verify 15 different designs were all vulnerable due to Boeing trying to nickel and dime their customers (by making the third sensor esssentially a paid upgrade/addon)
The ones who most venerate the Founding Fathers are the ones who usually claim that the status quo is good. The status quo can always be attributed as the will of the Fathers.
Sometimes that means using a ouija board to assert that some vague passage happens to mean what they want it to mean.
It's bold to assert that people make up Founder Father's reasoning when just above you claim we use the current electronic voting because:
> "I think just the fact that it was the first thing on offer that wasn't the thing they were already using."
Instead of just assuming things - aka making things up - you could check.
For the Declaration, Articles, and later the Constitution specifically, much of the Founder Father's reasoning and conclusions were well-documented in public via published letters, essays, and speeches at the time. No ouija board necessary.
There are numerous quotes attributed to the founding fathers regarding how future generations would need to update their solutions for the times. As far as how some will assume, some will assume anything that fits their worldview.
But even that peace keeping will involve active combat, unless the mission fails or the force involved is so capable ot deters opponent. You dont want to end up like the blue helmets in lebanon and more like nordbat in kosovo.
That still means the main point, the reason they are there, will never be peace. They are there to fight, and to fuck your shit up - which is both an image the current administration embraces, and very much not a good look outside the country.
This is in no way a solution to the population-scale problem of a belligerant nation having root on the citizenry's mobile phones/cameras/GPS units/network scanners
I'd throw in the manual gearbox, the noise, vibration, smell, and being able to see the mechanical workings as well. We can get a punchy, lightweight vehicle with an EV conversion, but as you've heard from others, that leaves something to be desired
But yes, the vibration, sound, and feel of the incredibly simple (as in stripped down, not unsophisticated) mechanics around you all very much contribute to the special feeling of driving these cars.
My 1976 BMW 2002 is actually my first car. I used to drive it to high school more than half my life ago, and I still drive it today. I’ve driven some other classic cars, luxury and sport, and simply nothing feels like a 2002. Just a beautiful, balanced, timeless design.
Fuck, you missed it being bad at being a phone. It launched on the network that had such bad coverage they needed Apple's hottest product ever to get people to switch. They had to put a cell repeater (or was it a miniature tower?) in the presentation center so the call would go smoothly, and still had to rig the cellular icon to always show full bars.
Judged purely as a "Let's give Ted a call"-phone, it was fucking bad compared to the competiton. They killed it in other areas, don't get me wrong, but not at being a phone.
> Devs have always considered ourselves lazy. The point of programming is to do as little actual work as possible ;) Any self-respecting sysop has a couple hundred scripts so that they don't have to actually type anything :)
Sure, that's why this [0] XKCD was made - getting pulled off on a geeky sidequest, automating something that has (almost) no business being automated, and spending far longer configuring, debugging, and refining your "time saving" scripts than actually doing the damn task are what I expect a dev to get lost in.
Which, sure, is a form of laziness, but it has a different vibe than getting an LLM to do everything for you IMO.
As an aside, a common refrain is that the best computer people are innately curious; they wanted to see how the computer responded if they broke or changed something. LLMs make putting up with the (relatively) long slog to find out less likely to happen; in a way, I'd argue they destroy curiousity itself: a horrifying proposition for anyone that looks to the future of computing, or even humanity in general.
> LLMs make putting up with the (relatively) long slog to find out less likely to happen
My experience has been the opposite. I get claude to go down those rabbit holes a lot, precisely because the effort of doing that is smaller, and claude usually has some insights that help. Often mistaken insights, but still.
While I could have sworn RIM put out their own modems (which Qualcomm used to make life difficult for them, especially as the world transitioned from 3G to 4G), and did their own hardware and software, I can't currently find a source
Because we won't need base load in 15 years? Or because you're arguing that we'll have so many batteries, and they'll be so cheap, and they'll be so over-provisioned regarding summer/winter variance, that we won't be able to sell excess nuclear power to the states?
Personally, I wouldn't make either bet, no matter what odds you give me
reply