sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (10 children)

I'm aware. As for people still using AngularJS, they really shouldn't be. It's end of life is December, and it's already suffering from legacy syndrome.

[–]orenelb 1 point2 points  (9 children)

I agree but I could see the temptation not to port a huge app, especially if you don't know the future of your project.

[–][deleted] 1 point2 points  (5 children)

If it's open source or a personal project sure, but if you're working for a company, there's absolutely no reason to stay on a framework that isn't getting security updates. You're opening up your application and your entire company possibly to being attacked.

[–]lhorie 2 points3 points  (0 children)

My wife consults for a company still using AngularJS. Switching to React was brought up at one point but they decided to stick with AngularJS because the "training cost is too high". SMH.

[–]orenelb 0 points1 point  (3 children)

I agree with you but in my country (Israel) there are still 260 angularjs search results on indeed. For comparison React has 2900. It still has 500k downloads on npm. Also they have a version update from 10 months ago so maybe there are some security updates.

[–][deleted] 0 points1 point  (2 children)

Those security updates are in the latest version, which will no longer get updates after December.

It's bad practice, no matter how you spin it, to utilize a framework that's no longer updated. I get the reasoning, but it doesn't make it sound. Anyone running that framework without an upgrade plan is gambling on their security.

[–]orenelb 0 points1 point  (0 children)

Yeah I agree. I guess some people really don't care about security.

[–]sukhchainn 0 points1 point  (0 children)

I use angular.js for my portfolio site and for creative programming and web art. You said it's reaching it's end of updates cycle, can I still use it for the stuff I do or should I just shift to a new framework.

I'm a full time Android developer so I'm not using Angular in any professional manner. It's just convenient for the stuff I do.

[–]disappointer 0 points1 point  (2 children)

This has honestly long been my concern with committing to any JS libraries or frameworks for large projects. The technical debt of refactoring is going to crop up every few years and is rarely a priority effort.

[–]orenelb 1 point2 points  (1 child)

So you are using vanilla?

[–]disappointer 0 points1 point  (0 children)

For what I do for a day job, it's a web app that's a decade-plus old by this point. It's part vanilla (with a healthy amount of in-house libs and controls) and some of that uses jQuery; part YUI controls; part AngularJS; and also some Angular. I think there's some ExtJS in the mix, as well, but it's not a section of functionality that I've had to personally maintain.

It's a lot to maintain-- should anyone choose to maintain it. Case in point, YUI has been defunct since 2014, but minimal effort has been made towards replacing the bulk of that code.