A £1500 car is £1500 because it's expected you'll need to replace the engine or transmission pretty soon. That can be up to a £4000 job (£2500 on the low end).
And, as it turns out, a brand new 50kWh battery costs around £4000 to manufacture. Used will be cheaper.
With most modern ICE cars everything but the transmission and the engine will fail before those two go out.
Also: I don't think that's the usual case. Plenty of sub 2k cars that will happily keep driving for years (I've had 3 such cars). ~700 mark is where you start seeing 300k mile "finish-them-off"-type cars.
Plenty of EVs will drive for years as well (so long as they have a good thermal system for the battery). So I'm not sure what point is being made.
Saying "It costs a lot of money to replace the battery" doesn't mean much as the battery, even if it has 70% of it's original capacity, is still perfectly functional. Very much the same as the engine which also costs a lot of money to replace.
Presumably a lot of people will charge at home which significantly cuts down the number of stations needed or the traffic to those stations.
For example, I have 2 gas stations within a mile of my home. They stay pretty busy because people around me constantly need to fill up. I, on the other hand, basically never visit either of those stations since I switched to an EV. I charge at home.
If everyone around me switched to EVs, those stations could not stay in business. There's a grocery store in the same area which makes anything those stations offer obsolete.
Those are the majority of gas stations that die with a mass switch over to EVs. There's a gas station for my hometown without an attached convenience store with 300 people there. There's no way that station stays in service if a significant portion of the community switches to EVs. It already struggles to be profitable as is (I know the owner).
Electricity is expensive in the UK (~25p/kWh) But not gas car expensive. It is £1.57/L (£5.94/gallon).
The EV infrastructure is also pretty dang far along, especially compared to the US. Remember that everything in the UK is a lot smaller and closer together than it is in the US. Further, the UK has a functional train system for long distance travel. You can go from the top of Dunnet Head to Lizard Point in a 15 hour drive.
People downvoting me, Look up chargers in plugshare to see just how many there are in the UK, it's a lot. And also correct my math if it's wrong. An 80kWh car costs £20 to fill up. A 55L car, which has about the same range, costs £85 to fill up.
Also if you are able to charge at home you can subscribe to a smart tariff that gives you electricity for 4p/kWh overnight. That’s £3.20 to fill an 80kWh battery that on a modern car will take you up to 320 miles.
There have been fairly recent changes to the linux kernel to better support panther lake in terms of power performance. I'd suspect a major reason for holding back is because ubuntu 26.04 has not been released yet and it is using kernel 7.0 which includes these power improvements. 24.04 does not.
By the time these laptops start shipping, 26.04 should be released and testing should be easy. I suspect no major differences from it vs windows.
7.1 includes even more performance improvements for panther lake. [1]
If I was releasing a laptop with Linux support as a key selling point, and the battery life was bad on Ubuntu 24.04 but good on the pre-release 26.04, then I'd advertise the good figures and write "tested on Ubuntu 26.04 beta, requires Linux 7.0 or later" in the footnotes.
I definitely /wouldn't/ rely on just Windows figures for a machine that's otherwise advertised as "Linux first". If the battery life was the same on both, I'd prominently mention that.
I'm a long-time Linux user who might actually be in the market for a just-works upgradeable laptop[1] that comes with Ubuntu.
I already know that combinations of hardware and software can be stretched and tweaked to do really interesting things in really excellent ways. I don't need them to tell me that computer systems are flexible. That's just noise.
And I don't want them to tell me how their (unreleased) hardware might work in the future with some unreleased/beta software. That tends to be interpreted as speculation, or as lies and deceit.
I'd prefer to see benchmarks of how it works if it shipped today.
If those benchmarks are unsavory (as they may presently be) and thus omitted, then that's not ideal but it's okay.
I definitely don't want to feel as if I'm being lied to, in place of an omission.
[1]: I just want a 15" version. I'm not a fan of little screens. My eyes aren't getting any better.
Yeah, really impressive to see that you can take a 13 and turn it into a 13 pro with just a few new parts.
I've just ordered my own 13 pro. I've been waiting for a laptop and this ticks all the boxes. I'd previously ordered a new dell xps laptop and ultimately returned it because the keyboard was busted. I would have kept it if I could have swapped the keyboard for a new one. The use of LPCAMM is also really nice. I've hoped to see this standard start taking flight and I'm happy to grab a product with it included.
> I suppose there is a fundamental tradeoff somewhere, but that doesn't mean you're actually at the Pareto frontier, or anywhere close to it. In many cases, simpler code is faster, and fast code makes for simpler systems.
Just a little historic context will tell you what Knuth was talking about.
Compilers in the era of Knuth were extremely dumb. You didn't get things like automatic method inlining or loop unrolling, you had to do that stuff by hand. And yes, it would give you faster code, but it also made that code uglier.
The modern equivalent would be seeing code working with floating points and jumping to SIMD intrinsics or inline assembly because the compiler did a bad job (or you presume it did) with the floating point math.
That is such a rare case that I find the premature optimization quote to always be wrong when deployed. It's always seems to be an excuse to deploy linear searches and to avoid using (or learning?) language datastructures which solve problems very cleanly in less code and much less time (and sometimes with less memory).
And as I point out, what Knuth was talking about in terms of optimization was things like loop unrolling and function inlining. Not picking the right datastructure or algorithm for the problem.
I mean, FFS, his entire book was about exploring and picking the right datastructures and algorithms for problems.
And, as it turns out, a brand new 50kWh battery costs around £4000 to manufacture. Used will be cheaper.
reply