3 ms·
IMO, anytime the programmer has to micro-manage anything it's basically assembly (Forth forces you to micro-manage the stack). I dislike syntax which uses the
by dewster 10y ago
IMO, anytime the programmer has to micro-manage anything it's basically assembly (Forth forces you to micro-manage the stack).
I dislike syntax which uses the <> symbols, but I'm all for RPN and postfix (in theory anyway).
- jononor 10y agoDoes imperative programming force you to micro-manage variables and arguments? For me I think the challenge is that the stack-effects are 'hidden' in the code. However, this seems like it could be solvable by compiler (typed stack effects for instance) and tooling/IDE.
- dewster 10y ago> Does imperative programming force you to micro-manage variables and arguments? I just don't think many programmers fully take into account all the trouble a stack-based language is. You're constantly rearranging the stack to get values stored on it in position to call functions and such. You know stack manipulations are inherently wasteful, and you worry about doing too many of them. So you end up micro-managing them, and often end up sacrificing readability for efficiency. And the readability of stack languages is already woefully bad. I don't really understand why they continue to exist.