6 ms·
Please expand further. I would be very interested in what you base this comment on and examples of better versions for these.
by SeanDav 14y ago
Please expand further. I would be very interested in what you base this comment on and examples of better versions for these.
- freehunter 14y agoJavascript libraries come and go, especially as Javascript is a tepidly developing language. It's very likely that in a few years the current crop of JS libraries will be out of date and people will have moved on to something else. Compare this to the relatively stable world of LAMP. Linux hasn't changed, nginx is popular but Apache is still the standard, databases come and go but MySQL is still here, and PHP is still quite a popular choice for web applications. Will the MEAN stack stand the test of time? How many forgotten JS libraries litter the timeline of web development?
- don_draper 14y agoRight on. That's why I'm sticking with EJB's and Oracle.
- wprl 14y agoAs a user of MEBN stack for the past 2 years, I don't see this being the case for server side JavaScript. Node will still be around, and it's hard to believe Mongo is half way through its entire lifecycle. For browser side packages, sure, there's churn. But that's true of any web stack, and at the pace browsers develop, it's worthwhile revisiting those library choices more than once a year anyway.
- marknutter 14y agoI think you're getting Javascript libraries confused with Javascript frameworks. Libraries have come and gone, yes, but there is a clear standard now in jQuery, and as such it's safe to assume it can be included in a stack for a long term project. Frameworks for building complex Javascript applications, however, are relatively new to the scene. One of the major offerings will eventually become the jQuery of Javascript frameworks and become the de facto standard, safe to include in a stack for a long term project as well.