3 ms·
> 6 years ago, I rewrote 30 000 lines of C++ code in 1000 lines of Ruby. (...) > Code bloat is indeed a recurrent problem. But in your example, you're still
by e12e 11y ago
> 6 years ago, I rewrote 30 000 lines of C++ code in 1000 lines of Ruby.
(...)
> Code bloat is indeed a recurrent problem.
But in your example, you're still depending on thousands (millions?) of lines of BIOS, OS, library, runtime code.
It's so many orders of magnitude different than the point Moore is making -- and also, more subtly different: it's not like Forth system don't have library/OS code -- but eg. fitting a rich editor/IDE and OS on a floppy is quite different from eg: Ruby. It's a completely different mindset.
Even if something like Ruby does a lot of things out of the box, if you were to strip it down to a subset that only allowed to be used as a caluclator repl, it'd still be quite complex compared to a Forth system (just think about all the code need to handle keyboard input, and talking to the monitor over VGA/HDMI etc).
None of that invalidates your point, that code bloat is a problem, I just think it highlights that there are different kinds of bloat.
Somewhere between colorForth and developing in in a "traditional" language with a "traditional" IDE on a "traditional" OS, we find things like Project Oberon and Smalltalk-80. Or VPRI's recent effort to create a full drivers-through-gui-up-to-and-including-applications system in 50kcloc total, making aggressive use of DSLs to manage the complexity.