News for hackers. Stuff that matters.
Re:It’s OK to Still Use Angular 1 in 2017 by eksemplar on Monday June 05, 2017 @03:06AM (#14485781)
We still use a range of old technologies where I work because it's where our resources are invested. We're steadily rescooling people, but that takes time, and even when every one is up to speed it'll probably still be 6 months before they are able to deliver the same quality at the same speed.

We also have around 350 different (minor to major) systems running, which won't be upgraded in a foreseeable future.

Using old technology is a consequence of reality, but that doesn't mean it's a good idea. It's very dangerous to get complacent, and I think especially so, with something so replaceable as Angular 1.

Re:It’s OK to Still Use Angular 1 in 2017 by akras14 on Monday June 05, 2017 @03:31AM (#14485873)
It is replacable, but the cost of doing so is pretty significant in a small start up.

The only real business benefit that other frameworks provide is that they make it easier to hire for. If things continue as they have been in a year or two we will have a bunch of new cool frameworks, and current super stars will become old. So why bother switching yet?

For now Angular 1 is not broken (assuming known limitations are OK for businesss need) so why fix it?

Re:It’s OK to Still Use Angular 1 in 2017 by eksemplar on Monday June 05, 2017 @04:30AM (#14486077)
Aside from our own development we also purchase around 10-25 IT systems a year. Some of these come from minor firms, sometime we even buy development directly from student startups where we do a lot of the usecasing and teach them on real world application, and we wouldn't hire someone doing Angular 1.

That's just us of course.

Re:It’s OK to Still Use Angular 1 in 2017 by akras14 on Monday June 05, 2017 @09:32AM (#14487441)
Why would you not hire someone doing Angular 1? Do you think it's THAT different from React or Vue?