[mcescalante]

I have been involved in a slow-rolling project at work to migrate a fair number of administrative screens and their data (written in the late 80s/early 90s) off of the existing zOS mainframe, primarily because of the costs (management doesn't want to pay IBM anymore for the limited set of things it's being used for and finding devs is expensive too). The project has already run way past the original estimate, no major surprise.

Our new APIs and web UIs are nice and all and offer a number of advantages for today's users/admins, but sometimes it feels they take more babysitting and fuss (updating deps, etc.) than the old mainframe code did - I'm not confident that an Angular SPA running for 20+ years would still work the same, so we have tried to take that into consideration while designing replacements.

I'm not complaining about one or the other but rather I feel lucky to have experienced tradeoffs and learned about how some of these problems were solved 20-30 years ago, while I was still in grade school.

[zozbot234]

Not everything needs to be an Angular SPA, surely? It seems obvious that choosing a well-understood server side platform would make way more sense for something like this.

[mcescalante]

You're absolutely correct - we have a healthy mix of traditional server-side web applications and a small number of SPAs only where it makes sense (usually complex forms with lots of feedback/conditionals). I just used Angular as an (admittedly) easy target. These days, I've been trying my best to avoid SPA for enterprise stuff if possible