4 ms·

> In my opinion as well, the future of software development is somewhere in the middle of this spectrum Unfortunately this is complexity in and of itself. I do

by jb3689 6y ago

> In my opinion as well, the future of software development is somewhere in the middle of this spectrum Unfortunately this is complexity in and of itself. I don't disagree that different cases require different tools, however the split should be strongly weighted in one direction. Mostly IPC over pipes with a few exceptions, mostly REST and JSON with a few exceptions, mostly language X with a few exceptions. Everyone will have their own preferences, but I think it's important to pick a side (or at least mostly pick a side) or else you accept chaos

chubot 6y ago
I think of it as a matter of scale. - At the scale of 1,000 to 1M lines of code, authors/programmers have some control, and you're dealing with a time scale of months or years. - At the scale of 10M to 100M lines of code, no organization is an author with complete control, and you're dealing with a time scale of decades. In the latter case, you can't make global changes to the system, so you end up with glue in the form of pipes and textual data dumps. You're going to have some chaos because you can't go and change every system to be consistent. So I would say the future of software development is at BOTH ends of the spectrum, not somewhere in the middle. ----- Good material on the subject: https://www.dreamsongs.com/Files/DesignBeyondHumanAbilitiesSimp.pdf https://www.dreamsongs.com/Files/DesignBeyondHumanAbilitiesS... If you look at the code in a web browser or operating system you will see this "lack of control". Once a codebase reaches a certain size, there's only so much you can do with it, and you end up with loosely coupled glue around it. I think a reasonably minimal Debian system has to have somewhere between 100M and 1B lines of code in it, and that whole thing becomes a blob that you dump on a virtually free computer like a Raspberry Pi, etc. I think if you look at the software that banks and airlines run on you will see the same thing. There's some code from the 60's or 70's written in some weird language at the heart of it. You don't really get to architect the system; it's more accurate to say that the system places its constraints on you.

by jb3689 6y ago

chubot 6y ago

I think of it as a matter of scale. - At the scale of 1,000 to 1M lines of code, authors/programmers have some control, and you're dealing with a time scale of months or years. - At the scale of 10M to 100M lines of code, no organization is an author with complete control, and you're dealing with a time scale of decades. In the latter case, you can't make global changes to the system, so you end up with glue in the form of pipes and textual data dumps. You're going to have some chaos because you can't go and change every system to be consistent. So I would say the future of software development is at BOTH ends of the spectrum, not somewhere in the middle. ----- Good material on the subject: https://www.dreamsongs.com/Files/DesignBeyondHumanAbilitiesSimp.pdf https://www.dreamsongs.com/Files/DesignBeyondHumanAbilitiesS... If you look at the code in a web browser or operating system you will see this "lack of control". Once a codebase reaches a certain size, there's only so much you can do with it, and you end up with loosely coupled glue around it. I think a reasonably minimal Debian system has to have somewhere between 100M and 1B lines of code in it, and that whole thing becomes a blob that you dump on a virtually free computer like a Raspberry Pi, etc. I think if you look at the software that banks and airlines run on you will see the same thing. There's some code from the 60's or 70's written in some weird language at the heart of it. You don't really get to architect the system; it's more accurate to say that the system places its constraints on you.