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

Version 6 of Angular Now Available

blog.angular.io

Post reply on HN
Print view View original

51–60 of 86 posts

Re: Version 6 of Angular Now Available

#51

Post by danellis »

megaman22 wrote: post #8

What is the backwards compatibility and support model for Angular? I just don't have time to chase after things that move this quickly, not and fulfill all my other responsibilities. I'm supporting a mature application that has a front-end started less than eighteen months ago with AngularJS. Maintenance and support on third-party components we use is already starting to dry up. Rewriting things every six months is n…

What is "this pace of change"? Which parts are changing too quickly for you?

> Rewriting things every six months is not reasonable for our team

I'm not sure why you think you'd need to rewrite things. Where are you getting your information?

Re: Version 6 of Angular Now Available

#52

Post by pygy_ »

PunchTornado wrote: post #36
smuemd wrote: post #34

Earlier quoted context omitted.

Check out this pattern http://meiosis.js.org Works great along w react

your comment proves his point exactly.

The Meiosis pattern cristalizes the essential complexity of centralized state management (flux/redux), with no boiler plate, and little to no extra library code...

How does that prove his point?

Re: Version 6 of Angular Now Available

#53

Post by lucidone »

dbbk wrote: post #41
bob1029 wrote: post #37

Sigh. Yet more confirmation that my team has made the correct choice in switching to a mostly vanilla JS development stack (we still use RiotJS for one-way template binding). I was there for the beginning of Angular and it got me hooked on single page applications, but what I am seeing now is the antithesis of productivity. No one building a website for a business should be using this stuff, unless they drank so much…

> Focus on what you want to build, not the tools you use to build it. This is an interesting comment to me because, by essentially building your own framework, that onus is now completely on you. If you want to implement code splitting or tree shaking or whatever, you have to figure that out for yourself. That's time taken away from building product features. Whereas other frameworks can offer this out of the box bec…

In addition to your in addition, the experience gained learning and using a proprietary framework isn't "resume-able" in the same way putting React or Angular is. That could mean a significant difference in salary, and it's also why I'm shopping around for new work right now. Like it or not, it matters.

Re: Version 6 of Angular Now Available

#54

Post by Bizarro »

stupidcar wrote: post #26
antonkm wrote: post #13

Was a firm believer in Angular when it was version 2, made the switch to React before Angular version 4. Best choice I've done for productivity.

I'd offer the opposite perspective: I started a recent app in React, and I wish I'd stuck with Angular. The core of the React render model is beautiful. It's far quicker to start writing and using a new component in React than in Angular, and the functional nature of React components feels good and highly productive. At first. But the problem is, around that beautiful core, the React community has built a mass of lib…

But the problem is, around that beautiful core, the React community has built a mass of libraries, meta-frameworks, techniques and practices that are decidedly less beautiful.

This is exactly what I have found working with React for the past couple years. Once you factor in the React ecosystem, things get messy/ugly and decidedly unproductive.

I'll most likely be moving on to Vuejs.

Re: Version 6 of Angular Now Available

#55

Post by 11235813213455 »

stupidcar wrote: post #26
antonkm wrote: post #13

Was a firm believer in Angular when it was version 2, made the switch to React before Angular version 4. Best choice I've done for productivity.

I'd offer the opposite perspective: I started a recent app in React, and I wish I'd stuck with Angular. The core of the React render model is beautiful. It's far quicker to start writing and using a new component in React than in Angular, and the functional nature of React components feels good and highly productive. At first. But the problem is, around that beautiful core, the React community has built a mass of lib…

There's a rich ecosystem, wide choice in React, definitely a benefit. Singletons? Services? that's just modules in React, in all simplicity

- styles scoping: CSSinJS (many libs exist, I like react-jss)

- forms: they are just simple to handle using state

Re: Version 6 of Angular Now Available

#56

Post by 11235813213455 »

pygy_ wrote: post #52
PunchTornado wrote: post #36

Earlier quoted context omitted.

your comment proves his point exactly.

The Meiosis pattern cristalizes the essential complexity of centralized state management (flux/redux), with no boiler plate, and little to no extra library code... How does that prove his point?

It seems they don't want to have to choose a user-land library, but expect everything to be provided by the framework

Re: Version 6 of Angular Now Available

#57

Post by ufmace »

I came in here to try and get a feel for what front-end developers these days think of the new Angular vs React. I don't have any stake in this game, since I'm not currently working on anything front-end. I'm pleasantly surprised to see that, instead of the half-expected Angular bash-fest, there seems to be a number of people praising Angular over the React ecosystem.

When I last did front-end, I was using Angular 1.x, and despite some warts, I did like the overall architecture of it, and how it provided all of the important components for you and gave you an overall app organization. It felt like quite a change to try and build an app with React and experience the world of having to pick and glue together a bunch of components with ever-evolving build systems. This makes me more interested in trying to build something in the new Angular.

Re: Version 6 of Angular Now Available

#58

Post by garraeth »

dbbk wrote: post #41
bob1029 wrote: post #37

Sigh. Yet more confirmation that my team has made the correct choice in switching to a mostly vanilla JS development stack (we still use RiotJS for one-way template binding). I was there for the beginning of Angular and it got me hooked on single page applications, but what I am seeing now is the antithesis of productivity. No one building a website for a business should be using this stuff, unless they drank so much…

> Focus on what you want to build, not the tools you use to build it. This is an interesting comment to me because, by essentially building your own framework, that onus is now completely on you. If you want to implement code splitting or tree shaking or whatever, you have to figure that out for yourself. That's time taken away from building product features. Whereas other frameworks can offer this out of the box bec…

I also did what the parent did. I'm using mine on several enterprise projects. And I'd also argue that devs spend //more// time implementing updates due to framework churn than for maintaining their own framework. After mine was "done", it was done. There is no code churn, all the features are in, tight code, etc,...so now I only spend time creating/expanding my products.

The discussion today about React v6 is exactly what we get to dismiss (as well as any along the way from v2 - v5) since our framework work is done.

Granted, you're absolutely correct when you say new devs have to learn all the proprietary ways of your framework. But even then, since the framework is such a small percent of the overall knowledge dump for a new hire, I'd argue, that it's not much of a concern. It'll take months to learn the systems, and maybe a week(?) to learn the framework.

And to be fully honest, I haven't learned React/Angular/Vue (did learn KnockoutJS back in the day), and if I need to hunt for a job, then yes I'm behind the curve.

Re: Version 6 of Angular Now Available

#59

Post by zygimantasdev »

InTheArena wrote: post #46

This upgrade looks absolutely fantastic. The Elements piece in particular looks amazing, and has the potential to be a real game changer for shops that have a diverse set of applications that they use, and need large scale re-use of components. At the mid-size corporation that I work at, we just standardized all Javascript development on Angular from a mismash of a ton of technologies. Angular seems very well suited…

>At the mid-size corporation that I work at, we just standardized all Javascript development on Angular from a mismash of a ton of technologies. Angular seems very well suited for this role.

In my experience centralisation and fixation on specific technology leads to stagnation quickly. IMO you should allow teams to choose their own tools. How else will you improve?

Re: Version 6 of Angular Now Available

#60

Post by aeriklawson »

megaman22 wrote: post #38
davidjnelson wrote: post #12

Earlier quoted context omitted.

Angular 2 came out in 2016. Why use angular 1 in 2017?

It was 2016 when we started this front-end rewrite, away from a mess of jQuery and Razor view spaghetti. Angular 2 was brand new, without much support for third-party components we used, and AngularJS looked like the mature option. Probably should have bet the other horse, but c'est la vie.

We're in the middle of upgrading from Angular 1 to Angular 5 (probably now 6) - it's not that hard and I'd recommend doing it.
Post reply on HN