fidzu : computers

About 90 percent of the distance driven by Perseverance has been autonomous.

08 Aug 2026 11:30am GMT

Open source WeatherNext model can make accurate predictions with lower-resolution weather data.

08 Aug 2026 11:05am GMT

NASA has squeezed at least another year of science out of Voyager 2 by cutting power to nonessential systems and switching to lower-power alternatives. Voyager 1 is expected to receive the same power-saving changes in the coming months. Space.com reports: Voyager 2 and its twin launched in 1977, called Voyager 1, rely on a form of nuclear battery known as a radioisotope thermoelectric generator that uses the heat produced by the decay of plutonium. But the supply of plutonium on each probe drops at about four watts a year on each spacecraft. To keep the probe running on this dwindling power supply, engineers recently reduced Voyager 2's power requirements by turning off a few non-science devices and using "lower-power alternatives" that are still effective enough to keep the spacecraft warm while it's so far from the sun, NASA officials said in a statement. "The spacecraft power margins have grown razor thin, requiring the team to conserve energy by shutting off non-essential devices and systems," NASA officials wrote of the mission, which is managed by the agency's Jet Propulsion Laboratory. The drop in power is having a measurable science impact on both spacecraft -- each has turned off two of their science instruments since 2024 alone. While some of these instruments were shut off after the spacecraft finished their historic planetary flybys decades ago, others were turned off due to power requirements. Each spacecraft initially launched with 10 instruments, and Voyager 2 is now down to only three instruments. At first it looked as though Voyager 2 would have to shut down another of these instruments later this year, but luckily, the new power shifts will allow all three to operate "for at least another year," NASA said.

Read more of this story at Slashdot.

08 Aug 2026 11:00am GMT

The police surrounded her car Thursday, "drew their guns, and told her to come out with her hands up," reports a local news station. The police thought they were pulling over a murder suspect, but "It turns out it was a mistake by another department with the Flock license plate reader technology." The black woman says she'd wanted to call her mother, "but I'm like, if I make a sudden move, it's going to be over. It's going to end my life." And amazingly, the same thing happened Monday, according to the local news report. "Milwaukee police pulled her over with guns drawn. She says officers never explained why, towed her car, and let her go." She now describes herself as "traumatized," recalling her second detention by police on Thursday. "After they put us in cuffs, they walked us to the car. I'm not knowing what's going on. I'm scared. All you see is people in their cars recording." She now says she's scared to drive her car, and so is her daughter. "Because she doesn't know if the police are going to pull us over and do it again..." "I haven't been to sleep since this happened. Every time I close my eyes, all I can see is guns." She wants an apology, since the local police would only say it wasn't their fault, it was the fault of the Milwaukee police department that failed to remove the alert from Flock's system. "Milwaukee police emphasized this was not a Flock camera issue, it was a data entry mistake," according to the local news report. The woman's response? "Y'all failed. Y'all failed the system. Y'all failed me. Y'all failed everybody."

Read more of this story at Slashdot.

08 Aug 2026 7:00am GMT

An anonymous reader quotes a report from the BBC: German energy company RWE has said it will abandon its offshore wind projects in the U.S. after reaching a $1.2 billion payout deal with President Donald Trump's Department of the Interior (DoI). RWE said that it will now reinvest the sum into conventional gas projects, including $900 million in a liquefied natural gas (LNG) export terminal project in Louisiana. "After careful consideration, it was determined there is no path forward to permit these projects in the US for the foreseeable future," the company said in a statement. RWE said it has agreed to relinquish its leases off the California and Louisiana coasts as well as in the New York Bight. Overall, the German firm plans to invest approximately $19.6 billion in the U.S. over the next six years "to grow its generation capacity." Interior Secretary Doug Burgum said in a statement posted on X that Americans deserve an energy system built on common sense and not one dependent on "costly subsidies." "We welcome RWE's agreement and voluntary investment in projects that strengthen our nation's energy security," he added. Earlier this year, the DOL reached a deal with TotalEnergies putting an end to the French company's offshore wind projects in the U.S. "Instead, the firm agreed to reroute investment to build a LNG plant in Texas and to develop 'upstream conventional oil' in the Gulf of Mexico," reports the BBC. Another similar deal was signed with Charlotte-based Duke Energy last month to terminate the company's offshore wind lease in the Carolina Long Bay area.

Read more of this story at Slashdot.

08 Aug 2026 3:30am GMT

Copernicus Browser adds wildfire visualization amid record wildfire season.

07 Aug 2026 9:48pm GMT

There's been a small flurry of articles from a variety of sources, all talking about more or less the same thing: Microsoft is trying to explain why Windows 11 is as difficult to develop as it is, in turn justifying why it's become such a mess over the years. I'm picking this one from Windows Central, which is an interview with Microsoft's CVP of Design and Research for Windows and Devices, Marcus Ash. Taking the long, still ongoing transition from the Control Panel to the Settings application as an example, Ash explains why this is such a long and difficult process. Unsurprisingly, Ash says that the reason this has taken so long is that Microsoft prides itself on compatibility with legacy tooling and workflows, so it can't just rush in and modernize everything without first ensuring the modern replacements maintain functionality with what came before. ↫ Zac Bowden at Windows Central This isn't really news to anyone. One of Windows' prized strong points is its often excellent backwards compatibility. This doesn't just apply to individual applications, but also to things like software makers adding settings panels to Control Panel, or complex business applications expecting certain entry points into the Control Panel to exist - and much, much more, all over the operating system. I'm exaggerating, but you can't so much as move a single pixel in the taskbar without breaking some component of some obscure corporate middleware suite from 1999 that somehow still functions as the beating heart of like 187 Fortune 500 companies. Sometimes I wonder if Microsoft is going about this the wrong way entirely. Of course, I have no idea what I'm talking about, but I feel like Microsoft has so man tools at its disposal to deal with this issue that it's not really using to their fullest potential. Specifically, Windows itself has a number of incredibly capable tools in its toolbox to make sure any application ever written for Windows and even DOS, regardless of how many bits it requires, can run. Windows has advanced and highly capable tools for virtualisation and containerisation, and on top of that, Windows NT has a very capable personalities system that feels underutilised, too. Couldn't these tools be harnessed to effectively isolate the entire backwards compatibility problem from the actual Windows operating system people use, and turn them into optional components installed and activated when required by an older application? Isolating backwards compatibility this way would then leave the Windows team much less shackled and more free to improve Windows at every level without having to worry so much about maintaining backwards compatibility. If the components an older application needs are virtualised, containerised, or part of a Windows NT personality and thus frozen in time, the Windows team would be free to work on the "current" version of said component without breaking the application in question. I feel like Microsoft has tried to use these technologies to address backwards compatibility in the past, but in true Microsoft fashion, it always seems to do so halfheartedly, without any real coherent vision behind it. Again, I wish to reiterate I'm by no means qualified enough to make any definitive statements about this, but it sure does feel like Microsoft is underutilising a lot of the tools it already has at its disposal.

06 Aug 2026 10:20pm GMT

Once upon a time in the mysterious lands of Mexico, starting in Fall 1996 and through Spring 1997, I coded a windowed operating system in 32-bit machine code, fit it into a floppy, and jumped in excitement as it boot up. Of course, I knew it was a great thing because you couldn't boot Windows 3.1 or GEM from a floppy disk, but I was very far from knowing how so cool it was. Unfortunately, not a thing I could give away for everyone to see, as it was written for a homebrew computer based on the Am29000 processor. Let's go back to my memories, some notes, and the ride of discovering again what I forgotten. ↫ Óscar Toledo Gutiérrez Trying to summarise this absolute gem of an article and all of the amazing effort and skill involved would be a huge disservice to Óscar Toledo Gutiérrez. I enjoyed this so much. Be sure to try out his custom emulator of a custom computer to run his custom operating system.

06 Aug 2026 9:28pm GMT

Two years ago, I was Porting my JavaScript Game Engine to C for No Reason. I have since found a reason: making a new N64 game! The result is Xibalba 64 - a Wolfenstein 3D-like FPS. Modretro agreed to publish the game as a physical launch title for their M64 (a modern N64 clone), complete with cartridge, packaging and manual! ↫ Dominic Szablewski The article details the development process, from setting up the correct tooling to actually getting the game to play on a real Nintendo 64, and everything in between - including optimising the game to get it to run at a steady 60fps. The biggest issue is that the Nintendo 64 is quite a complex and quirky console, and in order to develop for it, you needed access to Nintendo's officially sanctioned platform library, libultra. These days, though, there's an open source alternative, libdragon, enabling homebrew development. It's awesome that, thanks to the hard work of volunteers, people can still develop top-notch games for something like the Nintendo 64. If we had left it up to Nintendo, we'd be seeing nothing of the sort today.

06 Aug 2026 9:06pm GMT

This is just a short note on my blog that I have resigned from Arch Linux a package maintainer, developer and security team. I've spent around 10 years as an AUR maintainer, security team, Package Maintainer and then Developer. I implemented support for debug packages, did the initial POC work that would become the git migration and even somehow managed to pull of an online conference during The Plague with the help of others.

01 Aug 2026 12:00am GMT

Good morning from JetBrains Berlin office!

01 Jun 2026 12:00am GMT

Just trying to answer one simple question: What if the terminal was 3D?

11 May 2026 12:00am GMT