fidzu : geek

Stack Overflow's senior VP of community says predictions of their demise "make for compelling headlines, but they confuse a change in how people access knowledge with the disappearance of the knowledge - and the company - behind it. AI has changed developer behavior. In our recently released 2026 Developer Survey, 64% of respondents said they visit Stack Overflow less frequently for simple questions. But developers also report asking more advanced questions and visiting the site to verify AI-generated answers. Stack Overflow remains a place where people can challenge assumptions, compare approaches, and validate solutions. But it's also important to understand that our public Q&A site is only one part of Stack Overflow, the company. The knowledge created on the Q&A site helps power the AI ecosystem itself. Stack Overflow's human-validated content is used to train and improve models, strengthen retrieval systems, and make AI assistants and other tools more reliable. Developers and technologists may encounter an answer through a different interface - such as their IDE - but the underlying knowledge may still have begun the same way it did in the past: with a developer sharing what they learned on Stack Overflow. We're also building for what comes next. We recently launched the beta of Stack Overflow for Agents, an API-first knowledge exchange where agents can share knowledge and verify solutions. We also brought back Developer Story, giving developers a verifiable way to showcase their expertise, accomplishments, and contributions beyond a traditional résumé. And we have much more planned and in development to give people compelling new reasons to visit the site beyond Q&A. Several years ago, we pivoted aggressively toward the enterprise. In September, we launched the next generation of Stack Internal, our governed AI context layer for companies. It captures and curates organizational knowledge, adds provenance and trust signals, and brings in subject-matter experts when validation is needed. The goal is straightforward: to make sure employees and AI agents are working from accurate, current, permission-aware information - not confidently acting on whatever context happens to be nearby. That is the thread connecting everything we do: making human knowledge useful and trustworthy, whether it is being consumed by another developer, an enterprise team, or an AI agent. Stack Overflow is not standing still, and it is not disappearing. We are evolving from a website people visit for answers into knowledge infrastructure that supports developers, companies, and AI systems wherever they work. Reports of our death are, indeed, exaggerated.

Read more of this story at Slashdot.

02 Nov 2026 12:34am GMT

Toyota's EV sales have jumped 127% through September, reports Electrek: Including Lexus, Toyota sold 309,766 battery electric vehicles (BEVs) globally through the first nine months of 2026, up 127.4% from the same period last year. Except for January (+87.5%), Toyota's EV sales have more than doubled every month this year compared with 2025... While its EVs are catching on, Toyota Motor's global sales fell for the third straight month in September. Toyota sold 860,107 vehicles in September, down 2.2% from the previous year. The company said that although overall demand remained steady, sales in China fell, leading to lower overall sales than last year. Through September, Toyota sold 7.51 million vehicles globally, down 3.4%. In China, Toyota's sales plunged nearly 20%, marking its eighth consecutive month with lower sales. Toyota said the overall market in China "remained weak due in part to rising gasoline prices, while the market for gasoline vehicles and hybrid vehicles was particularly affected," resulting in lower sales. In the first nine months of 2026, Toyota sold just over 1.05 million vehicles in China, 18.9% fewer than in the same period last year... After the US, China is Toyota's second-largest market.

Read more of this story at Slashdot.

01 Nov 2026 11:36pm GMT

SystemD creator Lennart Poettering left Red Hat for Microsoft in 2022, but 10 months ago left to co-found Amutable a company that aims to build cryptographically verified Linux systems that stay trusted over time. It's FOSS calls it "a read-only, image-based system where every machine produces signed reports of its own state" - and signups are now open for a private preview: Before announcing this Linux-based implementation, Amutable had released two open source tools. tine, a Buck2-based build system that composes OS images; available under MPL-2.0, and Quarry, a TUF-based tool that distributes those images to machines; available under Apache-2.0. What Amutable Foundations brings to the table is a service where Amutable runs the images, update repositories, control plane and vulnerability fixes for organizations and individuals who operate their own systems. No license has been stated for those company-run parts, and the preview announcement does not say how much of Foundations beyond tine and Quarry will be open source. Software and configuration both ship as signed images, and a machine boots only what is signed. Because there is no package manager and no SSH or interactive shell, a change means giving every machine in your fleet a new signed image. Its images are reproducible, come with a software bill of materials (SBOM) and are built from pinned inputs of whichever distribution you pick, with tine being able to import packages from Fedora or CentOS Stream. Each machine sends a signed report that records what it booted, from the firmware and boot loader up to the kernel and OS, plus the configuration it runs... Amutable's control plane verifies reports from systemd-report, an experimental command in systemd 260 that the company helped build. It compares each one with the declared state and flags machines that deviate. A rollout only continues while machines can show they are in a good state... Amutable is signup formlooking for teams that manage Linux fleets and need to show what state each machine is in. It expects to start bringing the first 'design partners,' as it calls them, on board over the coming weeks.

Read more of this story at Slashdot.

01 Nov 2026 10:33pm GMT

A long flight home from feeding grounds messes with birds' internal clocks.

31 Oct 2026 11:15am GMT

The regulator says Tavneos was approved on the basis of manipulated study data. Should patients still have access to it?

31 Oct 2026 11:02am GMT

Sculpt OS 26.10 brings quite a few new features, like scalable cursors, support for UK keyboards, better webcam support, and more, but the real meat of this release is much tastier. First, Sculpt 26.10 is the first version based on Genode's custom microkernel instead of relying on a 3rd-party kernel. This kernel - designed from the ground up for the needs of Genode and Sculpt OS in particular - is not only more "micro" than any other of the microkernels supported by Genode, it also solves long-standing deficiencies concerning CPU scheduling and kernel-memory management. Sculpt OS finally stands on Genode's own footing! Finally, Sculpt OS 26.10 pays tribute to this year's overall theme of "building bridges" by featuring our software development kit (Goa SDK) running directly on Sculpt OS without virtualization. This entails a wealth of tooling including GCC, Binutils, Git, Sequoia, Expect, Curl, man, Make, and CMake having landed on Genode. Although still young and not time-tested yet, it shows what's possible today and allows us developers to gradually shift more and more development routine into this self-hosted environment, stressing the general-purpose qualities of Genode and motivating further optimizations. ↫ Sculpt OS release 26.10 announcement This new release also completes the transition from XML to Genode's own HID language for configuration, moves from VirtualBox 6 to 7, and upgrades a whole slew of its Linux-based drivers

31 Oct 2026 8:02am GMT

Raymond Chen published another story from the Windows development trenches, this time about what happens when you hold down the power button. If you hold a PC's power button for 12 seconds, it will turn off at the hardware level without notifying the operating system. This is a safety feature so that you can turn of the computer even if the operating system's "Shut down" command isn't working. After eight seconds of the power button being held down, the Windows kernel realizes that the user is trying to do a force-power-off of the system, and it quickly takes a kernel dump that can be uploaded to the Windows Error Reporting service the next time you turn the system on. ↫ Raymond Chen I'm a bit confused by these numbers, because I have never seen a PC take this long to power off when holding down the power button; usually it takes only a few seconds to do so, meaning Windows would never generate said kernel dump. I tried reading through the various ATX specification documents to find more information on this, but then I remembered I'm not an electrical engineer so I have no idea what I'm looking at. The baseline is that ATX always provides standby power to the motherboard, and pressing the power button shorts the power button pin to ground, telling the PSU to power on fully. Pressing the power button if the computer is running tells the operating system to initiate a shutdown (although you can change this behaviour), but if you hold the button down for a certain number of seconds, it forces a power-off. So far, so good; basic information. It seems that the length of time you need to hold down the power button to force a power-off is dependent on the motherboard in question, handled by a microcontroller or some other IC. Virtually every source I can find says this timing is set to about 4-5 seconds, which is quite a bit shorter than the number of seconds given by Chen. Perhaps motherboard manufacturers consider the 12 seconds to be too long, and just do their own thing, regardless what the ATX specification suggests? What further complicates matters is that Chen details how the kernel dumps created after pressing the power button for 8 seconds do, in fact, get sent to Microsoft once the computer turns on again. In fact, he is one of the people who gets to see these dumps and respond to them, so obviously they are indeed rolling in. Does this mean there's a huge number of computers out there that require you to hold down the power button for 12 seconds to force a shutdown that nobody's ever seen? These emergency kernel dumps are internally classified as "long power button hold" (LPBH) failures. One of the pieces of information recorded in these emergency kernel dumps is whether the screen consists entirely of black pixels. Those failures are sub-classified as "black screen LPBH", and they go to a special virtual team for analysis. (I happen to be a member of this black screen LPBH team.) ↫ Raymond Chen What's going on here? Obviously, I'm not going to doubt Chen, so there must be something here I don't quite understand or that I'm missing. The ATX specification might suggest 12 seconds, but could Windows perhaps adapt its kernel dump behaviour - dumping much sooner than 8 seconds - based on the motherboard it's running on, maybe through information provided by the chipset drivers? I would love it if someone more knowledgeable than me can help us unravel this small mystery.

31 Oct 2026 7:54am GMT

From curl 8.12 through 8.16, config files could slice variable values and include other config files without an explicit depth cap. Together, these features let curl simulate any two-counter Minsky program. Under the usual idealization of unbounded strings and resources, this construction was Turing-complete. Curl 8.17.0 added a five-level include cap that breaks this reduction. ↫ Nicolas Seriot Neat.

31 Oct 2026 7:10am GMT

The space agency solicited ideas for reboosting Hubble four years ago, but they didn't go anywhere.

31 Oct 2026 12:07am GMT

This is a story of how we got from something like this: Failed to deserialize BUILDINFO file: Parser failed with the following error: unknown ^ invalid makepkg build environment option expected `buildflags`, `ccache`, `check`, `color`, `distcc`, `sign`, `makeflags` To this: When the ALPM project started, the goal was fairly simple: Better tooling to interact with the low-level plumbing of Arch Linux Package Management (ALPM). This meant binaries to read/write individual file types, better error messages, extensive specifications and of course exports to common dataformats like JSON. The thing is, although some of us already had experience with low-level dataframe parsing, …

08 Oct 2026 12:00am 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

Good morning from JetBrains Berlin office!

01 Jun 2026 12:00am GMT