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

Angular 2 Fundamentals Course

courses.angularclass.com

Post reply on HN
Print view View original

81–90 of 120 posts

Re: Angular 2 Fundamentals Course

#81

Post by jogjayr »

_alexander_ wrote: post #45

I have only one question - when NG2 will be released? Because now it is not possible build real applications, many libraries are not stable, and still in beta or rc... Four month I'm trying to do real application and I must say that it was my big mistake when I decided use Ng2., with every new release I always have troubles with some dependencies or with new API, and there are no many stable components which I can us…

The uncertainty over this question is one of the reasons my team decided to build our new application in Angular 1.5 (though using TS and Webpack). It's less fancy, but mostly rock-solid and well-supported and understood.

We'll upgrade in a year or two once Angular 2 is well-understood and all the 3rd-party libraries have updated or deprecated into something else. The course looks like a good way to start understanding the differences.

Re: Angular 2 Fundamentals Course

#82

Post by ergo14 »

andys627 wrote: post #58
kimshibal wrote: post #18

Earlier quoted context omitted.

You don't need all that to create SPA app. it's bloated framework.

I wonder where the happy medium is. Setting up React/Redux/React-redux/react-router/react-redux-router/react-redux-router-thunk/webpack-hot-module-oh-my-god-what-am-i-doing takes forever.

A good way to start is to use polymer components :-)

Re: Angular 2 Fundamentals Course

#84

Post by sdegutis »

pbreit wrote: post #76
sdegutis wrote: post #6

Interesting coincidence. This week I've been tasked with looking into a JavaScript framework to replace our pure-Clojure stack at work. One of the front-end candidates is Angular. But we're considering cutting it from the race. The three main things we're looking for in a front-end framework: 1. Longevity: we don't want to adopt yet another fad framework that we'll have to replace in 2017. The current trend looks to…

If it's an internal app or if it otherwise doesn't need to be single-page-app, save yourself some brain cells and do something simple like Rails or Django. If JavaScript is absolutely required, stick with Sails/Mongo and skip the Ember/Angular SPA.

How does that help with a rich front-end? We're not looking to use JavaScript simply for the sake of using JavaScript. We want it in particular for a richer front-end. As far as I can tell, Sails isn't going to help with that any more than Rails does. That's why we're looking into Ember or Angular.

Re: Angular 2 Fundamentals Course

#85

Post by ergo14 »

_alexander_ wrote: post #60
Hendrixer wrote: post #15

Earlier quoted context omitted.

React is great, but it's just a lib. Angular 2 is in release candidate 4, and there are already ton of people using it. If you want a complete solution, I'd use Angular. TypeScript is awesome too. Angular comes with all the stuff you need, http, animations, routing, etc. I wouldn't cut it out just yet, seeing how it's on the horizon.

Could you share real projects(not todo-like applications) which use NG2?

Not NG2, but people for some weird reason try to ignore polymer here - and you have plenty of real-life appications starting from Google Music and Youtube to EA Battlefield1 and IBM and General Electric tools.

Re: Angular 2 Fundamentals Course

#86

Post by nightski »

ng12 wrote: post #80
andys627 wrote: post #58

Earlier quoted context omitted.

I wonder where the happy medium is. Setting up React/Redux/React-redux/react-router/react-redux-router/react-redux-router-thunk/webpack-hot-module-oh-my-god-what-am-i-doing takes forever.

You don't need all of that from scratch. You can just build React components, and when it comes time to add a store or a router the only thing you need to change are the glue components that bind things together. I think it works out nicely -- the dev process is as composable as the app itself.

Yea I've noticed that. The react community likes to focus on examples involving a sign up form with 3 fields where you "really don't need all of that". Except that is not what most of us SPA devs are building. We need most of that.

Re: Angular 2 Fundamentals Course

#87

Post by grkg8tr »

andys627 wrote: post #58
kimshibal wrote: post #18

Earlier quoted context omitted.

You don't need all that to create SPA app. it's bloated framework.

I wonder where the happy medium is. Setting up React/Redux/React-redux/react-router/react-redux-router/react-redux-router-thunk/webpack-hot-module-oh-my-god-what-am-i-doing takes forever.

Maybe something like http://aurelia.io ?

Re: Angular 2 Fundamentals Course

#88

Post by ghurtado »

talmand wrote: post #67
pbreit wrote: post #53

Earlier quoted context omitted.

Can you suggest an alternative?

If an alternative is not named, does that change the value of the opinion in any way?

Absolutely.

Here's an example: Human mortality sucks. However, since there is no alternative, complaining about it is an exercise in futility.

Re: Angular 2 Fundamentals Course

#90

Post by davidw »

wwweston wrote: post #77
gdi2290 wrote: post #13

Angular 2 is great, just look at all the features you get: WebWorker, Server-Side Rendering, mobile, progressive web application, Lazy loading support, Router, Material Components, Precompile your app. Tree-Shaking support, fast rendering, CLI, and TypeScript. The framework is backed by Google and Microsoft

The funny thing about lists of features is that they tend to create their own focus illusion. Here's what I want to know: 1) Are the various abstractions surrounding those things reasonably legible? Or are we back to talking about Factory Service Providers again or otherwise importing other bits of pattern hell idioms into a language where there's always been easier ways to get things done? 1a) What did they do to ma…

Angular is absolutely off in its own world of Factory Service Providers.

It all feels way too abstract and way too much "it's own thing" that is quite separate from the world of HTML and Javascript.

Post reply on HN