Slashdot Mirror
Google's New Angular 2.0 Isn't Compatible With Angular 1 (techcrunch.com)
An anonymous Slashdot reader quotes TechCrunch:
When Google announced Angular 2 in 2014, it created quite a stir in the web development community because this new version wasn't just an update, but instead a complete rewrite that wasn't compatible with the older version... "Angular 1 first solved the problem of how to develop for an emerging web," the company writes... "Six years later, the challenges faced by today's application developers, and the sophistication of the devices that applications must support, have both changed immensely."
Announcing the final release version of Angular 2 last week, Google thanked the open source community, saying "We are grateful to the large number of contributors who dedicated time to submitting pull requests, issues, and repro cases, who discussed and debated design decisions, and validated (and pushed back on) our RCs." TechCrunch writes that Google's Angular team "now also recommends that developers use TypeScript to write their apps...a Microsoft-developed superset of JavaScript that adds features like static typing and class-based object-oriented programming."
Announcing the final release version of Angular 2 last week, Google thanked the open source community, saying "We are grateful to the large number of contributors who dedicated time to submitting pull requests, issues, and repro cases, who discussed and debated design decisions, and validated (and pushed back on) our RCs." TechCrunch writes that Google's Angular team "now also recommends that developers use TypeScript to write their apps...a Microsoft-developed superset of JavaScript that adds features like static typing and class-based object-oriented programming."
That's because it's a complete rewrite, and anyone who has been around for the last year who develops Angular already knew this.
When Google announced Angular 2 in 2014, it created quite a stir in the web development community because this new version wasn't just an update, but instead a complete rewrite that wasn't compatible with the older version
Such a stir that it was noticed by Slashdot in 2016
Where can I download this "progressive enhancement" framework that you speak of?
.. are partly the constantly mutating APIs! Irony, much??
I think you have to start by running
npm install knowledge skill wisdom
They have a common dependency on experience, so it can be a bit time-consuming to get them all, maybe a few years. Also, depending on your environment, some of them may fail to install.
The good news is that you've got them, it's very quick to set up other useful things like stability, future-proofing, and even progressive-enhancement, with minimal dependencies on other JS packages.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
Angular 1 first solved the problem of how to develop for an emerging web,"
*What* "emerging web"? The web has been around for decades now. The only thing that's changed is the fact that there are now even more unnecessary layers of javascript on top of everything than there was before.
"Six years later, the challenges faced by today's application developers, and the sophistication of the devices that applications must support, have both changed immensely."
Yeah, because asshats like you keep reinventing the wheel and forcing everyone to relearn what they already knew, throwing away hard won lessons in the process, and resulting in poorer quality code overall because no particular language or API seems to last long enough anymore for people to become proficient enough in it to deal with all the inevitable bugs.
Why even call it Angular if it's completely incompatible with the previous version?