Live data from Hacker News

Angular 4.0.0 Now Available

angularjs.blogspot.com

151–160 of 360 posts

Re: Angular 4.0.0 Now Available

#151
post #64

I have been leading a good sized Angular app for work for the past 8 months, and upgrading from v2 to v4 has been painless, even while having an AOT compilation build pipeline set up - the only modifications we had to do was switch OpaqueToken to InjectorToken, to , and Renderer usage to Renderer2, and these weren't required to be done yet. We only did those changes to get ahead of the curve from the deprecation mess…

absolutely same experience in our case. Painless update with few template to ng-template ctrl+f changes.

Angular CLI stabilization is a much more important news, actually. One of mistakes of Angular team - Angular CLI had to be ready before Angular itself.

Re: Angular 4.0.0 Now Available

#152
post #106

Earlier quoted context omitted.

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.

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

No answer is better than arrogant answer.

Re: Angular 4.0.0 Now Available

#153
post #106

Earlier quoted context omitted.

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

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.

There was Ember.

Re: Angular 4.0.0 Now Available

#154
post #114

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

Can we expect Angular 4 best practices before 2020?

By their plan, in 2020 it will be Angular 10.

Re: Angular 4.0.0 Now Available

#155

I'll be that guy. I'm sure the Angular team are great people, and they're clearly talented devs... but stay away from Angular. It doesn't help with the problems you will actually face. Typed Javascript is a cargo cult. Angular just plain confusing for no apparent benefit. Dependency injection is bizarre. The distinction between modules, components, and directive is unnecessary. The Javascript community in general is…

My guess would be that static-typing is what they're trying to add albeit in an OOP form. Javascript is more of a 'Prototype' based language. They call things 'Object's but I've seen few portions of JS code that actually use OOP in the traditional sense (encapsulation, polymorphism, etc)[0]. Mostly objects are just used for namespaces for finding vars and functions. Agreed on the frameworks versus libs. I would recom…

Sorry, but this is one of my technical pet peeves. Polymorphism isn't solely an OOP concept. Every language has polymorphism of some sort. Most have several. Duck typing is an example of polymorphism actually.

You probably mean "inheritance", which is a way to achieve polymorphism, not a synonym for it.

Re: Angular 4.0.0 Now Available

#156
post #135

Earlier quoted context omitted.

I have about two years of experience with both Angular 1 and React. What was truly astounding to me was how while Angular required months of continually poring docs and Stack Overflow threads for every new thing I wanted to do, React took all of a week or two to get pretty comfortable with, and after that minor investment of time I was rewarded with dramatically increased development speed. I will never go back to us…

Euhm. Jsx and vdom are exactly About abstracting away the browser environment...

Erm, what?

JSX doesn't do any abstraction. Unless you're using React Native, you're writing HTML, just that JSX turns it into `React.createElement(...)` calls.

The VDOM is kind of an abstraction, as React Native can use the same reconciler as React, but the React (web) VDOM is just a tree of HTML DOM nodes that gets diffed against the component rerender output and the changes are applied to the DOM.

Re: Angular 4.0.0 Now Available

#157

I'll be that guy. I'm sure the Angular team are great people, and they're clearly talented devs... but stay away from Angular. It doesn't help with the problems you will actually face. Typed Javascript is a cargo cult. Angular just plain confusing for no apparent benefit. Dependency injection is bizarre. The distinction between modules, components, and directive is unnecessary. The Javascript community in general is…

Angular isn't really OOP. ES6 made JavaScript more like OOP. Typescript just applies types so you can lint your code better.

I am rewriting a React/Redux app I wrote to Angular 2. It's more readable, the control flow is easier to understand, and it's better to work on as a team. Instead of reducers and action creators, I have services separated into their own files. It's much easier for me to manage the work of others on the team.

Re: Angular 4.0.0 Now Available

#158

I'll be that guy. I'm sure the Angular team are great people, and they're clearly talented devs... but stay away from Angular. It doesn't help with the problems you will actually face. Typed Javascript is a cargo cult. Angular just plain confusing for no apparent benefit. Dependency injection is bizarre. The distinction between modules, components, and directive is unnecessary. The Javascript community in general is…

Some clarifications: 1. Angular 2 is not object oriented in the standard meaning of the term: it does not rely on inheritance or polymorphism that much. But it does rely on classes as the backing structure of your UI components. In other words, they tried to create a platform for creating widgets that compose. And more or less succeeded. This is a tried and true pattern that has been used to create complex user inter…

Observables are the most functional JavaScript library/mechanism I've worked with.

Re: Angular 4.0.0 Now Available

#159

I'll be that guy. I'm sure the Angular team are great people, and they're clearly talented devs... but stay away from Angular. It doesn't help with the problems you will actually face. Typed Javascript is a cargo cult. Angular just plain confusing for no apparent benefit. Dependency injection is bizarre. The distinction between modules, components, and directive is unnecessary. The Javascript community in general is…

Holy smokes, I can't believe how serendipitous this is. I am 5 minutes into a Pluralsight course on Angular 2. I really like the idea of Typscript, but now... now I guess back to the drawing board on what to learn.

Go with what you like. Take a look at Polymer documentation - it is very easy to pick up and works like a charm. I prefer it to react and angular nowdays.

You will still be able to use redux/whatever with it.

Re: Angular 4.0.0 Now Available

#160

Earlier quoted context omitted.

"Angular 1" is now known as Angular.js and is effectively at the end of its line. Angular 2+ is now simply Angular. All new releases follow a naming of version X.Y.Z where X indicates breaking changes, Y non-breaking new features, and Z is bug fixes. Version 3 is being skipped over due to poor naming of the related Angular Router lib. http://angularjs.blogspot.com/2016/12/ok-let-me-explain-its-...

It seems that lockstep versioning makes semantic versioning less meaningful A major version bump for a module could signal a breaking change, or it could just be due to the packages it's locked to having had a breaking change

A breaking change in your dependencies is a breaking change for you. If it weren't, minor version upgrades would cause you to pull in incompatible dependencies.

This is why keeping your dependency list as tiny as possible is imperative.

Post reply on HN