"Learn Angular 2 fundamentals while rebuilding a real app." Wouldn't it be great to turn business requirements into code training documentation and crowdsource the development of things?
I laughed. Then I started to think.
Angular 2 Fundamentals Course
71–80 of 120 posts
Re: Angular 2 Fundamentals Course
#72AngularClass knows what they're doing. This course is gonna be legit.
Re: Angular 2 Fundamentals Course
#73Re: Angular 2 Fundamentals Course
#74Earlier 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.
create-react-app is their official attempt at a happy medium that basically does bare minimum basic configuration to start building React apps with the latest tools: https://facebook.github.io/react/blog/2016/07/22/create-apps...
HN Discussion link: https://news.ycombinator.com/item?id=12144371
Re: Angular 2 Fundamentals Course
#75Earlier quoted context omitted.
Angular is a more full featured than React by itself. To get React to equivalent features you have to add on (and learn) several other things (Redux, WebPack, etc, etc). As a bonus, there are lots of different conflicting flavors-of-the-week for things to use with React to build out your stack, so whichever you pick to go with React might not be cool next week.
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.
Re: Angular 2 Fundamentals Course
#76Interesting 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.
Re: Angular 2 Fundamentals Course
#77Angular 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 make scope legibility better? (Assuming we still have the same scoping concept)
2) Do the abstractions leak? Angular 1.x abstractions leak like hell. Even if you're not concerned about performance, you have to be careful about snakes breaking out from under them and providing unexpected behavior, if you are concerned about performance you'd better have a detailed understanding about how the digest cycle works and it's utterly laughable that people thought this was a reasonable tradeoff for two-way data binding.
3) Is the tooling better? Some versions of Batarang were just straight up broken.
Given that Angular 2 isn't really stable yet, I have my doubts these questions can have clear answers, but happy to receive surprise illumination.
(At the moment, though, still avoiding applying to work at anywhere that lists Angular as a requirement. There's going to be technical debt and likely enough an ongoing technical decision making deficit at anywhere that does.)
Re: Angular 2 Fundamentals Course
#78Earlier 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?
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.
Re: Angular 2 Fundamentals Course
#79Earlier quoted context omitted.
Angular for job opportunities, react for more pleasant and forward looking web development practices.
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.
Re: Angular 2 Fundamentals Course
#80Earlier 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.
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.