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

Why Learning Angular 2 Was Excruciating

hackernoon.com

Post reply on HN
Print view View original

21–30 of 226 posts

Re: Why Learning Angular 2 Was Excruciating

#21

Post by georgefrick »

I'm going to cry foul. Lines like "has a umd now. whatever a umd is.... " Stack Overflow copy pasta developers. If you're an associate level developer; the project should be setup for you. If you are above that, you should understand some of the internals and build tools to the point where you are comfortable wiring them.

Also, this has already been discussed; we get it. RC5/6/7 sucked for everyone (well, except those of us who were eagerly waiting for forms 2.0). Must we do daily "omg rc5 was painful" posts?

The change to ngModule took 15 minutes btw, more if you count all the code you got to remove from other components.

Re: Why Learning Angular 2 Was Excruciating

#22

Post by kelvin0 »

lemmsjid wrote: post #6

I've found that learning new technologies from first principles is better than starting with frameworks, unless you're willing to put up with a lot of ambiguity. For example with Javascript I'd start with basic manipulations (e.g. get to know the prototype model, the debuggers, the DOM, etc.), work up to a make-life-easier library like JQuery, then try a framework. It may depend on your learning style, of course.

This is exactly the path I've taken. I figured if I start out with right off the bat, and not understand the foundation, I'd be screwed in the long run. My reasoning is that once I grasp JS's quirks/ins/outs (I'm looking at you 'this'), well I'd be ready to see the light and better choose a framework. So far, I think ReactJS nailed it, but keep in mind I am fairly new to Web Dev (coming from PC/Console/C++ world) so YMMV. Also, I would like to thank the good folks at Twitter for Bootstrap, I don't know how my frontend would look like without it!

Re: Why Learning Angular 2 Was Excruciating

#23

Post by ausjke »

I have been wondering why a one-person project like vue.js seems to be saner than the big guns such as angularjs and even react-ecosystem?

I have been trying all three recently back and forth and now leaning back to vuejs while waiting for its 2.0 release.

Re: Why Learning Angular 2 Was Excruciating

#24

Post by nanny »

mkozlows wrote: post #19
robin_reala wrote: post #13

Sorry, but sometimes I feel like the only sane person in the madhouse. It’s a blog! It’s literally just an index page and some display pages! Why could that possibly need 100s Kb of JS to run it? Of course you’re going to have trouble, you’ve picked a JCB to do a screwdriver’s job.

The point is to use the blog as an example to learn the tech, typically. Picking a familiar, not-too-big problem to solve is a good way to understand how new tech works.

A to-do list would've been a better choice. It's the classic choice for working with SPA frameworks. I thought the same thing as your parent's commenter when I read the word "blog".

Re: Why Learning Angular 2 Was Excruciating

#25

Post by WalterSear »

plexicle wrote: post #17

Your first foray into web development and you picked a large, unfinished (it wasn't final) framework to learn with? Then you are complaining that there were breaking changes you had to deal with? I get your beef with the ecosystem, but this is a very unfair knock on Angular 2. Angular 2 was not the problem here at all. Am I missing something obvious?

Unfinished? How about never finished.

>Angular 2 is going to have breaking changes only every 6 months from now on. So the next one would be around February with Angular 3. Yes exactly, they’re also finally switching to semantic versioning which is a huge win in my opinion.

IMHO, breaking changes every six months is the recipe for an shitshow of an ecosystem.

http://juristr.com/blog/2016/09/ng2-released/

Re: Why Learning Angular 2 Was Excruciating

#26

Post by mrits »

andrewclunn wrote: post #16

The best thing about Angular 2 is that Angular 1 is now stable. I say this as a web developer currently coding apps in Angular 1 for production. This is gonna be a python 3 moment all over again.

I liked Angular 1. It only took a few days to get the hang of it. If Angular 2 or React are really the future of front end then I'm not going to go back. I'm happy doing some backend dev in Go right now. After I finally figured out all the parts of modern front end development I was already sick of it all.

Re: Why Learning Angular 2 Was Excruciating

#27

Post by copperx »

lemmsjid wrote: post #6

I've found that learning new technologies from first principles is better than starting with frameworks, unless you're willing to put up with a lot of ambiguity. For example with Javascript I'd start with basic manipulations (e.g. get to know the prototype model, the debuggers, the DOM, etc.), work up to a make-life-easier library like JQuery, then try a framework. It may depend on your learning style, of course.

I love that approach myself; methodically learning the building blocks is the only way to get solid understanding.

However, that's very hard to do if your time is limited and you need to add a feature to an existing app or get something working ASAP. Stumbling through the API is the norm if you're doing something fast.

It reminds me of when I was trying to get Photoshop to do something before really sitting down and learning the principles. So much wasted time.

In the end, it's always worth it to learn the basics first, but your team will not always agree.

Re: Why Learning Angular 2 Was Excruciating

#28

Post by nichochar »

stevebmark wrote: post #9

To me this is still why React feels like the first front end UI framework that got it "right." It stays close to vanilla Javascript. There's a tiny API surface area to learn, and the rest is vanilla Javascript classes and functions. Angular's API, and apparently Angular 2.0's API, is still large, and strays far from vanilla Javascript

"tiny" nope.

Re: Why Learning Angular 2 Was Excruciating

#29

Post by BurningFrog »

JohnnyConatus wrote: post #12

TL;DR - developer learns the meaning of Release Candidate or rather...does not: "To be fair, I have been using versions of the library that have thus far not been officially released. Maybe, you say, it’s my fault for trying to download and use a version of the library that is still in alpha/beta/release candidate and expecting it to work and be relatively easy to use. Perhaps you are right. But, considering the fact…

Yeah, but a Release Candidate should be very close to what is finally released.

Re: Why Learning Angular 2 Was Excruciating

#30

Post by mythz »

nichochar wrote: post #28
stevebmark wrote: post #9

To me this is still why React feels like the first front end UI framework that got it "right." It stays close to vanilla Javascript. There's a tiny API surface area to learn, and the rest is vanilla Javascript classes and functions. Angular's API, and apparently Angular 2.0's API, is still large, and strays far from vanilla Javascript

"tiny" nope.

The surface area you have to learn to be useful in React is tiny, much so compared with Angular2.
Post reply on HN