4 ms·

I'm aware of the well-established movement to static websites for (mostly) static sites, but what work is happening right now to counter this problem in rich we

I'm aware of the well-established movement to static websites for (mostly) static sites, but what work is happening right now to counter this problem in rich web applications? Are there frameworks that take a stance that favors stability and maintenance?

SwellJoe 7y ago
I think the move toward micro-services (and serverless and whatever other buzzwords you want to use for a distributed loosely coupled design) is an answer to that problem, if not exactly the answer you're describing. The idea being that each small piece is easier to leave alone for long periods of time, and, should it ever become impossible to leave it alone, whether for security reasons or something else, updating it or replacing it is much easier than doing the same for a big tightly coupled pile of components.
freshhawk 7y ago
Frameworks aren't the design choice that favours stability. You take the inversion of control to get all the convention/plug-and-play/just-works features that come with it. Those are focused on developer productivity, which is a constantly shifting goal. Avoid that design and using a "libraries over frameworks" approach solves this problem but has other tradeoffs obviously, although a good ecosystem of libraries that have designed for interop solves most of them. These library ecosystems aren't the norm though, and the lure of "I'm going to package these together in a framework, that does things the way I like, and then brand it and help my career" for the library devs is always there (see Flask in Python for example, it was the "unDjango" until it got popular and now it's just another framework)
JustSomeNobody 7y ago
Those frameworks would be considered dead by most devs these days. If the last change log is dated older than a week they start to panic.

4 ms·

I'm aware of the well-established movement to static websites for (mostly) static sites, but what work is happening right now to counter this problem in rich we

by cardamomo 7y ago

SwellJoe 7y ago
I think the move toward micro-services (and serverless and whatever other buzzwords you want to use for a distributed loosely coupled design) is an answer to that problem, if not exactly the answer you're describing. The idea being that each small piece is easier to leave alone for long periods of time, and, should it ever become impossible to leave it alone, whether for security reasons or something else, updating it or replacing it is much easier than doing the same for a big tightly coupled pile of components.
freshhawk 7y ago
Frameworks aren't the design choice that favours stability. You take the inversion of control to get all the convention/plug-and-play/just-works features that come with it. Those are focused on developer productivity, which is a constantly shifting goal. Avoid that design and using a "libraries over frameworks" approach solves this problem but has other tradeoffs obviously, although a good ecosystem of libraries that have designed for interop solves most of them. These library ecosystems aren't the norm though, and the lure of "I'm going to package these together in a framework, that does things the way I like, and then brand it and help my career" for the library devs is always there (see Flask in Python for example, it was the "unDjango" until it got popular and now it's just another framework)
JustSomeNobody 7y ago
Those frameworks would be considered dead by most devs these days. If the last change log is dated older than a week they start to panic.