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

101–110 of 120 posts

Re: Angular 2 Fundamentals Course

#101

Post by hugozap »

RussianCow wrote: post #35
hugozap wrote: post #27

Earlier quoted context omitted.

This is not accurate. You don't need to learn Redux or WebPack to use React. With Angular you also need a build process so you can use gulp or WebPack. Maybe there's a pre baked process but you still need to know some build tool. Because React doesn't care about how you manage your state, you can use Redux or other solutions. Not because they are cool , but because it fits your needs.

I think the overall point that you have to fill in the gaps yourself still stands, though. Angular just comes with way more features than React does, so if you want an equivalent experience, you have to use third-party libraries with React, which increases the amount of things you have to learn. Not that this is entirely a bad thing, but you can't really compare bare React to bare Angular and say they're equivalent.

Not sure if your point about the amount of things to learn is true. I prefer learning small utilities and compose them. The cognitive load is much more smaller (for me) than having to learn a giant monolith. I guess it's a matter of preference.

Re: Angular 2 Fundamentals Course

#102

Post by hugozap »

komali2 wrote: post #75
hugozap wrote: post #27

Earlier quoted context omitted.

This is not accurate. You don't need to learn Redux or WebPack to use React. With Angular you also need a build process so you can use gulp or WebPack. Maybe there's a pre baked process but you still need to know some build tool. Because React doesn't care about how you manage your state, you can use Redux or other solutions. Not because they are cool , but because it fits your needs.

Why does Angular need a build process? You can just point script tags at a fat angular.js file, or a CDN, and go on your merry way. Sure it's not like the 10x dev way to do it, but I do it for simple apps all the time.

Same thing with React.

Re: Angular 2 Fundamentals Course

#103

Post by hugozap »

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.

Here's how to have a great starting point in less than 10 seconds:

npm install -g create-react-app && create-react-app hello-world

Re: Angular 2 Fundamentals Course

#104

Post by RussianCow »

hugozap wrote: post #101
RussianCow wrote: post #35

Earlier quoted context omitted.

I think the overall point that you have to fill in the gaps yourself still stands, though. Angular just comes with way more features than React does, so if you want an equivalent experience, you have to use third-party libraries with React, which increases the amount of things you have to learn. Not that this is entirely a bad thing, but you can't really compare bare React to bare Angular and say they're equivalent.

Not sure if your point about the amount of things to learn is true. I prefer learning small utilities and compose them. The cognitive load is much more smaller (for me) than having to learn a giant monolith. I guess it's a matter of preference.

There are tradeoffs. The advantage of learning smaller libraries is that you only have to learn what you need. However, the advantage of a monolithic framework is that everything is integrated so nicely that, once you learn the framework, everything kind of "just works", and you don't have to spend time figuring out how to glue everything together. I personally prefer the former approach, but I also understand the appeal of a framework like Angular or Ember that makes all the high-level decisions for you.

Re: Angular 2 Fundamentals Course

#105

Post by RussianCow »

pbreit wrote: post #78
talmand wrote: post #67

Earlier quoted context omitted.

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

I was just wondering what the author had in mind. But now that you ask, yes I think it does. Without a suggestion the opinion is pretty much worthless.

You really think we shouldn't criticize things if better alternatives don't currently exist? The fact that someone hasn't come up with a better approach doesn't imply that the status quo is the best possible solution.

Re: Angular 2 Fundamentals Course

#106

Post by Bahamut »

slmyers wrote: post #79
devuo wrote: post #31

Earlier quoted context omitted.

Er.. https://github.com/angular/angular-cli 1. Open terminal 2. > npm install -g angular-cli > ng new app > ng serve 4. Use the cli tool to generate components/pipes/services/etc., build, test, develop 5. Profit. Find a more blissful and joyful experience than this in react land?

Well, react did come up with this https://facebook.github.io/react/blog/2016/07/22/create-apps... recently. Also, one thing that is not enjoyable/straightforward with(angular-cli) is having to utilize System.js in order to include 3rd party libraries in your app.

That is about to change to webpack on next release - a big PR landed in the angular cli to switch it to webpack from broccoli.

Re: Angular 2 Fundamentals Course

#107

Post by ng12 »

msane wrote: post #97
ng12 wrote: post #80

Earlier quoted context omitted.

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.

Is that really an argument? that you don't need to write it at the beginning ? you still have to do it...

My argument is that it's a net benefit. Composable architectures are not boilerplate. Remember that there was a time when almost all React apps where written with Flux -- this model is what allowed Redux gain traction.

Re: Angular 2 Fundamentals Course

#108

Post by rendezvouscp »

JustSomeNobody wrote: post #25
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…

> Longevity: we don't want to adopt yet another fad framework that we'll have to replace in 2017. No such thing. They're all pretty much fad frameworks.

JavaScriptMVC/DoneJS has a pretty long history: http://blog.bitovi.com/longevity-or-lack-thereof-in-javascri...

CanJS, the MVVM part of DoneJS, is currently coming up to its third major/breaking version. I think that’s a pretty good track record for us/Bitovi.

Re: Angular 2 Fundamentals Course

#109

Post by ausjke »

Hendrixer wrote: post #62
ausjke wrote: post #38

Earlier quoted context omitted.

sails + vuejs + postgresql will be my choice.

Take a look at Feathers js, so much better than Sails

Thanks. Saw this somewhere before but it's less known. The good part of feathers.js is that it does express4, and I think sails.js is still with express3.

Re: Angular 2 Fundamentals Course

#110

Post by Chyzwar »

ken47 wrote: post #41
taesu wrote: post #3

I heard angular is a framework and react is lib. angular 2 or react. Coming from nodejs, python, php, jquery experience which should I learn?

Having used and studied both React and Angular2, Angular2 can do certain things that React can't. Two features at the forefront of this difference are: 1) Dependency injection 2) Direct support for using observables and promises in templates However, I cannot think of anything major in the reverse direction. There is also the fact that it is designed to be used with Typescript from the get-go, which can be a plus if…

You can inject stuff using props. DI is not unknown concept in react, note that angular1.x do not have true dependency injection.

React decouple data and view. You can achieve similar behaviour but using flux/redux to publish/subscribe.

Post reply on HN