Live data from Hacker News

Angular 2 Beta released

angularjs.blogspot.com

231–240 of 273 posts

Re: Angular 2 Beta released

#231
post #115

Earlier quoted context omitted.

Welcome to the programming world, js developers.

I never jumped on the CoffeeScript bandwagon .. I know people love it, just not me. Hence unlikely I will try TypeScript. Despite all its glaring flaws, javascript is an insanely productive language due to excellent mix of features. To improve upon that Id need to go to lisp / clojure [ but it lacks wide commercial acceptance .. not a criticism at all ] I'm actually wary of using the newer additions to javascript lan…

Es6 has destructuring and tail calls, too.

I also like cljs, mostly in a text editor.

Code quality it is the ultimate time saver. I prefer reading concise, literate source to exploring/churning APIs.

Re: Angular 2 Beta released

#232

Earlier quoted context omitted.

> ReactJS has slaughtered the front-end market share (in a good way) and completely taken develo Do you have a citation for that? I still see tons of user land projects using angular 1.

I am not talking about market share, I am more referring to sentiment in the community towards React. Just based on my observations, front-end developers love React and many more seemingly warming up to it. Considering React is still a new library, give it some time, but it does not take a trend to see that it is gaining popularity while Angular 1.x has peaked in my opinion and 2.0 will take a lot of convincing to ge…

This mirrors my experience. I left Angular 1.x for React and would need a huge amount of convincing to learn Angular 2.x. The killer feature of React for me is the full stack approach - react, react native, relay & graphql.

Re: Angular 2 Beta released

#233
post #227

Congratulations to the Angular 2 team on shipping before Christmas. The estimate was originally somewhere around early 2016, so this is a huge deal for them to get this out before the year was up. Unfortunately, Angular 2 launched into beta too late. In the amount of time that Angular 2 has taken to get to beta, ReactJS has slaughtered the front-end market share (in a good way) and completely taken developers by stor…

I usually evaluate frameworks based on the job market. In the UK there are currently 298 jobs for Angular and 109 for React (www.cwjobs.co.uk). React is up on around 40 jobs at the beginning of the year. The reality is that you should know Angular AND you should know React. These are not mutually exclusive.

When you say "up around 40 jobs", do you keep a historical graph on these stats? It would be an interesting read!

Re: Angular 2 Beta released

#234

Earlier quoted context omitted.

I'm not sure if that's entirely accurate Here's a chart where you can see daily download counts for react, angular, and angular2. http://npmcharts.com/compare/angular,react,angular2 React does indeed have about 4x as many daily downloads, but (Angular 1 + 2)'s download counts are ~5x what they were a year ago. (iirc the ng-europe RIP Angular fiasco happened in October 2014)

Worth noting that the onboarding process for each framework is different. Getting started with react pushes you to npm. Angular 1 pushes you to CDN, so I'm not sure how useful this graph is. Interesting, nonetheless.

That's a great point. I wonder if that would change with Angular 2

Re: Angular 2 Beta released

#236
I've played around with Angular 2 quite a bit the last few weeks. These are my (early) views for anyone interested:

* Templating syntax is intuitive after an hour or two

* Decorators are great! (sidenote: Warning Babel6 decided to remove them until the spec settles down)

* Typescript I'm undecided about. Its a bit of a pain to work with and tooling is still early days e.g. if you want to import a single js file/lib, you create a Type definition file (.tds) just for that. And if you don't want to document every interface in that .tds, then you can give it an "Ambient" aka "whatevs" definition. But in that case it will not be retain its semantics.

* The new component router wasn't ready for prime time 2 weeks ago. I doubt that has changed. And frankly, I feel a bit uncomfortable with how magical it is. That could change though, I know allot of effort is going into it.

* One of the best things is losing many of the hacky artifacts of Angular1 (pseudo-modules system, 9 types of component, config phases etc etc)

* IMHO the lack of opinion built into the framework will still cause allot of foot-shooting around the globe, especially compared to Ember or Aurelia.

That said, if I was going to start a large enterprise project right now, I'd SERIOUSLY consider the core being written in Angular 2 + Redux. I'd have to revisit Ember before I had that decision though, its been over two years ...

Re: Angular 2 Beta released

#237
post #233
post #227

Earlier quoted context omitted.

I usually evaluate frameworks based on the job market. In the UK there are currently 298 jobs for Angular and 109 for React (www.cwjobs.co.uk). React is up on around 40 jobs at the beginning of the year. The reality is that you should know Angular AND you should know React. These are not mutually exclusive.

When you say "up around 40 jobs", do you keep a historical graph on these stats? It would be an interesting read!

I just remember looking into various frameworks at the beginning of the year and trying to evaluate if React was "worth" getting into.

I'm very pragmatic about frameworks. Yes, React might be technically better than Angular 2, but it has to be better at putting food on the table. It probably will be.

In the meantime, there are a lot of Angular 1 projects that will need migrating to Ang 2.

Re: Angular 2 Beta released

#238
post #70

Earlier quoted context omitted.

I've been using TypeScript for a few months now and have been so impressed with it that I am beginning to favor Angular 2 over React just because of Angular 2's TS integration. TypeScript basically made JavaScript more powerful and a whole lot more fun for me. I feel so much better about slinging around parameters now that I know my IDE will catch type/parameter mismatches before I run the code, before I build it, ev…

> I've been using TypeScript for a few months now and have been so impressed with it that I am beginning to favor Angular 2 over React just because of Angular 2's TS integration. As a big fan of types myself, I hear you. Have you tried using flow with react? I wonder how they compare.

I can't tell you anything about flow (no experience and no interest), but I have no played a little bit with React & Typescript as well as Angular 2 & Typscript. Imho both configurations work quite good:

What I liked about React is that I also got type checks in JSX (compiler tells me if the types that I assign to props are correct). I don't get that kind of type checks for angular2 templates. If I assign something wrong there then it blows up at runtime.

What I disliked about React is that the ecosystem doesn't embrace typescript. For most 3rd party components that I tried there were either no type definitions available or they were broken (which is often worse - because then you can't assign props that are actually valid).

For Angular2 at least the framework is already typescript-first (so we have automatically up-to-date type definitions through the compiler), and I would hope many 3rd libraries follow that design.

Re: Angular 2 Beta released

#239
post #54

Earlier quoted context omitted.

If only typescript was written by facebook or google then people wouldn't hate it.

People hate Dart, written by Google, for same reason: it is better to stick to single language, for better ecosystem, than to fragment it. I, personally, just ignoring Dart, CoffeeScript, TypeScript, etc. Life is short.

We're stuck with javascript due to historical reasons, not because it's any good. I think that treating it as a bytecode, binaries, etc.. is the way to go. I.e. javascript (preferably fast subset of it) will be produced by proper tools and you'd never have to look at it again. Fragmentation is only natural.

So these languages exist precisely because life is short. Are they the perfect/stable solution? Probably not. But it's the right way to go.

Re: Angular 2 Beta released

#240

Earlier quoted context omitted.

> ReactJS has slaughtered the front-end market share (in a good way) and completely taken develo Do you have a citation for that? I still see tons of user land projects using angular 1.

I just checked Datanyze which crawls the Alexa 1m and more to see which services & libraries websites are using. They've detected 234,003 sites using Angular and 2,069 using React.

I'd love to see those numbers for Ember, Polymer, Backbone and Aurelia.
Post reply on HN