fidzu : computers

Should generative AI be used for videogame development? Brandon Stirrup, a strategy manager at Xbox, claims Xbox is already using AI, reports Engadget. And he also says that those who say they aren't are merely "pretending." Stirrup deactivated his social media account shortly after (though his posts have been archived elsewhere), igniting conversations about what role generative AI actually has or should have in game development. In some ways, it would be unsurprising to learn that Xbox is using AI to the extent that Stirrup implies. Xbox recently announced the formation of Xbox Labs at least in part as a response to a rising trend of AI-coded game ports; the announcement heavily implied that the new team would use AI as well but didn't say it outright. Xbox owner Microsoft is also a major player in AI development... Developers including Capcom, Square Enix, Sega, Nexon and Activision have all either used AI in their games or pledged to do so. Fortnite developer Epic Games has been particularly up-front about its AI use, and CEO Tim Sweeney has aggressively promoted it on social media... On the other hand, there are large pockets of the game industry vocally opposed to generative AI. Notably, these tend to be smaller, independent studios without shareholders to impress by touting the cost-savings of AI. These studios include Tunic publisher Finji, Stardew Valley developer ConcernedApe and Clickolding developer Strange Scaffold, among many more. Due to the sheer number and variety of game studios, it's impossible to say just how much of the industry actually uses AI at this point, but claims that "everyone" is using it are clearly false. There's a similar divide among players about whether generative AI should be embraced or avoided at all costs. While some simply accept AI as part of games going forward, others have pledged to avoid games that use the technology outright due to its environmental costs, labor issues or pure aesthetic preference. That's led to the popularity of tools like a browser extension that makes Steam's AI disclosures more visible and grassroots efforts by developers to implement labels certifying their games as AI-free... Many players and developers alike justify the use of AI in generating code, even if they're opposed to it in other areas. "Gaming is the only industry slow-walking the transition," Xbox's Stirrup allegedly said, "because users have negative sentiment. Everyone else accepts reality." "Gaming is the only industry pretending to not use AI."

Read more of this story at Slashdot.

01 Nov 2026 4:34am GMT

"We've now replenished 90% of the stolen assets, and we're committed to covering the remaining 10%," Binance co-CEO Richard Teng posted on X, adding that "Our users will not bear the financial impact of this incident." "Binance said it was able to replace the funds taken in the record hack by using company money to buy new tokens," reports NBC News: The remaining 10% consists of tokens that are less liquid, meaning they may take longer to buy, it said in a statement posted on X... Binance said it has set aside around $6.34 billion of company funds internally to cover the losses. The money spent re-buying tokens came from using part of its $1 billion Secure Asset Fund for Users, a bitcoin reserve it holds to protect customers in the event of security breaches, as well as some of its Futures Insurance Fund, and the company's own corporate treasury, it said on X. NBC News reports that the FBI blames the breach on a North Korea-sponsored group known as TraderTraitor: Members of [TraderTraitor] were observed by law enforcement converting stolen assets into the cryptocurrency ethereum, the FBI said in a statement, adding that it expects "further laundering" of the assets through the use of related technology... After the hack, the exchange stopped allowing customers to withdraw their funds, but it said Saturday it was still on track to reopen withdrawals Sunday. CNBC reports: The world's largest crypto exchange initially said the hack may involve "a compromised DevOps engineer's laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions." However, Co-CEO Richard Teng later said the attack involved a more complex process rather than the misuse of a single engineer's permissions. The New York Times describes what happened when Binance first spotted "a multibillion-dollar deluge of digital coins" pouring out of its accounts: As the news spread, Binance's top executives put together an informal war room on Wea, the company's internal messaging system, with about 100 participants, including specialized cryptocurrency tracers and security personnel. They eventually transitioned to a mass conference call, with 100 boxes on the screen, where employees took turns muting and then unmuting, communicating in a mixture of English and Chinese. Among them was He Yi, Binance's co-chief executive, who is seven months pregnant, and worked through the night from her base in Abu Dhabi, taking a call at 3 a.m. local time.... Much of the drama played out in public. Almost all crypto transactions are recorded on the blockchain, a ledger of money movements that anyone can look up. That meant crypto analysts could see funds leaving Binance in real time... North Koreans have targeted crypto companies for years, using the proceeds of those thefts to fund its nuclear program, according to Western officials. The hackers have developed increasingly complex strategies to steal crypto and launder the proceeds, a painstaking endeavor that can take months to complete. In a blog post on Friday, Chainalysis said the attackers had deployed "laundering patterns we have not seen before," conducting thousands of transactions over a short period, probably with the help of automation. At the same time, Binance's colleagues in the industry mobilized to intercept some of the laundered crypto. Certain digital coin issuers can freeze funds, allowing them to halt a money-laundering operation in its tracks. Soon after the hack, Tether and Circle, two major issuers, announced that they had frozen stashes of their own coins that the hackers had seized from Binance, a combined total of more than $2 billion in crypto. Binance is now working to gain access to those funds, the company said. But $2.4 billion in crypto is already "beyond any issuer's reach," according to [blockchain intelligence firmm] TRM. The article also includes President Trump's reaction when asked Friday about the breach. "I've always felt it was a little bit dangerous. But they say they have it pretty much under control. We'll see."

Read more of this story at Slashdot.

01 Nov 2026 1:34am GMT

CNN reports: The popular theory that comets were crucial in kick-starting life on Earth billions of years ago may not hold up, according to new computer simulations that counter decades of scientific thinking. The finding suggests the fragile organic molecules supposedly carried by the icy objects would have been destroyed on impact, upending an established origin of life theory that dates back to at least 1961 [with earlier versions postulated in 1908]... Early in its history - over 4 billion years ago - Earth may have experienced a period of heavy bombardment from more than 100,000 comets larger than 100 meters (328 feet), according to the new study, published Wednesday in the journal Scientific Reports. Those impacts, however, were mostly too heavy for life-starting molecules to withstand. The team used the latest models of comet formation and evolution to simulate this early planetary period 100,000 times. "Given what we know about surface environments on the early Earth, on average, our simulations found that there were no successful impacts," said lead study author Richard Anslow, who conducted the research while completing his doctorate at the Institute of Astronomy of the University of Cambridge in the United Kingdom... "The typical velocities of these comets when they impact the Earth meant that actually very few, if any, would have been able to deliver intact organic molecules, so comets actually don't seem to be as useful for prebiotic chemistry as was previously thought," Anslow said. More precisely, 54% of the simulations showed no impact at all, while the remaining 46% had at least one and a "tiny minority" returned up to three collisions, Anslow said. "We can't rule out confidently that there was never a successful impact - there could have been one of these fluke impacts." However, such flukes had to occur in a "perfect location" that already met several important conditions, including the presence of liquid water and other chemicals needed to support life. That combination makes the overall process unlikely, he added. The article notes his argument that even if a successful impact occurred, it's unlikely an important chemical like hydrogen cyanide (HCN) could survive the impact, and would've dissolved in an ocean impact. Plus, "many other precursor molecules are also needed, such as compounds that contain phosphorus and sulfur, but these are not routinely found in comets, Anslow said." An alternative cosmic source of organic material could have been asteroids, which typically struck Earth more slowly and in greater numbers. Anslow pointed to recent findings on samples from asteroids Bennu and Ryugu, which contain the majority of protein-building amino acids. The recent study also raises another intriguing possibility: While Earth may not have had the ideal conditions to foster HCN from comet impacts, ancient Mars might have been better suited. "Because Mars is much smaller than Earth and further away from the sun, the typical impact velocity of comets is much lower, so while these impacts on Earth were destroying most of the HCN, this wasn't the case so much for Mars," Anslow said. This idea could add another dimension to the long-standing question of whether the red planet once supported life. While the authors closely analyzed how HCN could have survived comet impact, the chemical may have undergone reactions before the icy bodies entered Earth's atmosphere, said Queenie Chan, an associate professor of Earth sciences at Royal Holloway University of London, who was not involved with the study. This process could have created biologically important compounds, such as those protein building blocks, that are less volatile and more likely to survive.

Read more of this story at Slashdot.

31 Oct 2026 9:50pm 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