fidzu : computers

An anonymous reader shares this report from Space.com: On Saturday evening (Aug. 15), SpaceX set another mark, for the shortest time between orbital flights: It launched two Falcon 9 rockets just 38 minutes apart, besting its old mark - set on Aug. 31, 2024 with two Starlink missions - by 27 minutes. The first liftoff, from Florida's Cape Canaveral Space Force Station, occurred Saturday at 9:12 p.m. EDT (0112 GMT on Aug. 16) and carried eight satellites to low Earth orbit (LEO) for Louisiana-based telecom company Globalstar. All eight spacecraft were deployed successfully, separating over a six-minute span beginning 56.5 minutes after liftoff, SpaceX announced via social media. While that Falcon 9 was powering its way to low Earth orbit, another one launched from Vandenberg Space Force Base, on California's central coast. That liftoff, at 9:50 p.m. EDT (6:50 p.m. local time; 0150 GMT on Aug. 16), kicked off a mission for the U.S. Space Force called USSF-366... Both of Saturday's missions featured successful rocket landings. The Falcon 9 first stage that launched the Globalstar mission came back for a touchdown at Cape Canaveral about eight minutes after launch. It was the 14th flight for that particular booster. The USSF-366 Falcon 9 first stage, meanwhile, came back to Earth about 8.5 minutes after its launch, touching down in the Pacific Ocean on the SpaceX droneship "Of Course I Still Love You." That booster now has 18 missions under its belt. Saturday's doubleheader brought the tally of Falcon 9 launches in 2026 to 96. The vast majority of those - about 75% - have been Starlink missions.

Read more of this story at Slashdot.

16 Aug 2026 7:34am GMT

Phys.org reports: Future fusion power plants aim to recreate the heart of a star here on Earth to power our future energy needs. While the core fusion plasma will burn at hundreds of millions of degrees, the surrounding structural components must handle sudden, punishing heat loads that rival the extreme temperatures faced by spacecraft upon reentry into Earth's atmosphere. Copper and its alloys are primary candidates for handling these intense heat fluctuations, making it vital to understand exactly how the metal behaves when pushed to its melting point. Now, researchers at the Department of Energy's SLAC National Accelerator Laboratory and collaborators have captured a detailed, step-by-step look at copper atoms as they underwent extreme heating. Published in Nature Communications, the results revealed a key parameter that allowed copper's crystal lattice to melt steadily rather than collapse instantaneously, as earlier simulations predicted. "These results greatly improve the simulations we use to predict which materials have the best shot at surviving the extreme conditions of future fusion reaction chambers," said Mianzhen Mo, a SLAC staff scientist who led the research. "They also demonstrate the incredible, atomic-scale resolution imaging we can achieve at SLAC's electron camera...." Researchers use computer simulations, aided by AI and machine learning, to sift through innumerable combinations of elements and identify promising candidate materials for real-world testing. "Whether the copper melts slowly or suddenly collapses, by the time the researchers look, the sample resembles nothing more than a metallic brown puddle," the article points out. But SLAC's powerful electron camera captures atomic and molecular movements down to the femtosecond - a millionth of a billionth of a second - and revealed that at around 1,424 degreesC (2,595 degreesF) there was still gradual melting as the temperature rose beyond the superheating limit, with real-world conditions showing the atoms shifted and retained some order. "It's a straightforward solution," said Mianzhen Mo, a SLAC staff scientist who led the research. "But molecular dynamics simulations had been overlooking it for years. When you have complex simulations attempting to capture every aspect of reality, down to individual atoms, it takes real-world data to show you what's missing from the calculations."

Read more of this story at Slashdot.

16 Aug 2026 4:45am GMT

An anonymous reader shared this report from TechCrunch: X is significantly expanding its open source codebase, which includes the app's "For You" algorithm and its core ranking engine, and adding a feature that will let users see if their account or posts have been impacted by any of its ranking systems, the social network said on Thursday. The company is making the source code for the "For You" timeline, the default feed you see when you open the app, available on GitHub under the Apache v2 license. It's also expanding its previous efforts to open source parts of its codebase to add more detail, including the model configuration, filter, and core ranking system details. That means it includes the parameters used to weight different signals - key to understanding which posts are actually displayed. This also makes the codebase roughly 10 to 15 times larger than it was before. "You'll get the core ranking code that pulls posts and ranks them for any given user and assembles the feed," X's VP of Product Keith Coleman told TechCrunch in an interview ahead of the announcement. "You can see the systems that filter out potentially problematic, rule-violating content...And some of those systems, like the ranker and the score, you can even run yourself outside the company." "This is the kind of thing that I think people will be fairly shocked that we are releasing," he added. In addition to the repository, X is providing tools that will let users see for themselves if and how X's ranking systems have impacted their account or posts. A new transparency tool is rolling out to an "Under the Hood" page in the app's settings, which will let users who have posted 10 or more times over the past month download their aggregate stats as a JSON file. The file will show if any labels have been applied to their account or posts over the past calendar month. X's VP of Product told TechCrunch that X engineers will consider pull requests. "That would be amazing to have people submitting code that improves the algorithm...I mean, how cool would it be for the X algorithm to be not just visible to the public, but also, like, by the public?"

Read more of this story at Slashdot.

16 Aug 2026 2:25am GMT

Also: Ahsoka S2 teaser, Doomsday trailer, news about MCU's X-Men and Star Wars: Starfighter

15 Aug 2026 9:21pm GMT

"Flamingo missiles were used. A good achievement."

15 Aug 2026 3:46pm GMT

Utility-scale solar leads by a mile, followed by batteries. Fossil fuels, not so much.

15 Aug 2026 11:09am GMT

Today, you can get low-quality knockoffs of just about any popular smartphone on sites like AliExpress or Temu, whether they be iPhones, Galaxy phones, or whatever else. They have terrible build quality, bottom-of-the-barrel components and specifications, and all run outdated versions of Android - badly. At the same time, various consumer electronics brands, once popular in a bygone era, sell the rights to their brand name to unknown companies, who then put these brands on generic hardware to give their products a sheen of legitimacy. That's why today, you can still buy Nokia smartphones, Polaroid cameras, and low-effort Hi-Fi equipment from various once-respected brands. None of this is new, however. In the late '90s and early 2000s, companies were already doing the same thing. In fact, there's one device from this era which combines both business practices - it's both a cheap knockoff of a wildly successful device, and it carries a once-revered brand name. Also, just to add some juice, this story involves stolen source code. Let's take a look at the worst PDA of all time, the Olivetti daVinci. In 1997, Palm launched the Palm Pilot, and it and its successors proved to be a massive hit. Where countless before it had failed, Palm found the magic formula to make pocket computing work. I wrote an in-depth article about Palm over 13 years ago which goes into much (much) more detail, but the reason the Palm Pilot succeeded where things like the Newton, PenPoint OS, and Windows for Pen Computing failed, is that Palm's founder, Jeff Hawkins, realised that they were competing with paper, not with desktop computers. Instead of trying to shove the capabilities of a full personal computer into a (barely) pockatable device, a pocket computer had to be as fast and convenient as paper, and therefore extremely strict about which features to add, and which to omit. To this day, the entirety of smartphone computing stands on the shoulders of Palm. Palm's ideas, implementations, approaches, paradigms, and even people were absorbed by Apple and Google, where they shaped both iOS and Android. The phone you're looking at right now has a ton of Palm DNA in it, still. After all, you're still using the homescreen-with-apps paradigm Palm already perfected in the late '90s and early 2000s. The success of the Palm Pilot and its successors did not go unnoticed. Microsoft, most prominently, felt incredibly threatened by Palm's success: The success of Palm's products got the attention of Microsoft, and the company pretty much announced it was going to crush Palm. According to Hawkins, Microsoft had a sales conference, where, at some point, a big target appeared on the projector screen, with the Palm logo dead in the centre of it: "we are going to crush and kill these guys", was the central message. Hawkins recalls that he got condolence letters after that, stating things like "Sorry Jeff. Too bad." ↫ Thom Holwerda While Microsoft proved to be unable to "kill and crush" Palm, it did manage to build a relatively successful business selling PDAs running various incarnations of Windows CE. Together, Palm and Microsoft dominated the PDA market pretty much throughout its entire existence, and while the market was a mere fraction of the smartphone market of today, other companies still wanted a piece of this pie too. One of these companies was Olivetti, a storied Italian company with a long history making typewriters, computers, and other electronics. I'm not going into detail about Olivetti's history, but the company was renowned for its attention to design, creating iconic products like the Lexikon 80, Lettera 22, Elea 9003, Programma 101, and so, so many more. Olivetti also entered the personal computer market, first with a variety of custom machines featuring Z80 and later Motorola 68000 processors running a variety of custom operating systems developed by Olivetti (including its own UNIX variant, X/OS). After a few machines using MIPS and Alpha processors in the early '90s, the company would eventually focus entirely on Intel-based PCs (including this amazing failure) running Windows. Like so many other computer makers from that era, Olivetti eventually left the PC business by selling it off in 1997. To this day, Olivetti PCs tend to cost more on the used market than those from other brands, despite no technical merits dictating so. At around this time, our current story begins. Seeing the success of the Palm Pilot and the emergence of copycat devices running Microsoft's Windows CE, Olivetti wanted in on the action. And so, in the late '90s, the company introduced the Olivetti daVinci, a line of PDAs whose software looked suspiciously like Palm OS. There's not a ton of information out there about the development history, but it seems that while Olivetti designed the hardware, it contracted the development of the operating system out to a company from Hong Kong, Echolink Design. And this is where things went horribly wrong for Olivetti. The software Echolink Design developed for the daVinci didn't just look like Palm OS, it was Palm OS - at least, according to Palm. After being on the market for about a year, the Palm Pilot maker, then a subsidiary of 3Com, filed for an injunction, alleging that the daVinci operating system designed by Echolink Design contained actual Palm OS source code. In addition, Palm also filed suit against CompanionLink Software, the company that developed the Outlook synchronisation software for the daVinci. Palm won handily, and within a day of the filing, temporary restraining orders were put in place on both Olivetti and CompanionLink, stopping sales of the daVinci and its software dead in its tracks. It seemed to have been a pretty clear-cut case. From The Wall Street Journal at the time: U.S. District Judge James Ware ruled Olivetti's Royal daVinci organizer contains software that appears to have been copied from the operating system for 3Com's Palm organizers. Judge Ware said a review by a software expert found the daVinci software contains private Palm code and even grammatical

14 Aug 2026 7:18pm GMT

In the last few days, I built a shoot 'em up game by embedding a tiny custom bytecode VM and rendering the graphics using a fullscreen pixel shader. The result is a 3kB Windows executable. This was done for Langjam Gamejam, a 7-day challenge where you create a programming language and then use it to build a game. The project combines several interests of mine: language tooling, game development, procedural graphics, and demoscene-style size constraints. The game jam format forced me to keep the scope small and explore new ideas. Also, it was fun! ↫ Laurent Le Brun In seven days, Le Brun created a brand new programming language, compiler, bytecode interpreter, a game written in the new language, and rendered it, ending up with a 3kB self-contained executable. It's amazing what humans can do.

14 Aug 2026 6:57pm GMT

A while back, when chatting with a colleague over their computer, I noticed that a logo did not look exactly the same as it did on mine. It looked thinner on theirs and more faithful to the original image. It was rendered at 15px; here is an upscaled version. If you squint, or take a step back, the one from Chrome looks thicker. A bit weird, but swapping the image for an SVG fixed it. Still, I was curious: why was it rendering like this in the first place? I did some digging and found a nifty optimization that Chrome uses when rendering JPEGs at small scales. ↫ Guillaume Técher I love it when people detail their discoveries like this.

14 Aug 2026 6:50pm GMT

Over the last few weeks, we have been doing research on the integration of our official distribution packages when installed on a target system. In this context we have been looking at the current uses of alpm-install-scriptlet(5) files and alpm-hooks(5) in around 120 package source repositories (alpm-source-repo(7)) to better understand the underlying functionality and use-cases these two integrations offer and target. In this article we are going to look at how these two systems work, how Arch Linux is currently using them and attempt to provide suggestions for when to use which. Learning about alpm-hooks(5) and alpm-install-scriptlet(5) files …

09 Aug 2026 12:00am 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