| ▲ | kerblang 42 minutes ago | |
It was less broken before open source allowed an architectural explosion, because the dependencies were too expensive. It took a lot of arguing to get management to splurge on a single library or other tool. A lot of astronaut-architect wannabes were constantly grumpy about mgmt that wouldn't pay for the latest whiz-bang thingie. The actual programming logic has certainly always been complex, but the integrations weren't so bad. You could learn your very small toolset quickly and focus on ideas. Now, you have an ultra-massive toolchain to come to terms with, made up of free software and "cloud" architecture that starts off cheap and gets expensive later on. Dependencies have always been the problem, but that problem has expanded in every direction, at every layer, approaching our own limits of comprehension. AI has allowed us to catch up, temporarily, but given the collective penchant for upping the ante, I expect the real supernova is yet to come. | ||
| ▲ | cmiles74 30 minutes ago | parent [-] | |
Is the problem open source? I haven't see these kinds of widespread problems coming from Java dependencies (25 years old) or Perl (maybe 30 years old)? Okay, maybe people aren't using Perl like they used to but Java is still a thing. Part of it is the inclination of the developer to make the thing more robust. Part of it is lowering the barrier of entry, maybe to the point it's _too_ easy to submit a package. Part of it is bad decisions made by the package manager, like running arbitrary scripts. | ||