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."

5 of 121 comments (clear)

  1. duh.... by theNetImp · · Score: 4, Interesting

    That's because it's a complete rewrite, and anyone who has been around for the last year who develops Angular already knew this.

    1. Re:duh.... by K.+S.+Kyosuke · · Score: 5, Funny

      Or, they're jealous of Swift 3.0.

      --
      Ezekiel 23:20
  2. Quire a stir... by Chrisq · · Score: 5, Funny

    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

    1. Re:Quire a stir... by jrumney · · Score: 4, Funny

      It is a new Slashdot new policy of being fair and balanced. An Emacs story has to be followed immediately by a similar but weeks old VIM story, and a Swift story has to be followed immediately by a similar but years old Angular story.

  3. Re:Thick client JS frameworks are the new Flash by Anonymous+Brave+Guy · · Score: 5, Informative

    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.