6 ms·

Angular core team here, we're pretty excited about this release. Main change, as noted, is the new View Engine. The design doc[0] is worth a read if you're int

Angular core team here, we're pretty excited about this release. Main change, as noted, is the new View Engine. The design doc[0] is worth a read if you're interested in front-end at all. Happy to answer any questions! [0] https://docs.google.com/document/d/195L4WaDSoI_kkW094LlShH6gT3B7K1GZpSBnnLkQR-g/mobilebasic https://docs.google.com/document/d/195L4WaDSoI_kkW094LlShH6g...

adam77 9y ago
is it really smaller and faster. i got the impression the payload size reduction might come at a cost to render performance?
- robwormald 9y ago
  That's discussed in the doc (and there's some metrics). Update speed takes a (minimal) performance hit, in exchange for code size reductions. We (and our colleagues at Google working on the web in general) find that the largest impact on performance comes from simply shipping less code. Edit: correction: turns out our tests show we didn't take a perf hit on updates at all, and in fact ever-so-slightly improved. So win win :D
d2kx 9y ago
1) I'm still new to this, but why would someone not use Angular Universal/why is it not default? I have only read positives, but am sure there must be a reason. 2) Why do we need Angular Material 2, when Google's official Material Components Web project is meant to be used with all kinds of frameworks and even has framework integration examples with Angular2: https://github.com/material-components/material-components-web https://github.com/material-components/material-components-w... 3) Should I follow Quickstart or CLI Quickstart in the docs to get started? I have heard that the CLI is recommended nowadays, but the Angular 4.0 release blog says the CLI isn't even stable.
- robwormald 9y ago
  1) the core of Angular Universal "graduated" into @angular/platform-server with 4.0 - previously it was a more experimental project. We're officially supporting a "renderToString()" API that can be used however you like. So really, it's brand new, and we're excited to see what the community does with it. Philosophically, pre-rendering every SPA server side isn't a silver bullet. For a ton of cases it makes a lot of sense, but we want to avoid the impression that we're positioning SSR as a replacement for making your app fast. 2) The expectation of the Material Components Web project is that everything be "wrapped" for the specific framework. Angular Material is native Angular, and we have a team dedicated to that. Polymer has a material suite as well, and most of those components can work in Angular apps too. Components for everyone! 2a) you're asking a Googler that question. We have like, 11 messaging apps. I don't know what to tell you. 3) CLI went stable today, with its 1.0 release. We'll be moving the docs over to use the CLI everywhere soon - personally, i'd use the CLI to generate a new project and then follow along the tutorials.
  - d2kx 9y ago
    Thank you, that was really helpful!
tomc1985 9y ago
Is it me or has the Angular1 site received an update? Is that platform still supported?
- kabes 9y ago
  It's still supported.
nkkollaw 9y ago
I have a question. Who thought it was a good idea to make Angular 2 incompatible with Angular 1? You had it, and you blew it. Most people aren't going to use any version of Angular, now, and have switched to React and Vue.
- pasta 9y ago
  "Who thought it was a good idea to make Angular 2 incompatible with Angular 1?" This is so much discussed that I am not going to answer that. Google it. But according to the latest StackOverflow survey [1] Angular is still bigger than you think: AngularJS 44.3%, React 19.5% [1] http://stackoverflow.com/insights/survey/2017/ http://stackoverflow.com/insights/survey/2017/
  - fatal510 9y ago
    Because Angular was the only real choice for awhile. That's like saying PHP is still bigger than you think because half the web runs on PHP but that is old legacy shit. Almost othing new and serious is using it.
    - d3ad1ysp0rk 9y ago
      What do you consider "serious"? Plenty of large applications are being built right now in PHP 7.
      - recursive 9y ago
        "Serious" means it was started by a person who regularly blogs or tweets about how to choose a technology.
    - EugeneOZ 9y ago
      There was Ember.
      - daliwali 9y ago
        Emphasis on the past tense -- "was" :)
akerro 9y ago
Can we expect Angular 4 best practices before 2020?
- EugeneOZ 9y ago
  By their plan, in 2020 it will be Angular 10.
  - owebmaster 9y ago
    And we will at least have angular 4 best practices consolidated? Because ng2 is in the past now and don't have.
  - madisfun 9y ago
    The next release is Angular 8. As every other major release is not backwards compatible, it is advised to wait until Angular 16 in 2024. /s
fareesh 9y ago
We're using the universal fork of the CLI with the recent AOT (client side) patch for a current project. Will my upgrade path be straightforward? The project is a simple content based website which consumes a ruby API that we had built earlier. We use universal for setting up meta tags, crawlability, etc.
- esistgut 9y ago
  https://github.com/devCrossNet/universal-cli/issues/101#issuecomment-288464913 https://github.com/devCrossNet/universal-cli/issues/101#issu... looks like the fork is going to be deprecated soon. I find the lack of documentation on universal a little bit frustrating, the only documentation I found is a blog post https://www.softwarearchitekt.at/post/2017/03/07/server-side-rendering-with-angular-4.aspx https://www.softwarearchitekt.at/post/2017/03/07/server-side... but the whole process is built on ng eject which removes some cli automations.
magic_beans 9y ago
"If you're interested in front-end at all" Am I being dense? Shouldn't that be everyone reading this thread?

adam77 9y ago

is it really smaller and faster. i got the impression the payload size reduction might come at a cost to render performance?

robwormald 9y ago
That's discussed in the doc (and there's some metrics). Update speed takes a (minimal) performance hit, in exchange for code size reductions. We (and our colleagues at Google working on the web in general) find that the largest impact on performance comes from simply shipping less code. Edit: correction: turns out our tests show we didn't take a perf hit on updates at all, and in fact ever-so-slightly improved. So win win :D

d2kx 9y ago

1) I'm still new to this, but why would someone not use Angular Universal/why is it not default? I have only read positives, but am sure there must be a reason. 2) Why do we need Angular Material 2, when Google's official Material Components Web project is meant to be used with all kinds of frameworks and even has framework integration examples with Angular2: https://github.com/material-components/material-components-web https://github.com/material-components/material-components-w... 3) Should I follow Quickstart or CLI Quickstart in the docs to get started? I have heard that the CLI is recommended nowadays, but the Angular 4.0 release blog says the CLI isn't even stable.

robwormald 9y ago
1) the core of Angular Universal "graduated" into @angular/platform-server with 4.0 - previously it was a more experimental project. We're officially supporting a "renderToString()" API that can be used however you like. So really, it's brand new, and we're excited to see what the community does with it. Philosophically, pre-rendering every SPA server side isn't a silver bullet. For a ton of cases it makes a lot of sense, but we want to avoid the impression that we're positioning SSR as a replacement for making your app fast. 2) The expectation of the Material Components Web project is that everything be "wrapped" for the specific framework. Angular Material is native Angular, and we have a team dedicated to that. Polymer has a material suite as well, and most of those components can work in Angular apps too. Components for everyone! 2a) you're asking a Googler that question. We have like, 11 messaging apps. I don't know what to tell you. 3) CLI went stable today, with its 1.0 release. We'll be moving the docs over to use the CLI everywhere soon - personally, i'd use the CLI to generate a new project and then follow along the tutorials.
- d2kx 9y ago
  Thank you, that was really helpful!

tomc1985 9y ago

Is it me or has the Angular1 site received an update? Is that platform still supported?

kabes 9y ago
It's still supported.

nkkollaw 9y ago

I have a question. Who thought it was a good idea to make Angular 2 incompatible with Angular 1? You had it, and you blew it. Most people aren't going to use any version of Angular, now, and have switched to React and Vue.

pasta 9y ago
"Who thought it was a good idea to make Angular 2 incompatible with Angular 1?" This is so much discussed that I am not going to answer that. Google it. But according to the latest StackOverflow survey [1] Angular is still bigger than you think: AngularJS 44.3%, React 19.5% [1] http://stackoverflow.com/insights/survey/2017/ http://stackoverflow.com/insights/survey/2017/
- fatal510 9y ago
  Because Angular was the only real choice for awhile. That's like saying PHP is still bigger than you think because half the web runs on PHP but that is old legacy shit. Almost othing new and serious is using it.
  - d3ad1ysp0rk 9y ago
    What do you consider "serious"? Plenty of large applications are being built right now in PHP 7.
    - recursive 9y ago
      "Serious" means it was started by a person who regularly blogs or tweets about how to choose a technology.
  - EugeneOZ 9y ago
    There was Ember.
    - daliwali 9y ago
      Emphasis on the past tense -- "was" :)

akerro 9y ago

Can we expect Angular 4 best practices before 2020?

EugeneOZ 9y ago
By their plan, in 2020 it will be Angular 10.
- owebmaster 9y ago
  And we will at least have angular 4 best practices consolidated? Because ng2 is in the past now and don't have.
- madisfun 9y ago
  The next release is Angular 8. As every other major release is not backwards compatible, it is advised to wait until Angular 16 in 2024. /s

fareesh 9y ago

We're using the universal fork of the CLI with the recent AOT (client side) patch for a current project. Will my upgrade path be straightforward? The project is a simple content based website which consumes a ruby API that we had built earlier. We use universal for setting up meta tags, crawlability, etc.

esistgut 9y ago
https://github.com/devCrossNet/universal-cli/issues/101#issuecomment-288464913 https://github.com/devCrossNet/universal-cli/issues/101#issu... looks like the fork is going to be deprecated soon. I find the lack of documentation on universal a little bit frustrating, the only documentation I found is a blog post https://www.softwarearchitekt.at/post/2017/03/07/server-side-rendering-with-angular-4.aspx https://www.softwarearchitekt.at/post/2017/03/07/server-side... but the whole process is built on ng eject which removes some cli automations.

magic_beans 9y ago

"If you're interested in front-end at all" Am I being dense? Shouldn't that be everyone reading this thread?