Live data from Hacker News

Angular 9.0

blog.angular.io

271–280 of 308 posts

Re: Angular 9.0

#271

Earlier quoted context omitted.

> Also if you are not familiar with RxJS before learning Angular then that is a second learning curve that you need to know too and it is a challenge. You are not the only one mentioning this here. Do you believe it's wise to start with learning RxJS before you even approach Angular if you are a VanillaJS/JQuery "dinosaur" looking forward to learn Angular?

RxJS is very cool and well designed, and stands on its own. Worth learning about even if you don't use Angular, but definitely if you do! The basics are easy to understand, but there are a whole lot of deep profound operators that it will take a long time to master, although you don't need them all at first. https://rxjs-dev.firebaseapp.com/api Reading the guide and pondering the following table helped me understand…

RxJS is not made for normal people. You have to be some brainy CS wizard to get it. If you're used to more traditional "linear" coding (no matter if functional or procedural), RxJS is a brainfuck with its time/stream component. I hated it when I tried to use it.

Re: Angular 9.0

#272

Earlier quoted context omitted.

This is the biggest “meme” about angular and it’s so unbelievable wrong. It shows that you haven’t used the framework if you think all the choices are made for you. Instead of spending all my time analyzing different open source packages for every single thing you do, you just have access to a first class supported solution. IMO, lots of the react ecosystem is built on engineers trying to show off. They get fancy com…

Unlike most people, I've written both Angular and React extensively: I've shipped both Angular and React web applications in enterprise settings. I wouldn't characterize my time in React spent "all day comparing open source packages" -- if that's what you think web application development on React looks like on a day-to-day basis, you haven't done much on it. To be clear, I do not intend to speak negatively about Ang…

I was mostly responding to this line “ It's hard to take pride and ownership in your work when 90% of everything has been decided for you,” Which in my kind is just a weird thing to say and seemed to imply a general statement.

A lot of comments state angular is inflexible and opinionated, but come from people who haven’t used the framework. They think your forced to do a lot of things where angular gives you choice.

I haven’t done much react development, but my significant other has and multiple members of my team have as well, and I’ve heard them discuss how when you need to find a package to pull in it’s a decision that involves searching and weighing the pros and cons much more then for angular.

I don’t hate react at all and totally understand its pros and how I think it’s a net positive on the web development landscape. It’s more that this site is extremely react focused and biased, and the US dev community is also that way. So angular gets called out as being something stupid to use that’s cumbersome, slow and big, but that’s just simply not the case. Example of angular app being smaller and faster then comparable react: https://www.freecodecamp.org/news/a-real-world-comparison-of.... I know these comparisons are silly so I’m not putting much thought into it, just one anecdote.

Both are great libraries/frameworks with great ecosystem of developers, we all need to stop flaming each other and see the progress each community is making. It’s not a winner take all type deal, there’s plenty of room for both.

Re: Angular 9.0

#273

Just want to say that all the Angular React comparisons are dumb. It is comparing apples to oranges. Angular is a bigger framework for developing more complex stuff. Therefore of course there is a steeper learning curve. Here are comments like "react is so much more easier because it is just functions". Why not just using vanilla js because you have nothing to learn then? Or just use binary code? It is just 0 and 1.

I think the problem then is people not respecting YAGNI. The vast majority of web apps should be built using React ant only the true monoliths should be built using Angular.

Also it's worth nothing that React and Vue scale. They work as well for small, scrappy projects as they do for large enterprise ones. I wouldn't say the same for Angular.

Re: Angular 9.0

#274

Earlier quoted context omitted.

Meanwhile, the web apps I wrote in 2014 in react still work flawlessly. Join us, you’ll enjoy the ride!

Are you suggesting that angular apps written in 2014 would not still be working?

I don't think so, the point is that Angular breaks user code often, whereas React rarely does.

An Angular 2+ app built in 2016 (when Angular 2 came out) wouldn't build anymore.

An Angular 1 app didn't even need a build step, so that would probably still work fine.

Re: Angular 9.0

#275
post #271

Earlier quoted context omitted.

RxJS is very cool and well designed, and stands on its own. Worth learning about even if you don't use Angular, but definitely if you do! The basics are easy to understand, but there are a whole lot of deep profound operators that it will take a long time to master, although you don't need them all at first. https://rxjs-dev.firebaseapp.com/api Reading the guide and pondering the following table helped me understand…

RxJS is not made for normal people. You have to be some brainy CS wizard to get it. If you're used to more traditional "linear" coding (no matter if functional or procedural), RxJS is a brainfuck with its time/stream component. I hated it when I tried to use it.

That's what I meant by "very cool"! ;)

Re: Angular 9.0

#276

Earlier quoted context omitted.

Well obviously they'll be CR'd. If you stick to prop drilling and functional code there's far less you can do abjectly wrong.

Except wire up routing in a strange way, or pick a library for form validation or form framework, or come up with odd ways of structuring tests, picking a strange approach for animations, etc. This is the cost when app architecture gets delegated to your developers over a high quality central solution, the quality is as good as your developers.

Those are the parts where you put a senior in charge. Hell I can't even do that in React, and have in the past literally hired a contractor to set that up for me.

Re: Angular 9.0

#277

Earlier quoted context omitted.

Don't interpret too much into it :) When I signed up to HN and had to choose a nick, I sat in my living room looking at a Tanne (a fir in German) outside, and chose Tannhäuser (literally, a man who lives in the woods) in a hurry. If anything, it's a (quite arrogant towards the HN crowd) reference to Richard Wagner's opera/character rather than Blade Runner. Hopefully you're not disappointed :)

Tannhäuser Gate is only the most enigmatic reference of the best scene of the best movie in the universe, and I never heard of any mind altering substance called Tannhae that you were admitting to use (are you a Can-D user or a Chew-Z user? [1]), so I assumed it must be a Blade Runner reference! But now I understand it's a direct reference to what Roy Batty may have been indirectly and allegorically referencing, whic…

Tannhäuser is also a opera by Richard Wagner (which refers to some older folk tale): This is probably what Philip K. Dick inspired to use that name.

Re: Angular 9.0

#279
post #88

The only thing I like about Angular is the dependency injection of services. Having "services" managed for you and just picking and choosing what you want is pretty nice. What I don't like is the verbosity and boilerplate... here's 2 examples: - Routing boilerplate is convoluted and time consuming. I think Nuxt.js has a much nicer implementation of SPA routing, where the filesystem is used to map the routes. - Angula…

Another benefit in my mind is that Angular is "batteries included" - you get everything you need in a single library, e.g. routing is a big one. From what I understand of React, you need to pick and chose the libraries (and versions of those libraries!) to use for your app, and then keep the versions of all the different libraries up-to-date and in sync with each other. Sounds like a maintenance nightmare.

> then keep the versions of all the different libraries up-to-date and in sync with each other

Not really, since by design React doesn't care. You can use a years-old version of React Router without any problems.

Re: Angular 9.0

#280

Earlier quoted context omitted.

I would assume angular outputs minified code, but not gzipped. That being said, 973kb seems like large-sized rather than mid-sized to me.

Sounds like you've never actually worked in a large application to me. Not to gatekeep or anything but large web applications will be in the order of millions if not tens of millions of LOC.

I'm not sure where LoC came from, since we're talking about minified file size.
Post reply on HN