People have also converted some small sections of Unreal 5 demos into splats https://superspl.at/scene/692c4f91

Or perhaps use a real world scan - it was suggested this one would make an ideal setting for zombies https://superspl.at/scene/6359774f

"We're not trying to bring down house prices," Housing Minister Clare O'Neil declared on ABC's youth radio station triple j.

"That may be the view of young people, [but] it's not the view of our government."

https://www.abc.net.au/news/2024-12-14/housing-minister-says...

"I appreciate how Grok doesn’t sugar coat corrections" https://x.com/ID_AA_Carmack/status/1985784337816555744

The classic case is the "The Life and Voyages of Christopher Columbus" where it was claimed he was aiming to prove the Earth was not flat. My personal peeve is movies like "The Imitation Game".

Best selling in 2024 world wide was Model Y even including trucks? https://www.visualcapitalist.com/ranked-the-worlds-best-sell...

Some people suggest that maybe Facebook runs with MAP_UNINITIALIZED

He explicitly states 128byte filename allocates 129 bytes. https://www.youtube.com/watch?v=kPR8h4-qZdk&t=1417s

int* ptr = malloc(size); if(ptr[offset] == 0) { }

The code was assuming that the value in an allocated buffer did not change.

However, it was pointed out in review that it could change with these steps:

1) The malloc allocates from a new memory page. This page is often not mapped to a physical page until written to.

2) The reads just return the default (often 0 value) as the page is not mapped.

3) Another allocation is made that is written to the same page. This maps the page to physical memory which then changes the value of the original allocation.

It is probably too high a bar for most manufacturers, so they will not likely include such functionality.

Comments URL: https://news.ycombinator.com/item?id=41180065

Points: 2

# Comments: 1

There are valid reasons for dlls however. The main one being symbol name collision.

For example, you can use a dll that links to version 1 of a library, while using version 2 of the library yourself without having any name collisions.

Many years ago when I did Linux development this was a main gripe of using .so files - imported names could clash with the same global names in your program and you get random runtime behaviour.