computers

24 May 2026

Slashdot

Tesla's Electric Cybercab is Certified as the Most Efficient EV Ever

Tesla's upcoming Cybercab "has been certified at 165 Wh/mi," reports Electrek - which makes it "the most efficient electric vehicle ever produced - by a wide margin." The next most efficient EV on the market, the Lucid Air Pure, consumes 28% more energy per mile. Tesla VP of Vehicle Engineering Lars Moravy confirmed the figure, which represents a certified rating - not a marketing claim or internal target. It's an impressive achievement, but it comes with a massive asterisk: Tesla accomplished this by building a tiny two-seat robotaxi with no steering wheel, no pedals, and a sub-50 kWh battery pack... Even Tesla's own Model 3 - one of the most efficient passenger EVs you can buy - needs nearly a third more energy to cover the same distance... Where the 165 Wh/mi figure genuinely matters is in the economics of running a robotaxi fleet. Energy cost per mile is one of the biggest operating expenses for any ride-hailing service, and the Cybercab's efficiency gives Tesla a structural cost advantage over competitors... The small battery pack also means faster charging times and lower per-vehicle battery costs - both critical for fleet economics. Tesla has said the Cybercab will cost $30,000, and the efficient powertrain is a big part of hitting that price target. Tesla confirmed Cybercab production has started at Giga Texas in April, though the ramp is expected to be slow initially. The company still hasn't solved unsupervised autonomous driving - the first steering wheel-less unit rolled off the line in February, but Tesla's supervised robotaxi fleet currently crashes at roughly four times the rate of human drivers.

Linus Torvalds on How AI is Impacting the Hunt for Linux Kernel Bugs

Linus Torvalds spoke this week at the Linux Foundation's Open Source Summit North America, reports ZDNet - and described how AI is impacting Linux kernel development: "In the last six months, we've seen a lot more commits," Torvalds noted, estimating that "the last two releases, it's been about 20% more commits than we had in the previous releases over many years.... The real change that happened in the last six months was that the AI tools actually got good enough for a lot of people... we're seeing a definite uptick in just development on pretty much all fronts...." On the positive side, he framed AI-discovered bugs as "short-term pain" with long-term benefits: "When AI finds a bug in any source code... long term is you found a bug, we fixed it, that the end result is better for it." After all, he continued, "I think finding bugs is great, because the real problem is all the bugs you didn't find..." For small teams or solo maintainers, he said, flood-style AI bug reports can cause real burnout, especially when "it's a bug report, and when you ask for more information, the person has done a drive-by and doesn't even answer your questions anymore." The AI news site Techstrong notes this quote from Torvalds. "I have a love-hate relationship with AI. I actually really like it from a technical angle, I love the tools, I find it very useful and interesting, but it is definitely causing pain points." The chief challenge with AI is that it forces people to change how they work, he found. People get into a rut, and AI challenges their norm. The Linux security mailing list got the brunt of this new wave of AI-generated commits. Not all bugs are security issues, but when "people think that when they find a bug with AI, the first reaction seems to sometimes be let's send it to the security list, because this may have security implications," Torvalds said. As a result, the security list - watched over by a small group of maintainers - was overrun by duplicate entries... The Linux project learned to manage the bug influx with a set number of tools to sort out and deprioritize the obvious drive-by reports (ones where the person submitting the report won't even answer any questions). One tool, Sashiko, reviews all the patches submitted on the mailing list. "Sometimes the review is not great, but quite often it finds issues and it asks questions and says, 'Hey, what about this issue?'" he said. Linux also updated their documentation, partly just to address "an uptick in bug and security reports from discoveries made in full or in part with AI."

23 May 2026

OSnews

“Long-term support” does not mean what you think it does

You may think you know what "long-term support" means when picking a Linux distribution and version, but judging by the multitude of utterly wrong takes and deeply confused users I come across online, I'm starting to get the feeling that in fact, no, you don't know what it means. KDE's Nate Graham is seeing the same confusion, and has published a blog post going over what LTS really means in the Linux world. People seem to think that an LTS release means it's going to be more stable, have fewer bugs, and receive support for a certain set period of time. The reality is that only that last one really applies, sort-of. LTS generally means you're going to be using a Linux distribution version where you'll get security fixes and possibly maintenance updates for a set number of years, but you won't be getting updates with new features or other updates that aren't security fixes. The purpose of an LTS release is to more or less freeze itself and its packages in time, so that users know exactly what they're getting. However, part of being frozen in time means any bugs, crashes, and hardware support are also frozen in time. The end result is that LTS releases will often have wildly outdated package versions, and those outdated package versions will most likely contain a ton of bugs and issues that have long been fixed in subsequent releases - subsequent releases you're not getting, because you're on an LTS release. LTS releases are fairly stable and reliable as long as you use the most popular software from their included software repositories. So in the circumstances when this stops being the case, I think sometimes people can feel betrayed. They think, "I thought this was supposed to be stable! Why didn't anyone fix this bug yet? Where's my long-term support?" But Debian, Ubuntu, and Kubuntu never promised any level of stability, reliability, or absence of bugs. They promised that the version-locked software in their repos would receive security fixes for a certain number of years. Ubuntu and Kubuntu also offered a certain amount of non-guaranteed best-effort hardware compatibility improvements and non-security bug fixes. ↫ Nate Graham This causes major problems for upstream developers. People who use an LTS release will be using versions of packages that are out of date and full of bugs that have already been fixed in later versions, but they don't know that, so they end up reporting these old bugs that have been fixed ages ago as if they're new. If you're an LTS user and you experience a persistent bug and subsequent crash in Kwin, you're most likely going to complain at the Kwin developers, even if the Kwin developers have already fixed this bug 18 months ago. Every week there's at least a few developers in my Fedi timeline rolling their eyes at Debian users reporting bugs fixed ages ago and getting mad when told they should complain at Debian developers for not backporting the fix. So many LTS users seem to think that LTS equals increased stability, fewer bugs, and fewer crashes, but that's just not what LTS is for or what it claims to offer. Sticking to specific (major) versions of packages means not you're not only missing out on new features and changes - which might be desirable for you - but also on bug fixes. With LTS, as they say, the bugs are also stable.

23 May 2026 11:36pm GMT

Slashdot

Is America Closer to Ending Daylight Saving Time?

A proposal to make daylight saving time permanent has advanced in the U.S. House of Representative, reports California news station KCRA: A proposal to make daylight saving time permanent has advanced in the House, reigniting an age-old American debate around the twice-annual clock changes. And this time, the proposal has the president's backing. President Donald Trump said Thursday that he will work "very hard" to sign the so-called Sunshine Protection Act into law after the House Energy and Commerce Committee overwhelmingly approved the bill by a 48-1 vote. The bill still needs to pass the full U.S. House, and then the U.S. Senate would consider taking up the measure. The bill would allow U.S states to decide whether to "exempt themselves" from Daylight Saving Time, according to the article. The bill's sponsor described the annual clock-switching as "inconvenient, unnecessary, and out of step with the needs of today's families and economy," while finally creating a permanent Daylight Saving would bring "more usable daylight hours throughout the year."

OSnews

Gnutella: a protocol outliving the world that created it

Now that's a name I haven't heard in a long time. Gnutella is a file sharing protocol that many have forgotten and it has the story of a decentralized technology adopted by millions of casual users who did not care to learn what a peer-to-peer system was. Users showed up because the protocol solved real problems at scale and the solution just so happened to be decentralized. No one ever pretended to use Gnutella in hopes their GnutellaCoinTM would go up in value later. They just downloaded MP3s. The network exploded in popularity, then plateaued for almost a decade, then settled into a permanent long tail state of continued but diminished use. Welcome to my overly enthusiastic love letter to Gnutella. ↫ Rick Carlino I genuinely didn't know - or I had forgotten, more likely - that Gnutella formed the backbone of LimeWire, another name I haven't heard in a long time. I'm quite sure I used LimeWire over 25 years ago, but details are fuzzy and I might be confusing it with other filesharing networks of a similar vintage. I was an avid CD buyer and MiniDisc user (I used MD well into the smartphone age), so I didn't have much need for downloading MP3s. Gnutella is also apparently still active, and there are still clients you can download and use. Of course, it's a mere shadow of its former self, but this, too, was news to me. I'm kind of inclined to see if it's still hosting MP3s.

23 May 2026 10:03pm GMT

Ars Technica

SpaceX's Starship V3—still a work in progress—mostly successful on first flight

SpaceX has more to prove before flying Starship all the way to low-Earth orbit.

23 May 2026 5:54pm GMT

Two space shuttle-era spacewalkers enter Astronaut Hall of Fame

"Two astronauts whose careers embody excellence, leadership, and service."

23 May 2026 11:30am GMT

China’s shark finning could lead to US seafood sanctions

A formal petition to the US government calls for sanctions on Chinese seafood imports.

23 May 2026 11:00am GMT

22 May 2026

OSnews

Migrating from Ubuntu 16.04 to FreeBSD

Bruno Croci's blog had been running on Ubuntu 16.04 for a long time, well past the Linux distribution's expiration date. As such, it was time to upgrade, but instead of opting for something standard like another Ubuntu release, he opted for FreeBSD instead. This blog has been running on a Digital Ocean VPS for over ten years. A machine hosted in New York City, running Ubuntu 16.04 LTS. An LTS that hasn't been in support for at least 5 years. It was about time to change it. After some considerations, I migrated to a Hetzner virtual machine that is way better than my old Ubuntu one, less than half the price of what I used to pay, and just across the country from me. Not only that, but I took the challenge to move my stack to FreeBSD. It's a long text, but stay for a cool introduction of FreeBSD Jails with Bastille and some interesting site load benchmarks. ↫ Bruno Croci I absolutely adore the recent surge in people (re)discovering the BSDs as a valid alternative to Linux in both the server and desktop space. In this particular case, it was FreeBSD's Jails and ZFS support that won Corci over, and it's easy to see why. While there are countless alternatives to Jails in the Linux world, ZFS is harder to come by as it can't be part of the kernel due to licensing issues. With how powerful and capable ZFS is, it makes sense to want to use it on your server, and in that case, FreeBSD is probably a better choice than most Linux distributions. There are countless reasons to choose one of the BSDs over a Linux distribution, and I'm glad we're seeing an uptick.

22 May 2026 7:00pm GMT