Lady in Love @Lady@cat.family

@wallhackio i also did this the TI-83/84 instruction manual was great

@aescling @wallhackio i don't think learning how a specific C compiler infrastructure works and learning C are the same thing at all

@aescling @wallhackio curious what there is to teach here

@aescling @wallhackio name a nasty corner in POSIX shell

@aescling @wallhackio as C or as C++? because these are very different beasts

@wallhackio (actually i think there’s an argument to teach basic programming concepts in POSIX sh instead, and would also consider this acceptable, but this is a more radical take)

@wallhackio i think basic software concepts should be taught in C, because there is no more basic software concept than “produce readable, maintainable code and do not shoot yourself in the foot”, and C is the easiest language in which to discern whether a student has learned these lessons

for anything more advanced than that, idk, probably Swift

@aescling @wallhackio this is the idea behind Racket; i’m not sure i agree but i do think lisps should be a required 200-level course

@wallhackio it’s wild to go through a basic computer science class and still not be able to read a single file of C code because they never REALLY taught you how malloc() and friends worked

@wallhackio our class did this and even at the time i felt like they should have just done C instead

@wallhackio @Satsuma listen to this album it’s not like this https://ssm.lnk.to/YELLOW

@wallhackio the only good ending, “died fucking an incubus in hell”

@aescling i don't know enough about how linkers operate to say. but git does do a huge amount of setup and teardown (see <https://github.com/git/git/commit/3f2e2297b9c88a6ab5fc4bff02cf2a07ce057589>)

@aescling hmm?