Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Angular 2 Core

docs.google.com

Post reply on HN
Print view View original

141–150 of 279 posts

Re: Angular 2 Core

#141

Post by joshuacc »

rantanplan wrote: post #132
nobleach wrote: post #112

Earlier quoted context omitted.

> The front-end is just 1-10% of any serious system and yet, in the JS world, it takes 90% of the time building it and maintaining it. It just doesn't add up. Wow, I want you to come work for me for a week. The front end is what interfaces with the user - your client - the one whom is paying money. You may hate JS, but it is the tool that we use to build interaction.

You misunderstood or I didn't express myself correctly. I don't want to underplay the importance of the front-end, or in general the interfaces and what that means for bringing value to a product. But however you spin it it's not the core technology. You could make the same point you made, by saying the same about the marketing/sales department. Yes, it's how you bring customers and without it you'll probably fail to…

That depends very much on what type of product you're building. I work on two "serious" enterprise products using Angular, and for one of them the "core technology" is evenly split between the Java backend and the Angular application, while for the other the Angular application is clearly the "core technology."

Re: Angular 2 Core

#142

Post by rdsubhas »

realusername wrote: post #47

I'm quite disappointed by this presentation, I see only new syntax everywhere for approximately zero benefit. There is not even any mention to the Object.observe integration which would be the most exiting feature to improve Angular apps. Angular looks and feels now like a Java framework, with ugly decorators and bloated APIs, that's really sad...

Came here to say this. In the last slide, when they were piling "RIP Directives", "RIP DI", "RIP Modules", etc., the only thing I had in mind was "RIP Angular". Very disappointing.

Re: Angular 2 Core

#143

Post by pcwalton »

skore wrote: post #36

To everybody trying to make this into a tech fight about Angular vs. React/whatever, I've been repeating this like a mantra and even mentioned it in a talk on javascript once[0]: You can argue about the minor details of the tech stack till you turn green and blue, but Angular wins because it succeeds in the only metric that really counts. jQuery: (for reference) 5,656 commits 7 branches 122 releases 199 contributors…

If popularity is the only metric that counts, then logically you should also dismiss anything other than PHP, MySQL, and Apache for the server side out of hand.

Re: Angular 2 Core

#144

Post by joshkpeterson »

woah wrote: post #126
davidholmesnyc wrote: post #92

I feel that Angular changes too much in HTML to be considered useful for long term projects.The new syntax is also disturbing. My ideal MVC for front end utilizes regular javascript and html tags. At most just add data-ang-click="" something like that instead of "(click)" the latter isn't even valid HTML. Sometimes I think Angular is mainly popular because it's supported by Google. If any regular developer made these…

I've been using Vue.js recently, it's a lot like Angular (inspired by?), without all the crazy nonsense: http://vuejs.org/api/

Terrible name.

Edit: Other framework name ideas ~ Modil.js, Controllr.js, Framework.js, Class.js, js.js

Re: Angular 2 Core

#145

Post by susi22 »

skore wrote: post #36

To everybody trying to make this into a tech fight about Angular vs. React/whatever, I've been repeating this like a mantra and even mentioned it in a talk on javascript once[0]: You can argue about the minor details of the tech stack till you turn green and blue, but Angular wins because it succeeds in the only metric that really counts. jQuery: (for reference) 5,656 commits 7 branches 122 releases 199 contributors…

Every Angular documentation page has a link to edit the doc right in github.

The same is true for React but not for Amber nor jQ.

However React's docs are much simpler than Angular since it only provides the View and the docs are only a few pages really.

Re: Angular 2 Core

#146

Post by zghst »

davidholmesnyc wrote: post #92

I feel that Angular changes too much in HTML to be considered useful for long term projects.The new syntax is also disturbing. My ideal MVC for front end utilizes regular javascript and html tags. At most just add data-ang-click="" something like that instead of "(click)" the latter isn't even valid HTML. Sometimes I think Angular is mainly popular because it's supported by Google. If any regular developer made these…

I see Angular 2 as more of going native, conforming with the Web Components API as well as adopting modern ES6 (since it's being finalized this year and being implemented almost everywhere).

I like that they've modernized their API, because of how it is designed currently it would be hard to take it to the next level using ES6, Angular 2 is a good call.

Re: Angular 2 Core

#147

Post by g13n »

skore wrote: post #36

To everybody trying to make this into a tech fight about Angular vs. React/whatever, I've been repeating this like a mantra and even mentioned it in a talk on javascript once[0]: You can argue about the minor details of the tech stack till you turn green and blue, but Angular wins because it succeeds in the only metric that really counts. jQuery: (for reference) 5,656 commits 7 branches 122 releases 199 contributors…

Interesting.

But I see the comparisons is between Apples and Oranges here.

jQuery is a DOM library.

Angular and Ember are client-side MVC libraries.

React is an [isomorphic] UI library.

IMHO Angular/Ember and React and jQuery don't even compare in the same planes.

I'm not supporting React here, but its quite new and off late its getting a lot of traction. So the number of contributors and commits for a library that's quite new is astonishing!

And frankly I feel Angular team made a huge mistake by completely changing the syntax which makes it difficult to be adopted by anyone that knows/uses Angular 1.x.

Re: Angular 2 Core

#148

Post by zghst »

omarelamri wrote: post #117
pedalpete wrote: post #10

I'm not sure I've seen a framework with such a drastic API change, particularly such a young API. I find that very threatening. Having spent a considerable amount of time learning and working with Angular.js, not only does this appear to be massively breaking changes, but it would also break 3rd party directives which has been a great benefit to building the Angular community. This makes me think that Angular didn't…

I agree. There is virtually no way you can smoothly upgrade an Angular 1 project to this. You'd have to redo most of it from scratch. There are a lot of huge projects that are built on Angular 1 -- many enterprise products too. And this is a huge blow to maintenance. It might be a reason for a lot of people dropping Angular and going for something that makes more business sense. Maybe it's React's time to shine.

The thing with React is that either Facebook's engineers are incredibly prescient or lucky. React very is really well designed and feels natural with ES6.

It's so incredibly designed, even without the ES6 optimizations of 0.12.0 (coming soon) you can code today in ES6 (I use 6to5 with JSX transformer harmony just in case).

Re: Angular 2 Core

#149

Post by bsimpson »

tracker1 wrote: post #6

I am literally working on a new project, starting to code the front end as of a day ago... I using Flux+React (nearstack.io, plug) around the Yahoo implementation of Flux's model. The down side, is this will be how things are for the next 3-5 years for the life of the site/application. Angular 2 looks really cool... they seem to be embracing the shadow-dom concepts (like polymer) as well as es6-style import directive…

FWIW, React will be in ES6 (with native classes and imports) before they tag 1.0. In fact, React 0.12 has some breaking changes to prepare for that transition.

Re: Angular 2 Core

#150

Post by zghst »

chubot wrote: post #139
Cthulhu_ wrote: post #34

Earlier quoted context omitted.

> Angular was started 5 years ago.. quoted just to remind people that Angular as we know it is older than most other single-page app frameworks - even if it only became popular a year or two ago.

Yeah I heard of Angular a long time ago, but then everyone started using it in the last year. What happened? Did they change something that all of the sudden made it popular?

Data binding, directives, MVC front end + the adoption of Node is what made it popular IMHO.
Post reply on HN