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

381–390 of 452 posts

Re: Angular 2 Final Released

#381

Post by cygned »

mattmanser wrote: post #268
woah wrote: post #203

Earlier quoted context omitted.

Do you really want to point and click around on everything all the time? Maybe read the documentation on what various flags mean when you decide to use something.

Yes, the mouse + GUI is a lot more usable to me than typing in a CLI. The command line is from when we had terminals. And worse still, yes, that's the case for most people. Most people prefer using mice + GUIs. Why are we going back in time? Why can't we have tools that work as both GUIs and CLIs? CLIs are great for automation (and keyboard obsessed users). GUIs are great for discoverability and making it obvious to…

I'd disagree here. All the most productive developers I know make heavy usage of the CLI, and some of them, including me, are even developing in it with tools like vim or Emacs.

Re: Angular 2 Final Released

#382

Post by ergo14 »

Bahamut wrote: post #220
ergo14 wrote: post #135

It is interesting how people are debating here, angular this, react that... Yet there is Polymer that just works, has a great ecosystem, awesome material design support and is a breeze to work with (+ its fast too). Right now there was 2.0 announcement and new version really supports easy migration path unlike Angular 2.x.

Polymer also has a lot of negatives - it still only publishes on bower for example, and the whole vulcanizing situation is sort of bleh. It also uses HTML imports for its components, which is unnatural and sort of munges concerns with the whole ES module import system - this includes importing HTML files for more traditional things such as XHR. To me, all these things put Polymer far behind the curve as something I'm…

Whats wrong with vulcanizing? The product is the same you would get with grunt/gulp and what people were doing for years building their js files.

Is bower less reliable than npm? (I do more python work than JS)

Re: Angular 2 Final Released

#383

Post by uremog »

throwanem wrote: post #216
Nemcue wrote: post #195

Earlier quoted context omitted.

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…

> I tried to stay very far away from Angular 1 since I found its documentation to be very low quality (probably a symptom of Angular 1 being poorly engineered as well). I haven't found either of these to be the case. Is your experience recent? If so, will you expand on it? I like Angular 1(.5) quite a bit, but I'd be interested to hear more about a different perspective.

In 2014 when I started using Angular, I could not make heads or tails out of the docs and went stright to 3rd party tutorials. Today, if I know what I need and just need to remember the syntax, I will go to the official docs, but if not, I search elsewhere. I still don't think it's suited for learning.

Re: Angular 2 Final Released

#384

Post by xeromal »

ehfeng wrote: post #186
mattmanser wrote: post #156

Earlier quoted context omitted.

That's a general javascript problem though as soon as you involve any third party library. Something funky going wrong when jQuery's involved? Good luck stepping through that.

May want to give Sentry a try for error logging: sentry.io/for/angular2 Let us know if there's anything we can be doing better :)

That's pretty slick. Thanks for sharing.

Re: Angular 2 Final Released

#387

Post by morsmodr »

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…

No thanks for the next 1 year, after Backbone, Angular 1.x, React-Redux, I am going to take a break from learning a new framework. React-Redux is simplistic with most of my coding being JS, I don't want to keep looking up documentation for ng-this and ng-that. If the framework really takes off in 12-18 months then I might consider investing some time in it.

Re: Angular 2 Final Released

#388

Post by slmyers »

namelezz wrote: post #100
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…

Do you know of any large projects that use Angular 2? I just want see how readable the projects are.

There is an example of an ng2 app using ngrx platform that is reasonably large -- ngrx is a redux using rxjs (more-or-less).

https://github.com/ngrx/example-app

Re: Angular 2 Final Released

#389

Post by charrondev »

omouse wrote: post #377
limelight wrote: post #257

Earlier quoted context omitted.

> 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…

And the performance of all those is just garbage in Firefox on a 3 yr old laptop and isn't that much better on mobile. They're fantastic for forcing people to buy new hardware just to look at information :|

Well it must not be a very good 3 yr old laptop then? And firefox isn't exactly the slimmest or lightest web browser. Sucks ram just as bad as chrome used to. My 3 year old laptop can handle all of the google services just fine.

Re: Angular 2 Final Released

#390

Post by charrondev »

scottmmjackson wrote: post #245
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…

SPA frameworks are not all-encompassing tools for buildong all web pages. Notably, trying to SEO a SPA is frustrating at best and impossible at worst. However, in b2b use cases where SEO isn't an issue, SPA frameworks are ideal for coordinating a static-site dynamic-api system.

React, Angular 2, Vue 2 and some other SPA frameworks or view systems all support server-side rendering with very little coercion nowadays. That combined with google executing javascript during indexing means that SEO isn't nearly the issue it used to be.
Post reply on HN