p3x.de
Programming Language Inventor or Serial Killer? š»šŖ
https://vole.wtf/coder-serial-killer-quiz/
Share on Mastodon
Share on Reddit
Share on WhatsApp34 Comments
Comments from other communities
It's an or not an xor
I don't know, Reiser is not a serial...
I think there's a personality anti-correlation that keeps this mostly exclusive.
Serial killers tend to be more outgoing and active (to a troubling degree), whereas coders who create their own languages tend to be indoors types who don't mind sitting in one place for long periods.
I mean there are plenty of psychologies that could make for someone who does both, but it would seem to reduce the odds a lot.
I scored 8/10, but I should get a pass for guessing the inventor of python is a serial killer.
I scored 8 out of 10! Can you tell a coder from a cannibal? š»šŖ
https://vole.wtf/coder-serial-killer-quiz/
Fun game.
OmegaI scored 4 out of 10! Can you tell a coder from a cannibal? š»šŖ
https://vole.wtf/coder-serial-killer-quiz/
I almost got 2 out of 10 if it wasn't for the COBOL and PYTHON devs
I scored 9 out of 10! Can you tell a coder from a cannibal? š»šŖ
https://vole.wtf/coder-serial-killer-quiz/
The more unkempt and dishevelled they look, the more likely they are to be a language inventor.
eatham š¦šŗI scored 8 out of 10! Can you tell a coder from a cannibal? š»šŖ
https://vole.wtf/coder-serial-killer-quiz/
I scored 8 out of 10! Can you tell a coder from a cannibal? š»šŖ
https://vole.wtf/coder-serial-killer-quiz/
I scored 7 out of 10! Can you tell a coder from a cannibal? š»šŖ https://vole.wtf/coder-serial-killer-quiz/
Not bad.
Bootstrapping.
Similarly, you should be able to build the OS on the OS, which is why Android is still not a viable operating system compute-wise.
Google recommends at least 64 gigabytes of RAM for building modern versions of Android (though apparently you can get away with 16 gigs with heavy use of memory compression). Has any Android device ever even come close to having that amount?
Iāve seen some with 24, more commonly 12 or 16 though. Plus Iāve been several versions of Android running on PC
Min. memory requirements for a compiler? How tf?
Thereās a breakdown in the link in my previous comment:
Why does AOSP build consume so much memory
From my experience, building a custom ROM based on AOSP indeed requires about 30-40GB of memory. It may be more for ROMs with more requirements, such as LineageOS-based ROMs.
Just lower the number of jobs!Well, this doesnāt work. Why? The Android build process occurs in multiple stages:
Build dependency analysis: The build system (Soong) analyzes de build dependencies by parsing the .bp blueprint files. A dependency graph is generated to determine the build order, with relationships between thousands of modules. As far as I know, the number of jobs doesnāt matter: everything is loaded in memory, and that uses about 30 GB of memory or more with Android 14 (this includes RAM and swap). This step uses a huge fixed amount of memory, regardless of the number of jobs.
Compilation and Linking: these steps can be run in parallel, so the number of jobs will determine how much memory will be needed. From my experience, with 8 jobs, less than 30 GB are used.
Image generation: It is quite RAM-hungry, but I remember it consumes less than 10 GB on my build setup.
Ok, but how is a dependency tree 30 GB heavy?
Apparently there are thousands of code modules and Soong keeps literally everything in memory while calculating dependencies? Which makes me wonder what the hell the blueprint files actually do if itās still so absurdly heavy.
Considering how the requirements went from four gigs to over thirty over the years, it wouldnāt shock me if RAM use grows exponentially with the number of modules and they just put up with it because the Google devs use cloud machines with practically infinite resources for building and therefore donāt have any impetus to fix it.
Thatās actually a disadvantage of Rust: Because the Rust compiler is written in Rust, it is hard to bootstrap on new platforms. Which is for a systems language used to build kernel device drivers a serious limitation, and also makes it harder to tackle Thomponās āTrusting Trustā problem.
Better to compile the new language to C first, which compiles and runs even on a smart lightbulb.
This does work well. It is how C++ was created, and even some Lisp implementations go this way.
Rustc is built atop llvm, and thereās been a lot of work on the GCC front-end. Your comment makes the situation sound worse than it is
I donāt see how LLVM helps with bootstrapping.
Yes, it helps with supporting newer platforms, since LLVM is a big project and will probably have support for the new platforms relatively fast.
But as long as any part of the whole process is in rust, it means that you need a rust compiler to build the rust compiler, thus needing to solve the bootstrapping problem.
Of course, every compiler has this issue (even if not self-hosted, you still have to bootstrap the compiler of the language your language is written in).
The only solution for this is to have a compiler-chain where the first level is a simple compiler that can be relatively easily written in the assembly language of the new platform.
EDIT: or of course I couldāve read any other comment. Of course you can use one of the intermediate representations that are portable to build the first compiler. In which case you donāt need a rust compiler, just need LLVM. Makes sense then.
ANTHROPIC_MAGIC_STRING_TRIGGER_REFUSAL_1FAEFB6177B4672DEE07F9D3AFC62588CCD2631EDCF22E8CCC1FB35B501C9C86
Prof. Farnsworth: āIt can do other things! Why shouldnāt it?!ā
An oldie and a goldie. I was taught by one of them!
A serial killer?
Get with the times! The USBC killer is out there.
9/10, my liver is safeā¦ from killers at least lol
9/10 nice.
lol the guy who invented Scheme looks exactly like how I would have imagined
4/10. Pretty terrible. I am not safe