3 ms·
Sure, if it works now, it'll work ten years down the line as long as they're not doing anything nonstandard. There's a big fear that projects that become unmai
by Cthulhu_ 8y ago
Sure, if it works now, it'll work ten years down the line as long as they're not doing anything nonstandard.
There's a big fear that projects that become unmaintained suddenly stop working; this isn't correct.
Besides, all webapps are rebuilt in a 3-5 year cycle anyway so it really doesn't matter.
- pjmlp 8y agoDo you feel like rewriting a bunch of webapps written in Perl/modapache around early 2000? I know of at least one company with such a stack. Just like I know others with Web Forms, Stucts, SEAM, JSP, Zope and many other stacks in production. Not everyone re-writes their webapps, specially in companies where software is a cost center and totally unrelated to their main business.
- codingdave 8y agoSure, I'd be happy to. Converting apps from an old platform to a newer platform is reliable work, and I've done my share of it over my career. It often is structured as temporary projects, so I've had the opportunity to travel to short-term gigs in new cities while I build out platform conversion plans. Sure, not everyone re-writes old apps. But enough companies do it to make it a decent professional specialty to cultivate. And it doesn't hurt knowing both the modern stacks and multiple generations of legacy stacks when working with large organizations. Sign me up.
- lazerwalker 8y ago"Works" and "is maintained" are two very different things.
- LaGrange 8y ago> Besides, all webapps are rebuilt in a 3-5 year cycle anyway so it really doesn't matter. And I thought places I worked at tended to be terrible :/
- megous 8y ago> There's a big fear that projects that become unmaintained suddenly stop working; this isn't correct. While true, it only applies if you don't want to upgrade your lower level dependencies, ever. And given that this is a React based framework, so it's not based directly on the web platform, if it's not maintained, you'll have to port the framework yourself. Coversely, if it is maintained, you may be forced to keep up and upgrade whatever this is based on, or backport fixes if the project moves on to a newer incompatible version of the lower level dependency. > Besides, all webapps are rebuilt in a 3-5 year cycle anyway so it really doesn't matter. Eh? :D I still iterate on 13 or 9 year old codebases for my clients without re-building anything.
- btbuildem 8y agoTen years!? It will break two months from now via some ill-thought-out npm push update.