social.omar.website

dynamic types vs. static types / non-hygienic vs. hygienic macros / memory-unsafe vs. memory-safe systems programming all feel like echoes of the same argument at different scales

in terms of the cultures who argue each side, the emotions they tap into, the different visions they present for what programming 'should be' and what kind of skills should be expected of a programmer

a good programmer doesn't need hygienic macros, they can just get the names right by hand and use gensym / a good programmer doesn't need memory safety, they should be able to allocate and free properly by hand

@omar I think it's less about the individual and more about the size of the team who will be writing that program together.

@omar yeah that still holds, writing asm all day I can clearly see that it wouldn't scale for large projects or large teams.

I was reading about the building of the Setun this morning, and where the team didn't even bother writing an assembler for some time and just wrote raw hex codes.

http://brokestream.com/daf.txt

It makes sense for a handful of team writing small program, but the moment you need an HR dep, it falls apart.

Inversly, when I was people using industry langs for personal projects..