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

Angular v8.0

github.com

Post reply on HN
Print view View original

141–150 of 210 posts

Re: Angular v8.0

#141

Post by Gene_Parmesan »

holografix wrote: post #16

I was recently at a Microsoft heavy tech conference and spoke to at least 50 .Net developers. Anyone who also did front end did so in Angular. I was surprised at how popular it is!

MS Build? I was there too! Great conference.

This fact about Angular doesn't surprise me. It uses TypeScript which is a Microsoft joint, and the architecture feels rather similar to the MS standard MVVM. Two way data binding in the UI, a "code-behind" in the component. And TypeScript lends a sort-of C# flavor to the framework. It takes some "enterprise" and puts it in the front-end, which can help make the transition from ASP.NET MVC or whatever to Angular a bit easier (especially as compared to something like React).

If you're already doing .NET stuff, and you need enterprise-grade front ends, Angular seems like the natural choice still. One thing about Microsoft shops (of which my employer is one) is they tend to use Microsoft for everything, and despite Angular not actually being Microsoft, TypeScript makes it close enough. I'll be curious to see if the eventual production-ready release of client-side Blazor changes the dynamic at all.

Re: Angular v8.0

#142

Post by Yuioup »

holografix wrote: post #16

I was recently at a Microsoft heavy tech conference and spoke to at least 50 .Net developers. Anyone who also did front end did so in Angular. I was surprised at how popular it is!

Meanwhile Microsoft is porting all of Office to React and have released React Native for Windows.

Re: Angular v8.0

#143

Post by sa46 »

visarga wrote: post #138

Angular is too abstract / has a steep learning curve. You need to learn too many design patterns at once (factory, provider, service, singleton, pipes, directives, observable, component, container, dependency injection). Trying something simple is trivial, but trying something more complex is overly difficult.

I understand your point but to be fair, if we cherry pick all the terminology from React it also looks bad:

JSX, components, props, context, error boundaries, forwarding refs, fragments, higher-order components, container.

Once you add in concepts from the other libraries commonly used with React like mobx or redux I think the comparison isn't as clearcut.

Re: Angular v8.0

#145

Post by ng12 »

stupidcar wrote: post #39
sheeshkebab wrote: post #6

Angular feels like frontend framework built by backend java Spring developers, that hate frontend development.

This feels like an argument made by somebody who has never built a serious project in either, and has instead formed an opinion based on quick glance at the respective syntaxes. To me, Angular is what HTML and the DOM would look like if they had been designed from the beginning for application development: - Custom elements backed by controller classes. - Data-binding and event-binding syntax baked into HTML - Compon…

> React seems far more like a project created by people who dislike front-end development

This is a really poor characterization. I started using React because I love front-end and it was exactly what I wanted front-end development to be. It solved every one of the pain-points I was experiencing with a jQuery/Backbone/Handlebars stack.

Re: Angular v8.0

#146

Post by TheSpiciestDev »

ripley12 wrote: post #133
pure wrote: post #72

Angular is really a great framework. I think a lot of people complaining about Angular haven't actually built an app in Angular 4+. I also wish the Angular team had just called Angular 2 something else, since the 1 -> 2 transition frustrated a lot of people who jumped ship and never looked back. I also understand that people just have different preferences, which is fine, too. Out of the box, you get: routing with la…

> a component-based approach to UI development This is actually something that bothers me a lot about Angular. Yes, you can extract components, but the process of doing so is a lot more... heavyweight than in React. In React, I can trivially extract any piece of UI into a stateless functional component in the same file (and later on I can move it to another file for wider reuse if needed). It's just like extracting a…

> heavyweight

I can agree with you there if by heavyweight you're referring to it's explicit definitions.

However, have you tried a "SharedModule"? You can throw any number of tiny components into however many shared modules (one shared module for your small-medium sized application vs n-number of lazily loaded shared modules for your large+ applications.)

I myself enjoy wrapping even helper components in modules because I then know exactly what a component needs and it's scope of dependencies.

Re: Angular v8.0

#147

Post by ng12 »

pier25 wrote: post #104
switz wrote: post #96

Earlier quoted context omitted.

I'm not a fan of Angular, but how many times are we going to have this conversation. At this point, this is a completely off-topic comment that has no place in this thread. I'm getting javascript fatigue fatigue. > With some exceptions, there is really no benefit This is just a contradictory sentence of hyperbole. Who cares if there are plenty of use-cases to not write a SPA. There are also plenty of use-cases for it…

> There are also plenty of use-cases for it, and many benefits. I obviously disagree, but please elaborate.

I've spend the last decade building highly dynamic data visualization applications. Building them server-side would be a huge pain.

Re: Angular v8.0

#148

Post by ng12 »

pure wrote: post #72

Angular is really a great framework. I think a lot of people complaining about Angular haven't actually built an app in Angular 4+. I also wish the Angular team had just called Angular 2 something else, since the 1 -> 2 transition frustrated a lot of people who jumped ship and never looked back. I also understand that people just have different preferences, which is fine, too. Out of the box, you get: routing with la…

> embracing TypeScript

There's been a huge React/TypeScript community since day one, even before Angular2 was released with TypeScript. The only difference is it's optional with React.

> creating injectable shared state (or you can call it Context)

Or Flux/Redux?

Re: Angular v8.0

#149

Post by ng12 »

pure wrote: post #108
azangru wrote: post #99

Earlier quoted context omitted.

> It's also interesting to see the React community move towards some of the things that Angular has been doing for years: embracing TypeScript, extracting business logic to services (or you can call them Hooks), creating injectable shared state (or you can call it Context). Huh? Hooks are just a way to use component lifecycle in absence of classes (note how React is pushing towards having components as functions as o…

Definitely correct me if I'm wrong, but I also thought hooks were for factoring out common logic and sharing it among functional components. I see lots of "hooks" libraries floating around. For Context, like you said, it existed before, but everyone was told not to use it. After the new API came out, people started suggesting ditching Redux for Context, and I know a lot of people did that. Using Context in that way i…

Hooks are used for abstracting component state logic. React is just as agnostic concerning how you implement your business logic as ever.

Re: Angular v8.0

#150

Post by equasar »

dmitriid wrote: post #82

In my opinion Angular's story is a story of how people invent problems and then valiantly tackle them. - We want to re-write the whole thing from scratch. In TypeScript. - And let's use Google's Closure Compiler for JavaScript. Even though it doesn't support TypeScript, modules, or anything, really from non-Google Javascript world (at the time) - Oh. Then... Let's create a TypeScript to Closure Translator even though…

What's the point you are trying to achieve with that negativity?

Writing non existing tooling around some tools is almost positive as they can pave the journey to other and better tooling.

Also, I doubt you are paying a cent to those developers to justify your complaints about it.

Post reply on HN