How a 20 year old bug in GTA San Andreas surfaced in Windows 11 24H2

https://cookieplmonster.github.io/2025/04/23/gta-san-andreas-win11-24h2-bug/

649•yett•5h ago

Comments

mschuster91•4h ago

To u/db48x whose post got flagged and doesn't reappear despite me vouching for it as I think they have a point (at least for modern games): GTA San Andreas was released in 2004. Back then, YAML was in its infancy (2001) and JSON was only standardized informally in 2006, and XML wasn't something widely used outside of the Java world.

On top of that, the hardware requirements (256MB of system RAM, and the PlayStation 2 only had 32MB) made it enough of a challenge to get the game running at all. Throwing in a heavyweight parsing library for either of these three languages was out of the question.

ceejayoz•4h ago

Vouching seems to be time-lagged and require more than one.

Magma7404•4h ago

The comment reappeared, and while you're right about using proper libraries to handle data, it doesn't excuse the "undefined behavior (uninitialized local variables)" that I still see all the time despite all the warning and error flags that can be fed to the compiler.

Most of the time, the programmers who do this do not follow the simple rule that Stroustrup said which is to define or initialize a variable where you declare it (i.e. declare it before using it), and which would solve a lot of bugs in C++.

mschuster91•4h ago

> it doesn't excuse the "undefined behavior (uninitialized local variables)" that I still see all the time despite all the warning and error flags that you can feed to the compiler.

Yeah but we're talking about a 2004 game that was pretty rushed after 2002's Vice City (and I wouldn't be surprised if the bug in the ingestion code didn't exist there as well, just wasn't triggered due to the lack of planes except that darn RC Chopper and RC plane from that bombing run mission). Back then, the tooling to spot UB and code smell didn't even exist or, if at all, it was very rudimentary, or the warnings that did come up were just ignored because everything seemed to work.

Yeask•4h ago

And it did not matter at all. The game shipped and was a success.

ryandrake•4h ago

This is the thing that drives artists and craftsmen to despair and drink: That a flawed, buggy, poor quality work can be "successful" while something beautiful and technically perfect can fail.

butlike•3h ago

The job of the artist is to take the years of expertise and distill it down into something "enjoyable." The hardest mental hurdle to get over is that people just don't care about the technicals being perfect. Hell, the final product doesn't even need to be beautiful; it just needs to be arresting.

RHSeeger•3h ago

Heck, sometimes the thing that's most interesting about a work is people arguing over whether or not it's art.

soulofmischief•3h ago

San Andreas might be rough under the hood, but on the surface it was nothing short of a masterpiece of game design. The engine was so complex and the cities felt alive, and the game could handle a lot of general nonsense. Still one of my favorite go-to games.

RHSeeger•3h ago

One artist can take months painting a picture of a landscape where everything is perfect. And the next artist can throw 4 colors of paint at a wall. The fact that lots of people enjoy the work of the second artist doesn't invalidate the work of the first. The two artists are focusing on different things; and it's possible for both of them to be successful at reaching their goals.

usefulcat•1h ago

Let's be clear that it was a success very much in spite of UB, not because of it. And there was still a cost--likely at least hundreds of person-hours spent fixing other similar bugs due to UB (if not more).

I worked in gamedev around the time this game was made and this would have been very much an ordinary, everyday kind of bug. The only really exceptional thing about it is that it was discovered after such a long time.

trinix912•3h ago

While it doesn't excuse the bad habits, we do have to keep in mind C++98 (or whatever more ancient was used back then) didn't have the simple initializers we now take for granted. You couldn't just do 'Type myStruct = {};' to null-initialize it, you had to manually NULL all nested fields. God forbid you change the order of the variables in the struct if you're nesting them and forget to update it everywhere. It was just considerably more practical to do 'Type myStruct;' then set the fields when needed.

badc0ffee•3h ago

You could always `bzero` or `memset` the entire struct to 0.

trinix912•3h ago

But only if it contains strictly POD members, otherwise it's UB.

mrighele•1h ago

I haven't been using C++ for a number of years but I think you could set the default values of fields even back then. Something like

    struct test {
        int my_int = 0;
        int* my_ptr = std::nullptr;
    };

Or is this something more recent ?

You cannot initialize them with a different value unless you also write a constructor, but it not the issue here (since you are supposed to read them from the file system)

kevin_thibedeau•4h ago

The flaw isn't the language. The issue is a 0.5x programmer not knowing to avoid sscanf() and failing to default and validate the results. This could be handled competently with strtok() parsing the lines without needing a more complicated file format.

butlike•3h ago

Worked fine on the target machines and the "0.5x programmer" got to see their family for winter holiday. Or are you saying they should have defensively programmed around a bug manifesting 21 years later and skip seeing their family during crunch time?

To be honest, I just don't like how you disparaged the programmer out-of-context. Talk is cheap.

db48x•3h ago

Using a well–written third–party library would not increase the development time; it would in fact reduce it. No risk of missing Christmas there.

trinix912•3h ago

Well-written 3rd party serialization libraries weren't exactly easy to come by 20 years ago, at least from what I can recall. Your best bet was using an XML library, but XML parsing was quite resource heavy. Many that seemed well designed turned out to be a security nightmare (Java serialization).

db48x•3h ago

I disagree. JSON is 25 years old, and SAX parsers are 22. A SAX parser is the opposite of “resource heavy”, since it is event driven. The parser does not maintain complex state, although you might have to manage some state in order to correctly extract your objects from the XML. Granted, it wouldn’t have integrated nicely with C to generate the parser code from your struct definition back then, but the basics were there.

But it is even more important for today’s game studios to see and understand the mistakes that yesterday’s studios made. That’s the only way to avoid making them all over again.

khedoros1•4m ago

> JSON is 25 years old

And in 2004, didn't have a published specification, or much use outside of webdev (which hadn't eaten the world yet).

> and SAX parsers are 22

And, especially at the time, pretty much exclusive to Java, right?

Put another way, which are the high-quality open-source implementations of those formats that the developers should've considered while working on SA in 2003 and 2004? Or for that matter, in the 2001-2002 timeframe, when the parsing code was probably actually written for use in VC?

danbolt•2h ago

I’ll be the first to defend the greybeards I’ve befriended and learned from in AAA, but having seen codebases of that age and earlier, the “meta” around game development was different back then. I think the internet really changed things for the better.

Your average hire for the time might have been self-taught with the occasional C89 tutorial book and two years of Digipen. Today’s graduates going into games have fallen asleep to YouTube lectures of Scott Meyers and memorized all the literature on a fixed timestep.

fragmede•1h ago

Otoh, the Internet has meant that nothing is ever finished, there's always an update to download.

bluedino•4h ago

Why weren't binary files used like I would expect in the 1990's DOS game? fread into a struct and all that

epcoa•4h ago

By the 2000s, portability was a concern for most titles. Certainly anything targeted at a rapidly changing console market back then.

coldpie•3h ago

Definitely, and architectures back then were far less standardized. The Xbox 360 was a big-endian PowerPC CPU, the PS2 had a custom RISC-based CPU. On the desktop, this was still the era of PowerPC-based Macs. Far easier (and I would argue safer) to use a standard, portable sscanf-like function with some ascii text, than figure out how to bake your binaries into every memory and CPU layout combination you might care about.

mrguyorama•3h ago

Video games are made by a lot of non-programmers who will be much more comfortable adjusting values in a text file than they are hex editing something.

Besides, the complaint about not having a heavyweight parser here is weird. This is supposed to be "trusted data", you shouldn't have to treat the file as a threat, so a single line sscanf that's just dumping parsed csv attributes into memory is pretty great IMO.

Definitely initialize variables when it comes to C though.

CamouflagedKiwi•2h ago

Easier for internal development. Non- or less technical team members can tweak values without having to rebuild these binary files. Possibly also easier for lightweight modding externally as well.

This isn't that uncommon - look at something like Diablo 2 which has a huge amount of game data defined from text files (I think these are encoded to binary when shipped but it was clearly useful to give the game a mode where it'd load them all from text on startup).

db48x•4h ago

You’re not entirely wrong, but a library doesn’t have to be “heavyweight” in order to be bulletproof. And you can load the library during startup and then unload it after; it doesn’t have to stick around for the whole run time of the game. Modern OSes will reclaim the pages after you stop using them, if there is memory pressure. Of course the PS2 didn’t do that I am sure.

rfoo•3h ago

Meanwhile, in a certain modern OS, unloading a library is too broken to the point that people are discouraged to do so... Try to unload GLib [0] from your process :p

[0] https://docs.gtk.org/glib/

wat10000•38m ago

Unloading C libraries is fundamentally fraught with peril. It's incredibly difficult to ensure that no dangling pointers to the library remain when it's unloaded. It's really fun to debug, too. The code responsible for the crash literally is not present in the process at the time of the crash!

anthk•4h ago

XML was everywhere.

PhilipRoman•1h ago

Wow I had no idea YAML was that old. I always thought it was created some time around when CI/CD became popular. Now I'm really curious how it ended up as a superset of JSON.

debugnik•32m ago

JSON didn't save them: This is the same studio that handrolled a JSON parser with accidentally quadratic time complexity, making most players wait 3 to 10 minutes to load GTA Online, for 7 years, until a player got tired and found the root cause.

https://nee.lv/2021/02/28/How-I-cut-GTA-Online-loading-times...

maz1b•4h ago

I always enjoy reading deeply technical writeups like these. I only wonder how much more rare they may or may not get in the AI era.

senda•4h ago

i think the shift will be from craftmens to trademens in regards to general software engineers, but these are type of writes up stem of a artisan style all to its own.

eduardofcgo•3h ago

We have been seeing this shift for a while, where "software engineers" graduate from 3 month bootcamps. Except now most likely they will not be earning 500k making crud apps.

bombcar•4h ago

This is the kind of thing I'd expect from Raymond Chen - which is extremely high praise!

I'm glad they tracked it down even further to figure out exactly why.

martinsnow•3h ago

Raymond is a wizard. Read his blogs for many years and love his style and knowledge.

RcouF1uZ4gsC•3h ago

Raymond knows everything. From microcode bugs on Alpha AXP to template meta programming to UI.

Discordian93•1h ago

He's a total legend, yet apparently he's never met Bill Gates in person from what he said in an interview in the Dave's Garage YouTube channel a few years ago. You'd think that someone who's been that prominent for so long in the company would have been invited to a company dinner where he was present or something.

bombcar•52s ago

Microsoft's a big company, and billg "stepped down" in 2000. Raymond is still working, so they overlap less than may appear.

adzm•4h ago

I'm more curious in what changed with the critical section locking/unlocking implementation in this version of Windows!

mjevans•3h ago

It looks like the utilized stack, or a stack protection area, increased.

asveikau•2h ago

When I worked at Microsoft and I had downtime I would sometimes read the code for app compatibility shims out of pure curiosity.

Win9x video games that made bad assumptions about the stack were a theme I saw. One of the differences between win9x and NT based windows is that kernel32 (later kernelbase) is a now user mode wrapper atop ntdll, whereas in the olden days kernel32 would trap directly into the kernel. This means that kernel32 uses more user mode stack space in NT. A badly behaving app that stored data to the left of the stack pointer and called into kernel32 might see its data structures clobbered in NT and not in 9x. So there were compatibility hacks that temporarily moved the stack pointer for certain apps.

ge96•4h ago

I like the one where you shoot at the moon and it gets closer

Shekelphile•3h ago

That isn't a bug. https://x.com/ObbeVermeij/status/1757572432863384046

carlos-menezes•4h ago

Much love to Silent, who’s been improving my favorite game for over... a decade now?

xxpor•3h ago

For some reason this domain is blocked by work dns filtering?

kstrauser•2h ago

Let your IT department know that their denylist is broken.

mjevans•3h ago

For anyone with access issues

https://web.archive.org/web/20250423144746/https://cookieplm...

nayuki•2h ago

> all these findings prove that the bug is NOT an issue with Windows 11 24H2, as things like the way the stack is used by internal WinAPI functions are not contractual and they may change at any time, with no prior notice. The real issue here is the game relying on undefined behavior (uninitialized local variables), and to be honest, I’m shocked that the game didn’t hit this bug on so many OS versions, although as I pointed out earlier, it was extremely close

This sentence is the real takeaway point of the article. Undefined behavior is extremely insidious and can lull you into the belief that you were right, when you already made a mistake 1000 steps ago but it only got triggered now.

I emphasized this point in my article from years ago (but after the game was released):

> When a C or C++ program triggers undefined behavior, anything is allowed to happen in the program execution. And by anything, I really mean anything: The program can crash with an error message, it can silently corrupt data, it can morph into a colorful video game, or it can even give the right result.

> If you’re lucky, the program triggering UB will show an appropriate error message and/or crash, making you immediately aware that something went wrong. If you’re unlucky, the program will quietly mangle data, and by the time you notice the problem (via effects such as crashes or incorrect output) the root cause has been buried in the past execution history. And if you’re very unlucky, the program will do exactly what you hoped it should do, until you change some unrelated code / compiler versions / compiler vendors / operating systems / hardware platforms – and then a new bug becomes visible, and you have no clue why seemingly correct code now fails to work properly.

-- https://www.nayuki.io/page/undefined-behavior-in-c-and-cplus...

As I wrote in my article, this point really got hammered into me when a coworker showed me a patch that he made - which added a couple of innocuous, totally correct print statements to an existing C++ program - and that triggered a crash. But without his print statements, there was no crash. It turned out that there was a preexisting out-of-bounds array write, and the layout of the stack/heap somehow masked that problem before, and his unlucky prints unmasked the problem.

Okay so then, how can we do better as developers today?

0) Read, understand, and memorize what actions in C or C++ are undefined behavior. Avoid them in your code at all costs. Also obey the preconditions of any API you use, whether in the standard library, operating system, etc.

1) Compile your application in Debug mode and compare its behavior to Release mode. If they differ by anything other than speed, then you have a serious problem on your hands.

2) Compile and run with sanitizers like -fsanitize=undefined,address to catch undefined behavior at runtime.

3) Use managed languages like Java, C#, Python, etc. where you basically don't have to worry about UB in normal day-to-day code. Or use very well-designed low-level languages like Rust that are safe by default and minimize your exposure to UB when you really need to do advanced things. Whereas C and C++ have been a bonanza of UB like we have never seen before in any other language.

semi-extrinsic•1h ago

I learned this lesson many moons ago, on a Fortran code I wrote for a university assignment. It was a basic genetic algorithm, and for some reason it was converging much more slowly than expected. So I was sprinkling some WRITEs to debug, and suddenly the code converged a hundred times faster.

spookie•1h ago

Other than C#, there is no reason to use those other languages for game dev. Unless the game is fairly simple, or you want to risk a fairly long project by employing a language that hasn't been proven in tge space yet (Rust). No shade at any of those languages, I don't even like C#, just being pragmatic.

wat10000•42m ago

I would add: code defensively. Initialize your variables (either to a sensible value, or an outrageously wrong value) before passing pointers to them, even when you "know" that the value will be overwritten. Check for errors. Always consider what happens when things go wrong, not just when things go right. Any time you find yourself thinking, "condition X is guaranteed to hold, so I don't need to check for it" consider checking it anyway just in case you're wrong about that, or it changes later.

rkunde•2h ago

I wonder if they fixed the vehicle definition file as well, or just the parser. The latter would be an incomplete fix.

tonmoy•2h ago

Given that those parameters are for wheels on a plane that doesn’t have wheels, I would say fixing the parser is the better fix

doublerabbit•1h ago

It is, but who enjoys fixing parser issues...

jandrese•2h ago

> Not ignore the compilation warnings – this code most likely threw a warning in the original code that was either ignored or disabled!

What compiler error would you expect here? Maybe not checking the return value from scanf to make sure it matches the number of parameters? Otherwise this seems like a data file error that the compiler would have no clue about.

burch45•1h ago

Undefined behavior to access the uninitialized memory. A sanitizer would have flagged that.

jandrese•1h ago

The compiler has no way of knowing that the memory would be undefined, not unless it somehow can verify the data file. The most I think it can do is flag the program for not checking the return value of scanf, but even that is unlikely to be true since the program probably was checking for end of file which is also in the return value. It was failing to check the number of matched parameters. This is the kind of error that is easy to miss given the semantics of scanf.

andrewmcwatters•1h ago

Uninitialized variables are a really common case.

andrewmcwatters•1h ago

Yeah, the debugging here is great, but the actual cause is super mild.

gitroom•2h ago

pretty wild how bugs can stick around that long - id never think something from 20 years ago would pop up just cause windows changed

josephcsible•2h ago

tl;dr of the explanation: the Skimmer vehicle is missing a wheel scale definition, so its wheel scale gets read from uninitialized memory. On previous versions of Windows, this happened to be the wheel scale of the previously-loaded vehicle, so things happened to work fine. Starting on Windows 11 24H2, LeaveCriticalSection (which gets called between loading vehicles) uses more stack space than before, so it now overwrites that memory with a gigantic value, resulting in the Skimmer spawning so high up that it may as well not exist at all.

pmarreck•2h ago

My takeaway, speaking as someone who leans towards functional programming and immutability, is "this is yet another example of a mutability problem that could never happen in a functional context"

(so, for example, this bug would have never been created by Rust unless it was deeply misused)

grishka•1h ago

This is more of a problem of the C/C++ standard that it allows uninitialized variables but doesn't give them defined values, considering it "undefined behavior" to read from an uninitialized variable. Java, for example, doesn't have this particular problem because it does specify default values for variables.

gavinray•1h ago

Rust protects you from external file data you read being incorrect?

That's one hell of a language!

stefs•1h ago

Of course not, but this here was a memory access error and rust would have prevented this.

mbel•1h ago

Most popular languages would prevent this. In this case it’s as simple as having more sensible reader API than sscanf in standard library and forcing variables to be initialized.

ArchOversight•1h ago

The code would have failed because you can't use an uninitialized variable, so you would have had to set it to a default. You don't just get random garbage from the stack.

SkiFire13•1h ago

It would have forced you to either specify a default or fail pretty loudly as soon as you launched the game, both much better than leaving a bug there just for it to resurface 20 years later.

jdndndb•1h ago

Could you elaborate? I cannot see how a functional programming language would have protected you from reading a non existing value while not providing a default

pmarreck•37m ago

I've never heard of a functional language that would allow you to initialize a value to whatever value the system memory already had in that memory location. In languages that allow nil, it would at least be nil; in languages that don't, you would have gotten an error about an uninitialized and undefaulted value. In any typed language, you would have also gotten an error.

It's true that C may be unique-ish in this regard though- this bug also couldn't happen in Ruby, which is not a functional language, but Ruby certainly still makes undefined behaviors much more possible than in other languages like Elixir.

smj-edison•1h ago

I'd actually say that Rust is a third option between "everything is immutable" and "mutable soup". Rust is more of "one mutator at a time". Because, Rust really embraces being able to mutate stuff (so not functional in that sense), it just makes sure that it's in a controlled way.

bentcorner•1h ago

FWIW I think a linter or other similar code quality checker would have caught this as well. From a practical perspective (e.g., how do you prevent this from happening again in your game studio's multi-million line code base) that would have been the right thing to do here.

csours•1h ago

Once this category of error is raised to your attention, you start to notice it more and more.

A little piece of technology made sense in the original context, but then it got moved to a different context without realizing that move broke the contract. Specifically in this case a flying boat became an airplane.

---

I recently worked a bug that feels very similar:

A linux cups printer would not print to the selected tray, instead it always requested manual feed.

Ok. Try a bunch of command line options, same issue.

Ok. Make the selection directly in the PPD (postscript printer definition) file. Same issue.

Ok! Decompile the PXL file. Wrong tray is set in pxl file... why?

Check Debug2 log level for cups - Wrong MediaPosition is being sent to ghostscript (which compiles the printer options into the print job) by a cups filter... why?

Cups filter is translating the MediaPosition from the PPD file... because the philosophy of cups is to do what the user intended. The intention inferred from MediaPosition in the PPD file (postscript printer definition) is that the MediaPosition corresponds to the PWG (Printer Working Group) MediaPosition, NOT the vendor MediaPosition (or local equivalent - in this case MediaSource).

AHA!! My PPD file had been copied from a previous generation of server, from a time when that cups filter did NOT translate the MediaPosition, so the VENDOR MediaSource numbers were used. Historically, this makes sense. The vendor tray number is set in the vendor ppd file because cups didn't know how to translate that.

Fast forward to a new execution context, and cups filters have gotten better at translating user intention, now it's translating a number that doesn't need to be translated, and silently selecting the wrong tray.

TLDR; There is no such thing as a printer command, only printer suggestions.

smcameron•1h ago

Surprised to see the return value of sscanf being ignored, that seems like a pretty rookie mistake, and this bug would never have made it out of the original programmer's system if they had bothered to check it.

amenghra•1h ago

IMHO, if something isn’t part of the contract, it should be randomized. Eg if iteration order of maps isn’t guaranteed in your language, then your language should go out of its way to randomize it. Otherwise, you end up with brittle code: code that works fine until it doesn’t.

roseway4•1h ago

iirc, Go intentionally randomizes map ordering for just this reason.

withinboredom•29m ago

Yep, and then you get crash reports you can’t reproduce.

bri3d•1h ago

There are various compiler options like -ftrivial-auto-var-init to initialize uninitialized variables to specific (or random) values in some situations, but overall, randomizing (or zeroing) the full content of the stack in each function call would be a horrendous performance regression and isn't done for this reason.

mras0•1h ago

Not really the ethos of C(++), though of course this particular bug would be easily caught by running a debug build (even 20 years ago). However, this being a game "true" debug builds were probably too slow to be usable. That was at least my experience doing gamedev in that timeframe. Then again code holding up for 20 years in that line of biz is more than sufficient anyway :)

gzalo•51m ago

I agree, this can also detect brittle tests (e.g, test methods/classes that only pass if executed in a particular order). But applying it for all data could be expensive computation-wise

abnercoimbre•50m ago

Regarding contracts, there's an additional lesson here, quoting from the source:

> This is an interesting lesson in compatibility: even changes to the stack layout of the internal implementations can have compatibility implications if an application is bugged and unintentionally relies on a specific behavior.

I suppose this is why Linux kernel maintainers insist on never breaking user space.

willcipriano•36m ago

Then you are wasting runtime clock cycles randomizing lists.

ormax3•11m ago

one might argue that one of the advantages of languages like C is that you only pay for the features you choose to use, no unnecessary overhead like initializing unused variables

qingcharles•1h ago

20 years and still nobody has realized what the back of this sign is about. IYKYK.

https://static.wikia.nocookie.net/gta-myths/images/f/f1/Egg_...

spopejoy•1h ago

fixed link (the above did not work for me) https://static.wikia.nocookie.net/gta-myths/images/f/f1/Egg_...

rideontime•1h ago

And if I don't know?

nubinetwork•1h ago

Apparently the planes are buggy in all sorts of ways, although I don't remember them being this bad... https://youtu.be/hrJ0eVY5ACw

olvy0•1h ago

Just like $dayjob.

gigatexal•18m ago

Use a debugger folks. A 10x dev cited this story to me about the ills of not using one.

ajross•8m ago

Tools like valgrind/asan/msan would have flagged this instantly too. Just a unit test of that vehicle loader would have seen it.

Really this is more a story about poor development practice than it is an interesting bug.

Fuchsia RFC: fast and efficient user space kernel emulation

How to Cut Your Risk of Stroke, Dementia and Depression All at Once

Meta and Apple Just Got Slapped by Europe's New Rulebook

'China Track' bank netting system shields Russia-China trade from Western eyes

Modular's CUDA alternative is ready

PyTorch 2.7 Release

First Successful Lightning Triggering and Guiding Using a Drone

Animals Are More Rational Than You Think

Transform Your Career with Our Cloud and AI Academy

Moon photovoltaics utilizing lunar regolith and halide perovskites

Upcycling POS Devices

The record-breaking tunnel being built from Denmark to Germany

Show HN: Build a $1/HR AI voice companion in 20 seconds

What is a POS (point of sale terminal)?

C++26: more constexpr in the core language

Google Search AI invents plausible meanings for any phrase

The Easiest Way to Standardize Your Team's Code

Ninth Circuit Takes a Wrecking Ball to Internet Personal Jurisdiction Law

xPal Encyrpted Messenger Security

College Applications in 10 Minutes

USAID Budget Cut Death Counter

Link-Time Optimization of Dynamic Casts in C++ Programs [pdf]

ePub 3.3 Recommendations

Reverse Engineering the International Superstar Soccer Password System

Namie: A nuclear ghost town reopens after 6 years (2017)

Show HN: SoundLeaf – iOS Client for Audiobookshelf Server

A parasitical business model: how ticket resellers squeeze out loyal supporters

Show HN: Document agent example that can parse and chat over unstructured data

Guillotine: Hypervisors for Isolating Malicious AIs

Tiny Teams: $6M ARR, 5M users with 4 employees [video]

Fuchsia RFC: fast and efficient user space kernel emulation

How to Cut Your Risk of Stroke, Dementia and Depression All at Once

Meta and Apple Just Got Slapped by Europe's New Rulebook

'China Track' bank netting system shields Russia-China trade from Western eyes

Modular's CUDA alternative is ready

PyTorch 2.7 Release

First Successful Lightning Triggering and Guiding Using a Drone

Animals Are More Rational Than You Think

Transform Your Career with Our Cloud and AI Academy

Moon photovoltaics utilizing lunar regolith and halide perovskites

Upcycling POS Devices

The record-breaking tunnel being built from Denmark to Germany

Show HN: Build a $1/HR AI voice companion in 20 seconds

What is a POS (point of sale terminal)?

C++26: more constexpr in the core language

Google Search AI invents plausible meanings for any phrase

The Easiest Way to Standardize Your Team's Code

Ninth Circuit Takes a Wrecking Ball to Internet Personal Jurisdiction Law

xPal Encyrpted Messenger Security

College Applications in 10 Minutes

USAID Budget Cut Death Counter

Link-Time Optimization of Dynamic Casts in C++ Programs [pdf]

ePub 3.3 Recommendations

Reverse Engineering the International Superstar Soccer Password System

Namie: A nuclear ghost town reopens after 6 years (2017)

Show HN: SoundLeaf – iOS Client for Audiobookshelf Server

A parasitical business model: how ticket resellers squeeze out loyal supporters

Show HN: Document agent example that can parse and chat over unstructured data

Guillotine: Hypervisors for Isolating Malicious AIs

Tiny Teams: $6M ARR, 5M users with 4 employees [video]

How a 20 year old bug in GTA San Andreas surfaced in Windows 11 24H2

Comments