Live data from Hacker News

Angular 2 Final Released

angular.io

131–140 of 452 posts

Re: Angular 2 Final Released

#131
post #41

Earlier quoted context omitted.

Yeah - we consult with an angular + Java group (for angular only) --- I can't understand half of what they are talking about when they talk about Enterprise level Java web projects. Java for Hadoop, Spark etc I work with daily.

Enterprise projects tend to have way more convoluted business logic and interfaces than consumer stuff -- it doesn't get nearly the love it deserves imho. Those developers, DBAs, devops folks, and sysadmins suffer sooooo much every day.

Java EE is basically an excuse for consultants to overcharge for overengineering solutions to problems that were already complex to begin with.

Source: Did some Java EE consulting here and there.

Re: Angular 2 Final Released

#132
Nice, played around with Angular 1 and 2 - Angular2 with its use of components reminded me of making front-ends with the Apache Wicket framework some time ago.

This might appeal to java full stack/backend engineers that need to once in while show case a nice and shiny GUI. It my experience, the combo of Angular with Bootstrap/Font awesome works just fine for that.

Very positive to have static typing through TypeScript as well. But also here I am quite biased for I never liked the concept that 'everything is just a var' ;)

Re: Angular 2 Final Released

#133
post #129

Earlier quoted context omitted.

I recently started a new front-end-heavy project and ended up just using Angular 1 instead of React. The decider for me was the amount of tooling that React needs you to have in place just to get up and running. React expects you to do your development on some flavor of Unix, and really doesn't have a sane plan for Windows, so you lose VS.NET and its huge productivity gains. And it needs tools upon tools upon tools t…

And it needs tools upon tools upon tools to set up, whateverify, transpile and pack the files you write into something that can display in a browser. I think this was true six months ago but now there is create-react-app. You might want to try it out - you won't need to whateverify your code, you just need that one tool. Also it works on Windows. https://github.com/facebookincubator/create-react-app I want to edit so…

npm install -g create-react-app

The fun thing watching the new world of Javascript is that overtooling is so built in to everything that nobody even realizes how many tools they're using. You can't even install this thing until you have the standard pile of javascript tooling in place. And it never occurred to them to even mention how to get said pile set up.

Once set up, this still uses all the same stuff. It just removes a few steps to produce the Big Red Button you press to run it all.

Re: Angular 2 Final Released

#134

Earlier quoted context omitted.

That's Conway's law for you. All three frameworks were built by meglogcorp, and they all feel exactly the same. It is funny that after the Rails driven success web devs had moving away from J2EE they are falling right back into the same traps - ultra complex bloated frameworks built on a terrible language.

Javascript is definitely a terrible language, but it is the only language for the web unless you consider languages that transpile to javascript. Are you suggesting not using a javascript framework, using a transpiled language instead of javascript, not writing any front end code at all, or doing something ridiculous like turbolinks?

What is wrong with turbo links???

Re: Angular 2 Final Released

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

Re: Angular 2 Final Released

#136
post #21

As someone who uses Angular 1 currently but would pick React for their next project, I'd love to see a list of reasons why I should use Angular 2 over React. If nothing else, Angular just stranded all their developers, while React has a huge head start on mindshare/plugins/tutorials/etc.

I like the opinionated approach of NG2 over the flexibility of React because it takes a lot of decisions off of me that i am not too interested in when building a new project. I am a full stack developer leaning more towards backend in recent years and i found setting up and finding out about best practices and "what to use" for React a bit tedious, also it changes so much. The last Flux framework i used was alt.js w…

Regarding the "Flux" frameworks, that's not a problem anymore - basically Redux (which improves on some of Flux's faults) has won. Its developer was hired by Facebook, so I guess it's kind of officially sanctioned now.

Re: Angular 2 Final Released

#137
post #26

Earlier quoted context omitted.

All three frameworks are excellent at helping us build ambitious front-end applications; you simply can't go _wrong_ by picking one over the other. If a particular framework's trade-offs don't for any part of the app (performance for example), you can always write just that part in a different way (manual DOM manipulation). But to contrast all three, I'll pick the area I'm most interested in - templating. The purpose…

Have you seen yesterday's post about Cx? I'm curious what you would have to say about it. Cx adds declarative data-binding, controllers and router on top of React and includes composable widgets and charts. It looks for a sweet spot between development speed and freedom to do whatever you want. Here's a quick example https://cx.codaxy.com/fiddle/?f=42vDn4I1 . Disclaimer: I'm the author of Cx.

First impressions: looks like Angular's two-way data binding (using custom attributes in the template itself) added to React. This should make it possible to write complex views quite fast - without writing much code, and yet we don't lose out on the component-based composition of Javascript code offered by React.

What I need time to get around to is the concept of controllers and how it works when we want to compose things together. For example, how to write a multi-select widget that exposes a clear API to the rest of the world (onChange), and encapsulates all other details within. Cx does deserve a deeper look, and I'll definitely give it a whirl some time. Also kudos for the extensive documentation you've so far written!

Re: Angular 2 Final Released

#138
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 and Angular 2.0 seems to have a lot concepts in common and I don't fully understand why they are going to compete, given they come from the same source. But for me it seems that Polymer nowhere picked up as Angular.

When it comes to performance it is great in Chrome. In other browsers not so. I hope v2 will be much better once they can get rid of the compatibility layer for other ever-green browsers.

Re: Angular 2 Final Released

#139
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.

Does anybody actually use Polymer? Frontend jobs are mostly either Angular or React related.
Post reply on HN