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

Angular 2 Final Released

angular.io

Post reply on HN
Print view View original

411–420 of 452 posts

Re: Angular 2 Final Released

#411

Post by gbog »

hackerboos wrote: post #316
gbog wrote: post #287

Earlier quoted context omitted.

Microsoft stuff not allowed in my stack...

Why? It's Apache 2.0 licensed...

People seem to have forgotten that MicroSoft was a gigantic threat to our industry, and still is. It owns 98% PCs world wide. What would we think if 98% of gaz stations worldwide where belonging to one company? That would be dangerous, right? Same with MS except it's worse, because PCs are eveyrwhere controlling everything. It's Big Brother in real life. Just imagine one moment how many critical decisions having world wide impact on the life of billions of people are done using Excel? What if Excel was remote controlled?

So, no, sorry, I don't eat that stuff. Bill Gates has built the most dangerous edifice and no amount of charity will save him from the Hell of digital beings.

Re: Angular 2 Final Released

#412

Post by szines »

tutuca wrote: post #395
szines wrote: post #214

Earlier quoted context omitted.

You probably missed the best option: Ember.js. It has all the best from other frameworks and it looks the only serious player out there.

And exactly the worst performance of them all. Coupled with the kind of spooky side effects down your pipeline that you thought long gone since the first releases of ruby on rails...

Performance? You compare 100 ms with 150 ms?

But actully, the performance is not a question anymore, with the new Glimmer Engine 2 Ember will be the fastest framework, with full backward compatibility.

Re: Angular 2 Final Released

#413

Post by Sacho »

Nemcue wrote: post #195
NhanH wrote: post #77

Earlier quoted context omitted.

Any chance you can do a quick cons review too? Specifically comparing to the weakness of Angular 1 like bloated complexities, issue with custom directives or scope life-cycle.

Cons: 1. Typescript. If your team isn't familiar with it it's not trivial to get everyone on board. The up-front cost can absolutely be worth it in the long run, but there's some friction in the day-to-day work with managing type definition files and looking up esoteric lint-errors from the Typescript compiler. 2. RXJS. Canonical NG2 should use Observables, and rxjs is not a trivial library to learn the ins and outs…

> 5. Sub-par debugging experience.

I've worked with AngularJS and React. After spending enough time with each framework that I'm "productive" with them and don't get constantly confused by what's going on, this is now by far the most important reason to me when adopting a framework. React(and Redux) just spoil you with an awesome debugging experience, and it's just painful for me to go back to any set of tools that takes some of that away. The rest of the points I've already "suffered" through with AngularJS, and it is my opinion that they are a rough, but surmountable cost. Having a poor debugging experience, however, just kills my willingness to work.

(For the record, AngularJS has some debugging aides - you can inspect scopes pretty easily given a DOM element. However, the watches and digest cycles, which do all the heavy-lifting, are pretty much opaque - you need to have a good understanding of how your watch expressions are compiled into watch functions and place conditional breakpoints deep within the framework in order to inspect why a certain watch is not being called/being called too many times)

Re: Angular 2 Final Released

#414

Post by pekk »

limelight wrote: post #257
electrotype wrote: post #240

Serious question : Why are SPA frameworks so popular these days? When someone asks "What should I use for web development?", It's now all about React/Angular/Ember/etc. But when I look at how are built the sites I like and visit frequently, I'd say 95% of them are not SPA, they are classic sites where the server generate each page (sometimes with one or two Ajax requests)! The Single Page pattern is great for desktop…

> I think I still prefere the "feel" of classic websites. Your hacker biases are showing. The sites where 95% of people spend most of their time (Twitter, Facebook, Instagram, etc.) are all built as single page "applications." Users expect rich interactivity from websites these days and are usually not tolerant of UI refreshes. The comparison is not to "desktop" applications but to mobile apps. Users expect a mobile…

Hyperlinks are a form of interactivity. That aside, there is no reason why one cannot have many individual pages which each have their own interactivity.

If you are going to argue that this is about "hacker bias" you will have to show user studies, not poll JS developers.

Re: Angular 2 Final Released

#415

Post by j_jochem »

doczoidberg wrote: post #187
j_jochem wrote: post #128

Earlier quoted context omitted.

As far as I know, Google does index SPAs that are only rendered in the browser.

Google does not index my ng2 site without prerendering. There will be always limits for search engines on interpreting js.

That's interesting. I previously researched this with regard to React apps, and the tenor was that server-side rendering was no longer required in order to get indexed by Google.

Google itself has this to say:

https://webmasters.googleblog.com/2014/05/understanding-web-...

Have you tried to figure out the cause using Search Console?

Re: Angular 2 Final Released

#416

Post by Kiro »

simonrobb wrote: post #297
Kiro wrote: post #178

Earlier quoted context omitted.

Who has switched? Do you have any example?

I've just finished my first major redux project and found it incredibly slow to develop with. Write an action type constant/action creator/dispatch/reducer/mapStateToProps just to show an element in response to a mouse click? I found myself cutting corners on the UI because the amount of code I'd have to write makes it seem like a huge task. I'll be evaluating mobx for my next project, definitely, along with Relay. I…

That's interesting. I've only used redux for one project and you may be right. It is tedious to all those things for every little action.

Re: Angular 2 Final Released

#417

Post by tigershark »

EugeneOZ wrote: post #39

I use Angular 2 in production since November 19, 2015 (alpha.46). Currently I've built 3 web apps (40, 60 and 20 components each), 3 mobile apps (with Ionic 2) and my employer have plans for more apps. Breaking changes during alpha stage were expected, so I didn't have issues with it. Most positive things I want to highlight: 1. Components are encapsulated and truly reusable (and without dependencies hell). 2. You do…

I am really surprised to know that there are people that use an alpha version in production. I would never ever do that even if it was allowed, and obviously it is not allowed in my company.

Re: Angular 2 Final Released

#418

Post by philippz »

elmigranto wrote: post #249
philippz wrote: post #159

Earlier quoted context omitted.

For economical reasons. We decided between ng2, React and Vue.JS: https://docs.google.com/spreadsheets/d/1ULB2GjA3ytXAN_Sn-fEy... React would mean to rewrite your whole application as it has a totally different basic concept. Following the ng2 migration path you're able to migrate slowly.

> React would mean to rewrite your whole application I don't see what is a problem to just drop in React into ` ` tag and use for single part of the page, gradually refactoring stuff.

That would mean to live with a hybrid solution, more overhead and a bigger footprint. We currently deploy our JS base to web, Android and iOS (Cordova/Phonegap). It is and will remain one code base to be flexible and fast until we get "product/market fit" and until we have KPIs where we want them. This is cost effective but comes with the slowness of web-engine rendered apps. Therefore performance is big factor and we're optimizing for that. By switching to ng2 we have have a cost-effective and performant compromise.

Re: Angular 2 Final Released

#419

Post by joe563323 »

tigershark wrote: post #417
EugeneOZ wrote: post #39

I use Angular 2 in production since November 19, 2015 (alpha.46). Currently I've built 3 web apps (40, 60 and 20 components each), 3 mobile apps (with Ionic 2) and my employer have plans for more apps. Breaking changes during alpha stage were expected, so I didn't have issues with it. Most positive things I want to highlight: 1. Components are encapsulated and truly reusable (and without dependencies hell). 2. You do…

I am really surprised to know that there are people that use an alpha version in production. I would never ever do that even if it was allowed, and obviously it is not allowed in my company.

alpha guys do that.

Re: Angular 2 Final Released

#420

Post by EugeneOZ »

tigershark wrote: post #417
EugeneOZ wrote: post #39

I use Angular 2 in production since November 19, 2015 (alpha.46). Currently I've built 3 web apps (40, 60 and 20 components each), 3 mobile apps (with Ionic 2) and my employer have plans for more apps. Breaking changes during alpha stage were expected, so I didn't have issues with it. Most positive things I want to highlight: 1. Components are encapsulated and truly reusable (and without dependencies hell). 2. You do…

I am really surprised to know that there are people that use an alpha version in production. I would never ever do that even if it was allowed, and obviously it is not allowed in my company.

We started using it for internal web app, were satisfied by the level of quality and then switched main site to Angular 2.
Post reply on HN