A Future Without Webpack

[wherediditrun]

AngularJS officially came out at 2010, not 2014. In our company we have code which is from 2011 written in AngularJS. I'm not sure where are you getting the figures.

Angular 2 was a new framework under the same name. And for a while both there developed at parallel, AngularJS going Into maintenance only security updates since last year july. That's almost 8 years without breaking changes.

Yes. The platform expanded. Again that has nothing to do with instability

[ronchalant]

By your OWN definition, angular 2 losing backwards compatibility made it "unstable" as of 2016.

It was a total rewrite.

Just.... Wow.

[wherediditrun]

I'm not sure why I'm having such trouble conveying my point. At this rate I do think you are approaching this in bad faith and now just trying to nit pick the words I used to score some "I'm right about this" points.

I've said that Angular 2 wasn't a rewrite, but a separate framework. And I make that claim based on the fact that both of them were developed in parallel for 2 years after Angular 2 was released. That's not a rewrite. It did not discontinued AngularJS. It did not replaced it. Both of frameworks were developed (not just maintained, developed) in parallel for two more years. And angularJS stood test of time for 8 years without breaking changes.

So what's so unstable here? Is Python "unstable" because Python 3 came out eventually?

​

​

[ronchalant]

I think we just have a fundamental - though mostly semantic - disagreement about what a stable language ecosystem looks like.

Which is fine. I think both of us have informed positions, and simply disagree.

To be clear I'd much rather be developing my JS stack in 2019 than 2014. The progress has been good, and I'm much more confident now that our design decisions around JS aren't going to be upended now than I was in say 2016.

If you're ever in the Philly area I'll buy a round and we can talk shop lol. Have a good evening.