4 ms·
> This is very frustrating. But it does serve as yet another reminder of the dangers inherent to closed ecosystems. The bulk of the code in my day job is deepl
by rodgerd 5y ago
> This is very frustrating. But it does serve as yet another reminder of the dangers inherent to closed ecosystems.
The bulk of the code in my day job is deeply proprietary and runs on deeply proprietary, closed systems: stuff like 40 year old COBOL running on CICS on zOS.
The problem is not that the system is closed. The problem is that some vendors have an institutional sense of responsibility to their customers. Others have nothing but contempt.
- javajosh 5y agoYes, it is perverse how intolerant devs tend to be toward old systems that perform valuable service and make a lot of money. There are some interesting ideas in those older systems designed to run with incredibly small resource constraints. That said, I think it's also true that incentives aren't always aligned when it comes time to port away from the entrenched environment, as these projects, if successful, constitute a real loss of income for the older devs.