3 ms·
At work our program is about a million lines of code (plus third party libraries etc). We've got 124 different customer specific file/data integrations. Most of
by magicalhippo 7y ago
At work our program is about a million lines of code (plus third party libraries etc). We've got 124 different customer specific file/data integrations. Most of those integrations are file based, and the majority of them also involve us fetching or uploading via HTTP or (S)FTP.
Doing low-level file I/O, socket I/O, handling low-level HTTP and FTP code for each one that needs it, parsing XMLs from scratch five dozen times, doing all those integrations without abstractions... how is that an improvement?
And reducing line count by a mere 10x would do nothing for keeping it all in the head at one time. Even if you could get it down by 1000x, I don't think you'd accomplish much because the logic still has to be there.
- haolez 7y agoChuck Moore, the creator of Forth, created a CAD system for microelectronics with a tiny fraction of code that mainstream products required. With our bloated stacks, the most used CPU instructions that our binaries use are the ones moving data. We are not using the computers to compute, but just to move data around. That just feels wrong. K, APL, Forth and the likes are living proofs that there are other ways to solve complex problems.
- magicalhippo 7y ago> We are not using the computers to compute, but just to move data around. That just feels wrong. That is because moving data around is a very useful thing. In fact, our entire product is almost entirely about moving data. Using it, our customers don't have to move data by hand. They don't have to look at invoices and fill in forms with a pen, put those in an envelope and send it to the government. Instead our product can do that. And it can be smart about which data to move, when to move it, and where to move it. That's where the small bit of computation comes in.