4 ms·
Less optimizations, simpler instruction sets, easier to implement. Going from transistors to C is like petrol to driving. Do you want to learn how a car works
by jumploops 3y ago
Less optimizations, simpler instruction sets, easier to implement.
Going from transistors to C is like petrol to driving.
Do you want to learn how a car works by building some 2024 safety and tech enabled car?
Or would you rather start with something that resembles a 60s Beetle but with even less bells and whistles?
- DeathArrow 3y agoBut aren't there real architectures that are simple enough? Z80, MOS 6502, Pic, AVR?
- jumploops 3y agoReal hardware handles real trade-offs. For example, there are hundreds of instructions in Z80 to support various quirks of the implementation (like the duplicate register file). Sometimes less is more, and it can be freeing to know that your code compiles to a CPU with just a dozen or so instructions. It’s the same reason most universities don’t teach git, UNIX, and other industry tools. Sometimes computer science is best seen in its purest form. Same with computer engineering.
- kelseyfrog 3y agoAnd at the end of the day, students should be trained to teach themselves (including things like Git, and Unix). I'm curious if GP (or anyone else) has been in the position of hiring entry level and finding someone who they felt didn't work out because the new hire was incapable of learning tools. Or the new hire eventually taught themselves?