Notices by niconiconi (niconiconi@mk.absturztau.be), page 21

The [2004] worm will also copy itself to various peer-to-peer shared folders as the following files:
Doom 3 release 2.exe
Gimp 1.8 Full with Key.exe
Internet Explorer 9 setup.exe
Smashing the stack full.rtf.exe
Win Longhorn re.exe
Windows 2000 Sourcecode.doc.exeLMAO. I didn't know those worms from 2004 were that hilarious. :blobcatlul:

@rq@borg.social I just wanted to wipe it, but I dropped the trackball on the floor...

Trackball reoiled, the cursor goes faster now. :restless_cursor:

@foremostarchwiz@mastodon.social @puniko@mk.absturztau.be
Q: What is a woodworker's favorite operating system?

A: Unix, because everything is a file.

@puniko Good meownyaaaaaaaaaaaa

@hyc@mastodon.social Well, the flamewar between freestanders and Batteries Includers is a long and old one...

@hyc@mastodon.social memcpy() is no longer a library function today, it also works like a special code annotation. I believe calling a dummy memcpy() is one legal way to do type punning. If you do it yourself by casting pointers, the result is undefined. If memcpy() does it, it's implementation-defined - which usually gets optimized into a noop by the compiler anyway, if direct access to the underlying memory is acceptable for a particular machine (not always, e.g. alignment-to-machine-word rules).

The root of the problem is that C cannot decide whether it's a high-level or low-level language and sits on the borderline between both. Historically, programmers did all kinds of hacks inside C, like arbitrarily casting memory from and to char * (K&R didn't even have void), or the famous "you're not expected to understand this", which relied on compiler-specific register allocation. But when it became a general-purpose language, for portability and optimizations, only a subset of all possible C code is allowed, which is the part that only operates on "entities" rather than bytes without making assumption about the underlying machine or data representation.

But of course machine-specific assumptions must be made somewhere down the chain. How should the intention of the programmers in these kinds of code be expressed or communicated to the compiler is never systematically considered when C was originally designed.

#TIL C++26 is planning to add the whole BLAS into the standard library, and will natively support std::mdspan (the official multi-dimensional array since C++23). C++ surely is a programming language that people just throw everything imaginable into it. #hpc

@lanodan@queer.hacktivis.me I guess the inclusion of special functions into STL is what truly makes C++ a "complex" programming language. https://en.cppreference.com/w/cpp/numeric/special_functions

#TIL C++17 has std::riemann_zeta(), C++ surely is a programming language that people just throw everything imaginable into it.

@puniko mew mew mew

"the person who intentionally added that backdoor."not necessarily under their free will.

The operating system is called DOS because it's easy to DOS yourself.

@chjara@akko.wtf @rq@borg.social O=MiniTruth CN=Big Brother http://www.cypherspace.org/adam/hacks/lotus-nsa-key.html

This ancient Rage Comic is still an all-time classic.

"There are no known reports of those [backdoored xz] versions being incorporated into any production releases for major Linux distributions"It's the one single big difference between npm and traditional distro packages - a bad upstream change doesn't instantaneously propagate to all end users within a picosecond.

Good meownyaaaaaaaaaaaaaaaa

@puniko meowco-celebrity

Berlin Wall implies the existence of Berlin Wextra.

Modern Python code uses explicit type annotation everywhere, meanwhile modern C++ code uses implicit type "auto" everywhere and relying on template type deduction to match it to a compatible function automatically. What a strange new world we find ourselves living in.