r/webdev • • Oct 18 '18

Angular 7.0.0 released

/r/Angular2/comments/9pbn4f/angular_700_released/
223 Upvotes

148 comments sorted by

96

u/thatgibbyguy Oct 19 '18

Why is everyone downvoting people who are questioning Angular's upgrade/versioning strategy?

  • React is currently at 16.5 and the inital "major" release of this version (16.0) was back in September of 2017. So it's been over a year at a single "major" version.

  • Vue 2.0 was released September of 2016 and is currently at 2.15.17. So it's been over two years since a "major" version.

  • Angular 6.0 was released in May of 2018 and is now at 7.0 in October of 2018. So.... five months before a new "major" version?

Considering the debacle of "ng 1" to Angular and that incompatibility, it should be fairly easy to understand why people are side eyeing the release strategy of the Angular team. I mean, generally "major" would mean something pretty majorly different, and that just doesn't seem to be the case here.

78

u/DerpsMcGeeOnDowns Oct 19 '18

It’s just proper semver man. Nothing crazy. If there’s a major breaking change, it’s bumped. Simple.

16

u/WHO_WANTS_DOGS Oct 19 '18

When they announced Angular 2, they said they would be doing a major release every 6 months. I wonder if they are consistently introducing breaking changes every release.

25

u/APimpNamedAPimpNamed Oct 19 '18

Fine for devs scary for managers

4

u/itsmoirob Oct 19 '18

Is there a breaking change in this?

12

u/E2Ehh Oct 19 '18

Yes, technically upgrading TypeScript to 3.1 is a breaking change. For most applications, it will not cause any side effects or require any fixing, but in some obscure cases it will need some fixes applied (e.g. as TypeScript has got better / more strict at detecting type anomalies). I upgraded our codebase today after the release was announced: >10k TS files, took me a couple of hours to read the release notes, upgrade packages and test everything out and get it deployed - hit no issues at all this time!

3

u/itsmoirob Oct 19 '18

10k files? I salute you. Good effort

1

u/E2Ehh Oct 19 '18

To be fair a lot of the files are pretty empty... small barrel files, ngmodules etc

-4

u/[deleted] Oct 19 '18

If you need major breaking change too often maybe there is something wrong.
Definitely a smell.

-5

u/Arkhenstone Oct 19 '18 edited Oct 20 '18

And it's what bad actually. Too much breaking changes, it makes your code legacy in less than a year. Edit : I've been downvoted and I just see that my comment is not that explanatory. It's not really bad as for bad for everyone. In a small where development is not the core activity, a language that introduce too many breaking change is not likely to be a good choice. Because the development will be slow, the app will have an outdated language by the times it goes out. For example, I've got an app which I started to develop a year ago. With Vue, it's still Vue 2, I can deploy the app with the latest version without even caring about about upgrading. It's not about skill or whatever, it's just about cost.

8

u/icouldnevertriforce Oct 19 '18

A breaking change can be a small change to a barely used API.

It's a "heads up check your code if you use this thing we've tweaked"

4

u/glydy Oct 19 '18

Yep, I've had to bump major versions for tiny things sometimes. It feels a bit wrong upgrading a major version for something so small, but a breaking change is a breaking change.

3

u/DerpsMcGeeOnDowns Oct 20 '18

So upgrade it like a responsible human being.

21

u/[deleted] Oct 19 '18

Because it’s the same over the top reaction every time.

It’s like everyone is learning for the first time that different pieces of software take different approaches to versioning!

I guarantee that when Angular 8/9/10 is released you will have to read through all of the same stupid comments again.

0

u/[deleted] Oct 19 '18

[deleted]

6

u/PalomSage Oct 19 '18

That is one approach. Not the only one. For example, when I worked with Southwest Airlines their commerce site used this structure X.Y.Z. where X are the last two digits of the year. Y is the number of the year's sprint which usually matched the month, and Z was the number of post activation hotfixes deployments that had to be done.

5

u/[deleted] Oct 19 '18

Ok, but it's been over 2 years now since Angular2 was released, and they made the versioning strategy clear back then!

Reading the same tired comments with each new major version is getting really old!

5

u/DerpsMcGeeOnDowns Oct 20 '18

People are still on React vs Angular??? 😂😂😂

2

u/uplink42 Oct 19 '18 edited Oct 19 '18

There hasn't been many breaking changes since v.2, and ever since 4.x most updates are quite trivial and ever since v6 you can run a CLI command that automatically fixes/warns you about deprecated features. v5 to v6 had major changes to rxjs imports but this could be remedied by importing a compatibility library.

I haven't experienced any major pains ever since the early days of 2.x and RC versions breaking things every month.

-6

u/[deleted] Oct 19 '18

This is just one of the reasons we have switched newer projects to react...

7

u/PalomSage Oct 19 '18

When a version number is more upsetting than features or issues with the framework. LoL. This is such a snowflake issue.

-4

u/[deleted] Oct 19 '18

"One" of the issues, and by far the least important. But who cares... as long as one can put in some virtuesignalling while responding

6

u/PalomSage Oct 19 '18

How was I virtue signalling? lol.

0

u/[deleted] Oct 19 '18

[deleted]

27

u/DerpsMcGeeOnDowns Oct 19 '18

5 to 6 required no changes??? Brah... I love Angular but this is factually, demonstrably, and unmistakably false.

0

u/[deleted] Oct 19 '18

[deleted]

2

u/barrybario Oct 19 '18

yep the rxjs changes were breaking for sure

1

u/DerpsMcGeeOnDowns Oct 20 '18

That and completely retooling the CLI, enabling multiple apps in a single workspace via architect, RxJS, the list goes on.

14

u/[deleted] Oct 19 '18

Angular 5 to 6 required no changes.

So they just aren't using semantic versioning? Major version upgrades should be breaking. If the changes don't break the API then it should just be a minor version upgrade.

12

u/Imposter1 Oct 19 '18

Angular 5 to 6 required no changes.

5 to 6 was a nightmare but that was mostly due to rxjs going from 5 to 6 and the auto update too not working very well on our codebase. We also didn't want to leave the rxjs compat lib in there.

Besides that, yeah I agree, it's been pretty smooth upgrades the whole way through.

2

u/A-Grey-World Software Developer Oct 19 '18

Depends if you're using the feature that breaks. 5 - 6 was a massive breaking change for me because I used a load of the RX stuff. I think the poster must have had some changes because RX is pretty integral into Angular - but if he didn't, then he might have had no refactoring. Maybe the auto update tool worked for him and he's forgotten!

It's still a breaking change to the API though, he's just not using that particular change.

Hell, updating to the latest version of TypeScript will be technically a breaking change, but very unlikely to actually impact anyone.

The animation system was changed, a breaking change. I'm guessing a lot of people's applications don't use Animations and they never needed to care. Still a breaking change.

0

u/DerpsMcGeeOnDowns Oct 19 '18

5 to 6 required changes for sure. Anyone claiming the opposite doesn’t know. Period.

1

u/itsmoirob Oct 19 '18

5 I think it was is the only really upgrade that broke my work (when they changed to their new .JSON file, plus the httpClientModule stuff)

-3

u/thatgibbyguy Oct 19 '18

the most confusing part of Angular versioning is how so many people struggle with it

Maybe... that's because the versioning is confusing.

18

u/DerpsMcGeeOnDowns Oct 19 '18

Let me break it down for ya:

0.0.1 = bug fixes

0.1.0 = features

1.0.0 = breaking api changes

Simple.

6

u/E2Ehh Oct 19 '18

Everything is confusing if you haven't learned it yet!

https://semver.org/

0

u/[deleted] Oct 19 '18

[deleted]

-1

u/thatgibbyguy Oct 19 '18

MAJOR version when you make incompatible API changes

If they're making API changes every few months... maybe the framework just isn't stable.

3

u/[deleted] Oct 19 '18

What makes you think it's not stable? It has many enterprise solutions running it.

-1

u/thatgibbyguy Oct 19 '18

The fact that they have to break their own API every five months would make it seem unstable. API changing that often is the very sign of instability. But whatever, I really don't care about this framework, I was just listing why people think angular is a joke.

3

u/E2Ehh Oct 19 '18

Bear in mind any single API change requires a major version bump. So of the many many packages that make up Angular (e.g. router, forms, http, animations etc etc) if any single one of them has an API change, they bump the version of the whole lot (all packages are incremented together so you can easily ensure compatibility)

Your post suggests that a major version bump means all APIs are changing and it's a ton of work for developers. In practice it's usually one or two tweaks here or there.

The worst breaking change I have experienced since Angular 2 beta was'nt even Angular - it was the change to RxJs - they changed their library fundamentally (from prototyped based function extensions to "pipeable" pure functions). And that only took a day or two on our (pretty big) solution.

When you say hyperbole like "people think Angular is a joke" it makes it clear you either are very inexperienced with this kind of webdev and don't know much about Angular at all, or you work in a bubble. Thousands of companies happily use Angular every day

2

u/[deleted] Oct 19 '18

You clearly don't know what you're talking about.

37

u/Rockytriton Oct 19 '18

Next version, Angular 8, everything moves to web assembly, no upgrade option either.

27

u/myhf Oct 19 '18

See you later, Angular-8-er.

1

u/e-gorman Oct 19 '18

well done.

7

u/[deleted] Oct 19 '18

I had high hopes that ivy will be released in this version, guess I'll have to wait for the next one.

3

u/A-Grey-World Software Developer Oct 19 '18

Yeah, It's a shame I was looking forward to Ivy.

3

u/[deleted] Oct 19 '18

Me too. I have some good expectations to it.

11

u/Wapen Oct 19 '18

I am wanting to fill out my skill set a bit more and tossing up between Vue, React and Angular. What would you guys recommend? Focus on one (which one would be best in your opinion) or gain a basic knowledge of all 3 and go from there?

13

u/nowtayneicangetinto Oct 19 '18 edited Oct 19 '18

Here's my bit of knowledge gained professionally to best help you out!

  • AngularJS

    • Excellent for learning a quick, stable, and widely used framework

    • It just makes sense. It's easy to learn and has a lot of baked-in features (directives) to help you get going.

    • Initially built for directives then retrofitted for components

    • Two way data-binding out of the box makes life easier as you learn.

  • Angular 2+

    • Steeper learning curve, but once learned is incredibly powerful.

    • Component based architecture

    • Also uses directives that help make DOM elements easier to create, manipulate, etc.

    • Direction of data is easier to manage (one way, two way, controller -> model, model -> controller)

    • Many companies that have antiquated AngularJS code bases are usually moving to this framework.

  • React

    • Light weight library that is fast and relatively easy to learn

    • Relies on solid knowledge of vanilla JS skills

    • Component based architecture, contains HTML and JS within a JS file.

    • Great for practicing JS and understanding the fundamentals

    • Many companies are using React from startups to large corporations.

    • Relies on state management, most prominently Redux, for larger applications

  • Vue

    • Think of it as the love child of React and AngularJS, has directives, lightweight and super fast.

    • Huge community and growing

    • Unique structure as it uses directives and components, built with both in mind.

    • Contains HTML, CSS, and JS in a .vue file

    • More and more companies are picking it up, but seems to be mainly startups.

    • Larger apps need state management like Redux or VueX

This is not a complete picture, just a few bullet points that come to mind. There are many differences between all of these Frameworks/libraries that I didn't even touch on. There are many purists out there that will make solid arguments for why you should use one over the other, but in reality, there is no "best choice". It comes down to the scope of your project and how you aim to accomplish it. Here's my final thought:

If you're new to JS go with AngularJS, it will build up a good foundation and make you viable for jobs.

If you're somewhat experienced with JS go with React, it will make your JS skills that much better and if you're really up for a challenge, learn and implement Redux.

If you're familiar with the core concepts of JS and modern frameworks, go with Angular 2+, it will force you to learn TypeScript and rxjs, as well as how to build a fully scalable powerful app.

If you're comfortable with JS and want to see how fast you can learn a new challenge, go with Vue.

I suggest Vue last because it is the least in-demand (at least from what I have seen) in terms of job listings. If you don't care about landing a job right away, go for any of these. They all present great challenges of their own and will make you feel accomplished no matter what. In the end, they will all make you fall in love with JS.

Best of luck to you, I hope this helped!

35

u/hansolo669 Oct 19 '18

I would strongly advise against learning AngularJS ... The writing is on the wall, and I don't know of any teams willingly adopting it for new development.

Plus the bizzaro injection system and dependency framework is just a handicap when trying to pick up anything sane (saying that as someone that did a lot of AngularJS work).

12

u/Calsem Oct 19 '18

I totally agree with this. Learning AngularJS is a career dead end.

1

u/_xiphiaz Oct 31 '18

Unless you want a career in maintaining those websites that refused to upgrade shudders

3

u/nowtayneicangetinto Oct 19 '18

I agree with the fact it is on it's way out. Which makes it a less solid investment for the potential for future growth, but there are many companies that still use it (a ton of enterprise) and are hesitant to move on to newer frameworks.

1

u/[deleted] Oct 19 '18

Agreed, the best bits of AngularJS exist in Vue.

4

u/Wapen Oct 19 '18

Thanks for the comprehensive answer! I am sorted on a job right now but just wanting to add more strings to my bow so I very much appreciate this.

4

u/nowtayneicangetinto Oct 19 '18

Any time! Glad to help. What ever route you choose to take, I highly suggest finding the associated subreddit and browsing through the posts. There are usually a lot of great articles submitted that can help you out.

4

u/Wapen Oct 19 '18

Wow that was fast, by the time I edited my comment you had replied.

3

u/RedditorFor8Years Oct 19 '18

Hi, is it right to say that all the frameworks you've listed above are for SPA only and won't work for multi page applications like e-commerce or blogs etc ? I haven't worked on frameworks like this since angular 1.2. Just wondering if Vue can be used in a e-commerce website..

5

u/E2Ehh Oct 19 '18

All of the above frameworks / libraries can be used in the setup you describe in one way or another.

For Angular, you'd probably want to investigate Angular Elements, which basically package up an Angular app into a "web-component". So include a script on your page, reference the new custom element in your template, and you're done.

https://angular.io/guide/elements

1

u/imhotap Oct 19 '18

React etc. are MVw frameworks for business forms and highly interactive web apps - the entire point is organizing your code around rendering HTML/DOM uniformly in response to user input and other asynchronous events. When you don't have much interactivity on your site eg. mere content and e-commerce sites (including text editors and simple forms) using frameworks is nuts, as HTML browsers are already highly specialized apps for this purpose. You also loose searchability/SEO, content syndication, content workflows such as for product catalogs, accessibility and everything else the Web stands for.

1

u/E2Ehh Oct 19 '18

You'd usually do something like this if you had a mostly static site (or an existing CMS / other server-rendered site) but needed to add a self-contained complicated widget to one page.

SEO is not an issue in situations like this (or if it is, it's entirely possible to server-render Angular / other isomorphic frameworks).

Not sure why you are suggesting accessibility is an issue - that's entirely down to how an application is developed...

0

u/imhotap Oct 19 '18

Thst's right. React, Angular & co. are for web apps/SPAs not web sites.

0

u/[deleted] Oct 19 '18

[deleted]

4

u/Mike_Enders Oct 19 '18

angular guy myself but this is utterly false. Sure since it was crafted in asia it has a lot of usership there but many other companies are picking it up
https://madewithvuejs.com/websites

Thats by no means complete

https://trends.builtwith.com/javascript/Vue

Sure React and even angular have far more but "precisely no one" and "only has audience in Asia" is totally and demonstrably false.

7

u/tweakdev Oct 19 '18

Agreed with your point, just wanted to point our that Vue was not crafted in Asia. It was created by Evan You during his time with Google and Meteor in the US.

In my experience in Denver right now, Vue is absolutely gaining traction with startups. Though React is still ahead by a good amount.

2

u/Mike_Enders Oct 19 '18

I don't think any open source project gets anywhere unless it us crafted by community support. I wasn't referring just to evan. The earliest community was Asian. The first time I saw it I passed because the docs were Chinese

1

u/tweakdev Oct 19 '18

This just isn't right either. You can checkout the days after launching Vue on Evan's blog. I think Laravel was the first established community to really take hold of Vue. Evan has said as much on a few podcasts, although I don't feel like doing the leg work to link them.

Vue became widely used in China for a number of reasons. Of course it still is. All I am trying to say is that it did not start there (not that that would be a mark against it), founder, initial releases, community, or otherwise.

1

u/Mike_Enders Oct 19 '18 edited Oct 19 '18

I know what I saw on github so I'll stand by it regardless of your objection. I probably should have specified that the docs I was referencing were not necessarily the official ones but third party projects and training (part of the community) A great deal of the community's work was in fact documented in chinese and some projects for chinese only (never said anywhere Evan did not have an english blog). I also said nothing about an established community taking on Vue but the community of Vue itself growing. You can stick your head in the sand if you wish but I see nothing wrong with a framework gaining a foothold anywhere on the planet so if you think I am putting a strike against it on that basis you are dead wrong.

I simply do not count the release date as the sole beginning of an open source project. We all know an open source project is still in its beginning phase until it has a community around it and its undeniable to me that solidified in the Asian community (and why shouldn't it? Some of the smartest people I have met) before it did in other countries. Thats reflected to this day.

0

u/[deleted] Oct 19 '18

[deleted]

1

u/Mike_Enders Oct 19 '18 edited Oct 19 '18

If you think all those sites are Asian then you are beyond delusional and anything will emphasize your point in your mind.

0

u/[deleted] Oct 20 '18

[deleted]

3

u/Mike_Enders Oct 20 '18

As long as they are not only asian your drivel has been proven false. Like I said "precisely no one" and "only has audience in Asia" is totally and demonstrably false. I've demonstrated it easily. Doesn't need for you to see or admit it. Everyone else not biased can see the evidence you are dead wrong and thats more than good enough.

0

u/[deleted] Oct 20 '18

[deleted]

2

u/Mike_Enders Oct 20 '18

The only moron is one who when caught in a demonstrable error plows on in abject stupidity hence owning his stupidity as an ingrained character flaw.

You wear it well

→ More replies (0)

2

u/denialerror Oct 19 '18

Yes, the world comprises of Silicon Valley and Asia.

4

u/[deleted] Oct 19 '18

I personally learned Angular first, but now after getting a bit familiar with all of them I would recommend React or Vue.

This really depends on your location, but in my experience React is by far the the most popular one and it's easiest to get job with.

Vue's popularity is growing and it seems like the easiest to learn.

Angular cool and all but there isn't that much trust in Google maintaining their shit well especially after what they did with AngularJS in the beginning.

4

u/[deleted] Oct 19 '18

Jobs? React

Most popular? React

Most libraries and custom components? React

Like linking everything yourself? React or Vue

Coming from Java/C#/Android? Angular

Want something that is structured (maybe rigid) and has the necessities for a non trivial SPA? Angular

Beware the view library trap. You want to do something and there might be multiple ways or multiple libraries to choose from. I've spent more time learning the different libraries more than React itself.

2

u/[deleted] Oct 19 '18

Try out all of them (on a small scale ~2d project). But decide for one of them to gain understanding on a deeper level (smallish ~2w project). Which one you choose should depend on the experiences of the first part -- Is the build easy (?), is developing intuitive (?), does it fit to your usual projects (?), does it integrate well with other frameworks you usually use... (?)

1

u/BoxMonster44 Oct 19 '18 edited Jul 04 '23

fuck steve huffman for destroying third-party clients and ruining reddit. https://fuckstevehuffman.com

3

u/E2Ehh Oct 19 '18

This is a good answer, just playing devils advocate here - for many larger companies / teams having that freedom to choose tooling / css solutions / whatever else can be considered a bit of a negative.

If you hire a new dev and they have used Angular before, they will jump in to the solution, be familiar with the CLI, the project structure, how everythign fits together. It's a huge productivity boost being able to swap developers in and out of solutions with minimal learning curve.

If someone has used React before, they might only be familiar with MobX and not Redux, or have use react-router v3 but not v4, or a completely different router module. The flexibility React gives (being a library rather than a framework) certainly make it appropriate for many situations, but flexibility is not a default positive thing in every scenario!

3

u/BoxMonster44 Oct 19 '18 edited Jul 04 '23

fuck steve huffman for destroying third-party clients and ruining reddit. https://fuckstevehuffman.com

0

u/Lauxman Oct 19 '18

Just do React because that’s the most popular one and easiest to get a job with.

-6

u/icemelt7 Oct 19 '18

ReactJS is the best

0

u/[deleted] Oct 19 '18

[deleted]

23

u/hansolo669 Oct 19 '18

Angular seemed overly complicated and at the end of the day was not flexible enough to suit my projects needs.

Overly complicated I won't disagree, but not flexible enough? Angular is over-engineered to the point where I struggle to think of something you couldn't represent (albeit, potentially awkwardly)

Good choice on Vue though. It would be a tough call if I was starting a new project today between Vue and React.

0

u/[deleted] Oct 19 '18

[deleted]

8

u/E2Ehh Oct 19 '18

Angular Elements can package up an app into a custom "web-component" to be embedded into a page - just include the built script, reference the new custom element in the template, and you're done. If you don't need a router (or forms or animations or whatever else) - just don't include them!

2

u/[deleted] Oct 19 '18

You don't have to include routing in your Angular project. In fact you have to opt in to having routing modules and whatnot added to your project.

1

u/Indubitables Oct 19 '18

Seems to be a very small project, why bother with a framework at all?

5

u/Wapen Oct 19 '18

Thank you, I appreciate it.

5

u/BrianPurkiss Oct 19 '18

A lot of people say they like abuse the best, but most job openings are for Angular and React. :-/

14

u/Spacey138 Oct 19 '18

As a programmer of 12 years I can confirm we like abuse best. At least based on my life choices.

1

u/BrianPurkiss Oct 19 '18

Well that was... an strange and sad autocorrect...

5

u/E2Ehh Oct 19 '18

I agree with this person - try them all and learn how they are similar / different, and which ones are suited to which tasks. Everyone learns differently but you may find TodoMVC a quick way to compare multiple frameworks / libraries

If you're finding Angular "too complicated", perhaps it's not the right tool for the job you are trying to do. Conversely, if building a large long-lived application with a large development team, that "complication" really starts to shine and hold together the structure and architecture as a product grows and evolves.

0

u/[deleted] Oct 19 '18

[deleted]

3

u/Wapen Oct 19 '18

Thanks for that! Vue was the one I was leaning towards.

3

u/E2Ehh Oct 19 '18

Personally unless op is completely new to programming and is feeling overwhelmed by new concepts, I would suggest trying TypeScript with any of the frameworks they decide to use. It's an incredibly powerful language and generally leads to a more structured reliable codebase, removing many of the JS gotchas.

0

u/[deleted] Oct 19 '18

[deleted]

3

u/lazilyloaded Oct 19 '18

Vue, the library itself, will be written in Typescript, but you'll still be able to use JS when using the library.

0

u/[deleted] Oct 19 '18

[deleted]

1

u/lazilyloaded Oct 20 '18

My mistake. I was confused why you brought up the language the Vue library was written in since the person you were responding to was worried about what language you needed to use the frameworks.

0

u/[deleted] Oct 19 '18

[deleted]

4

u/ekobeko Oct 19 '18

!Remindme 1 Year

1

u/RemindMeBot Oct 19 '18

I will be messaging you on 2019-10-19 11:58:19 UTC to remind you of this link.

CLICK THIS LINK to send a PM to also be reminded and to reduce spam.

Parent commenter can delete this message to hide from others.


FAQsCustomYour RemindersFeedbackCodeBrowser Extensions

3

u/[deleted] Oct 19 '18

Now I am five versions late.

5

u/Mike_Enders Oct 19 '18

Understand the issue but sorry - I have too much to do to argue about version numbering. Its always been a bit pointless. Plus whole number version changes have always been about feature sets not just breaking changes (though often they go together)...so ho hum. its still the javascript world - if you can't embrace rapid changes and feature additions then you can stick with python.

2

u/tarnos12 Oct 19 '18

And I am still using Angular 1.6

Oh well

3

u/ThisIsNowAUsername Oct 19 '18

Yeah we're on 1.5 from the project we started last year or so. We have a half-baked typescript implementation where you get all the cons and none of the pros lol

1

u/ThisIsNowAUsername Oct 19 '18

Yeah we're on 1.5 from the project we started last year or so. We have a half-baked typescript implementation where you get all the cons and none of the pros lol

1

u/TheBigLewinski Oct 19 '18

Have Angular engineers invaded this thread? There's a lot of condescension and downvoting being thrown around for anyone who dares question the update cycle.

The concerns of rapid major updates are legitimate. Angular is a framework, not an application. With a complex app, you can't just reboot your code and have it work. People invest lots of time and money building and testing a project, and refactoring because of a major release costs both time and money.

Stability is a major factor when it comes to adoption (for the above reason), and that has cascading effects. Large companies -job providers- tend not to pick frameworks which require significant overhauls just to keep it functioning and secure. And the larger the company, the more important that stability becomes.

To be fair, this isn't just a problem with Angular, it's prevalent in many front-end tools. While every developer understands -and even promotes- the concept of constantly improving tools, there's a threshold, a balance, when it comes to releases. If you are constantly changing your ideas, perhaps your ideas need to sit in the oven a little longer before they're released.

15

u/E2Ehh Oct 19 '18

Not an Angular engineer here, just a dev who uses Angular for their day job.

I think a lot of people who are fans of other frameworks like to jump in and make a deal out of Angular releases as a way to "1 up" for their framework of choice. I tend to downvote comments that don't contribute to the discussion, e.g. people who don't understand semver and just want to take a jab.

You are absolutely correct that stability is a major factor for a framework, and there needs to be a balance between innovation and stability. The Angular team seems to have set that threshold at 1 year. Major versions are released about every 6 months, and breaking changes have a whole extra major version before coming into effect (e.g. an API will be deprecated in v4, and removed in v5). Source: https://angular.io/guide/releases

That's pretty reasonable to me and my team, and if you use the framework as it's intended and practice good software architecture in general, the upgrades are usually pretty painless.

For example, when Http was deprecated in favour of HttpClient, it was literally 1 place in the code to go update, because we have a layer of abstraction between our components and the API. If we had build the app in such a way that each component was firing off API calls willy-nilly, it would have been a real pain. So sometimes when you see people saying upgrades were very hard, it's because they are working on a codebase that has not been built in a maintainable fashion. I would imagine they suffer from similar issues when upgrading other libraries or performing other routine maintenance.

As to your point of companies not picking frameworks based on churn, I think it entirely depends on the type of software being written. If I worked for an agency, and was churning out hundreds of sites a year for different clients, and needed to keep them all patched / updated but was not actively developing on them once released, I might not pick Angular. However I work on a single product (split into a handful of Angular applications), and we've been going since Angular 2 beta days and are still iterating on it with no end in sight. For this kind of product development, some minor framework changes once every 6 months / year is not a big deal, we're constantly doing this kind of maintenance as all of our dependencies update anyway.

So perhaps some of the condescension / downvotes being thrown around are by different groups of developers who don't entirely understand what the other groups are doing day to day. React vs Angular vs Vue vs WhateverJS is a bit of a silly debate IMO, they are all good at different things and people should pick the best tool for the job at hand and be happy for everyone else working on the web platform as a whole - we're all on the same team here!

4

u/gabynevada Oct 19 '18

Any insights on how to perform the HttpClient abstraction? Do you mean performing an abstraction between the HttpClientModule and the services?

5

u/ggeoff Oct 19 '18 edited Oct 19 '18

It's probably something as simple as

class RestService {

    constructor(private http: HttpClient) {}

    get<T>(path: string) : Observable<T> {
        return this.http.get<T>(path);
    }
    ...

}

class UserService { 
    constructor(private restService: RestService) {} 
    
    getUser(id: number): Observable<User> {
        const path = `path/to/user/${id}`
        return this.restService.get<User>(path);
    } 
}

Sorry for formatting on my phone Now you only inject the http client into the rest service so any changes that may happen to the httpclient in angular is isolated to our rest service. edit. fixed formatting

2

u/E2Ehh Oct 19 '18

Yep, this is essentially what we do ^

0

u/[deleted] Oct 19 '18

I couldn't care less about framework war, but this fast release cycle of Angular seems to bite Angular's adoption a lot.

More and more I see people having to choose a framework and there you have 7 versions of Angular (including JS). It's confusing, demotivating, doesn't promote Angular's adoption a bit. It feels like anything but a stable ecosystem.

Now, I know reality isn't that bad and that if you know Angular 2 you know all of the following releases, but whether you like it or not there are plenty of breaking changes between versions and other libraries that interact with them.

This just doesn't promote the adoption of this excellent framework. The last thing I feel I want to do is to start an Angular 7 project now, by the time you figure it out and so did most of the libraries there's already Angular 8.

If google's team wants to proceed that way, I'm happy for them, but Angular's popularity will keep eroding month after month as it keeps eroding since 2016.

4

u/E2Ehh Oct 19 '18

Is that really all that different to picking react, and coordinating changes to react-router, redux, whatever-forms-lib, and the other satellite of libraries you generally match up with react to make a full framework? This is just how front-end development is in general, you either stagnate (e.g. by sticking to an older framework like AngularJS / Knockout - not necessarily bad if it solves all your problems) or you innovate and adapt to change.

I struggle to see how Angular's well documented, regular, steady release cycle is confusing in comparison. In fact I would suggest it as a good reason for (enterprise) companies to adopt Angular over other frameworks. They have clear expectations of upcoming change and how much time will need to be allocated to maintenance.

4

u/Lauxman Oct 19 '18

The downvotes are because the refactoring due to breaking changes is almost always minor at best.

People like you act like every major version of Angular upgrading is the same as upgrading AngularJS -> Angular 2

1

u/Mike_Enders Oct 20 '18 edited Oct 20 '18

it seems to me this is more about version numbering rather than breaking changes. Your points are valid they are just not relevant to a version numbering debate. People are actually complaining that a new whole number version should have breaking changes. Version numbers makes no automatic argument for there being instability.

Whats more confusing is how people refer to angular2 for all versions but thats come about by social convention not official release numbers. Angular+ to differentiate it from the old angularjs is a better convention

Angular+ version 7 is a whole lot less confusing than
Angular2 7.0

thats almost bad enough to have been named by a microsoft team member.

1

u/E2Ehh Oct 20 '18

When Angular was pushed to v4 the team asked the community (at ng-conf or Connect, I forget which conference it was) to proactively change how they refer to it.

They said "AngularJS" for the legacy framework, and "Angular" for the new framework

2

u/Mike_Enders Oct 20 '18

yeah but its not working because not everyone said or wrote angularjs all the time for the legacy framework. they sometimes already shortened it to angular. I'm seeing lot of references to angular2 as anything version 2 or higher. Even subreddits r/angular2

1

u/[deleted] Oct 19 '18

All right. So, a quick question. Should I learn Angular or React?

3

u/A-Grey-World Software Developer Oct 19 '18

Look at jobs in your area and see what's most used.

I'd say you'd find Angular easier if you've got a C# or Java background. React if you've got a JavaScript and general web background.

1

u/[deleted] Oct 19 '18

I have a JS background. I think I'll go for React. Thanks!

-14

u/[deleted] Oct 18 '18

I don't understand what is happening with Angular. This is like a meme at this point.

28

u/[deleted] Oct 19 '18

They use semver, which can move faster than less objective versioning systems. Each major release is also a relatively painless upgrade, so it's really not that crazy.

25

u/PeEll Oct 19 '18

What version of Chrome are you running?

0

u/[deleted] Oct 19 '18

I don’t need to know

0

u/[deleted] Oct 19 '18

[deleted]

3

u/MatthewMob Web Engineer Oct 19 '18

You can do both of those things by changing a single Chrome flag...

5

u/IsoldesKnight Oct 19 '18

Integers are free.

0

u/[deleted] Oct 19 '18

[deleted]

-7

u/[deleted] Oct 19 '18

It's just the speed at which they decide it's time to release a version that's so different from the previous one they increment a whole integer. And it's speeding up.

7

u/aclave1 Oct 19 '18

Do some reading on semantic versioning. If there's any breaking API changes, it requires changing the major version (first number). So even a relatively small set of changes could warrant a major version change. Semantic versioning is great because we as library consumers can tell at a glance how difficult a library upgrade will be!

-2

u/[deleted] Oct 19 '18

Yeah I understand the concept. I was just arguing that the rate at which they release a possibly incompatible version is so quick.

8

u/PeEll Oct 19 '18

TypeScript 3.1 is a technically a breaking change (most apps should just work though). Do you want that breaking change to come at an unpredictable time, or in a way that isn't labeled as breaking?

0

u/ekobeko Oct 19 '18

suka blyat

0

u/gabdelacruz Oct 19 '18

Vuery nice..

oopss typo.. I mean very nice.. :)

-17

u/achauv1 Oct 18 '18

Damn Angular, chill ...

-13

u/the_interrobanger Oct 19 '18 edited Oct 19 '18

Angular 8 is just going to be removing all the code in the codebase and replacing it with:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,

MINOR version when you add functionality in a backwards-compatible manner, and

PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

EDIT: Oooh man I touched a nerve! Read up on semver!

-16

u/colly_wolly Oct 19 '18

Bloat and complexity. An example application that we created in a course I am doing weighs in at 208Mb. It only has a few basic form elements in it and some basic validation.

13

u/E2Ehh Oct 19 '18

An Angular hello-world app is 10kb - 20kb (haven't tried it in new 7.0.0 yet). Using the new rendering engine Ivy which is likely coming in 8.0.0 a hello-world app has been made at 3.2kb

Saying your app is 280mb by counting your node_modules is incorrect - you don't ship your node_modules to your end users...

I can build a .NET program which ships a 100kb exe file, but the .NET dev tools are gigabytes and gigabytes. It's pretty common, e.g. JDK, the Android SDK etc

5

u/A-Grey-World Software Developer Oct 19 '18

An example application that we created in a course I am doing weighs in at 208Mb

Did you take into account the operating system?

9

u/[deleted] Oct 19 '18

How is that even possible?! Did you use electron? Did you count node_modules folder?

-13

u/colly_wolly Oct 19 '18

Did what the instructor told us. (It probably is including the nodejs folder).

ng new npm install ng generate module (three times)

There is an unbelievable amount of code generated. The most valuable thing I have learned from this course is not to bother with Angular.

14

u/anubgek Oct 19 '18

The most valuable thing I have learned from this course is not to bother with Angular.

This comes off as somewhat naive. Especially when you previously state that you measure the size of the application by looking at the development folder

(It probably is including the nodejs folder).

Are you then saying you are not even sure what's included in the size you're so adamant about criticizing? Have you measured the size of the production package that would go to clients?

Yes there are a lot of dependencies but this is not for no reason. This allows for immense functionality and the ability to produce efficient compiled code that has all the bells and whistles that Angular provides.

I would wait until you're more experienced with web development in general before making these kinds of judgement calls as they don't appear to be coming from wisdom, but an initial emotional reaction to complexity you're not yet familiar with.

9

u/BrunnerLivio full-stack Oct 19 '18

Why are you bothering about the size of your node_modules folder?

Sure there is a lot of code involved, but it has its purpose. Angular is REALLY modular. They've built the whole framework in separate modules. That is part of why the Angular CLI generates quite some boilerplate, because it needs to specify the correct modules which will get imported. This is a drawback but also a huge advantage. You can only use the modules you actually need to develop your app. Therefor you can reduce the size of your final bundle by A LOT, if done correctly..

If Angular is built too complex for you and it does not suit your application; sure do not bother.. But there are tons of people who see a lot of benefit for Angular and its use case to use in the real world, so do not degrade it.

7

u/A-Grey-World Software Developer Oct 19 '18

Hey, I used React recently and it was Gigabytes big and cost me hundreds of dollars.

Like, they said "Get a computer, install windows on it then..."

Windows is massive man! That computer cost me loads of money. I learned never to use React.

Sarcasm aside. The one thing I've learned from your comment is you didn't learn much much on this course.

-6

u/[deleted] Oct 19 '18

I don't like Angular's policy a bit. Too many releases, too much confusion.

7

u/A-Grey-World Software Developer Oct 19 '18

Why is it confusing?

-2

u/[deleted] Oct 19 '18

Too many breaking changes, libraries that need to catch up, documentation that works for angular 5 doesn't for angular 3, same for stackoverflow questions, etc, etc.

Of course if you know any of Angular 2+ it's not a problem to catch up with what are generally minor api changes, but it doesn't change the fact that for people (either devs or management) looking at Angular it's not really motivating. By the time you started developing your product on Angular 7 everything's already moved on Angular 8.

I just don't like this release policy and it's pretty obvious it's not just me and it's biting Angular's popularity.

6

u/A-Grey-World Software Developer Oct 19 '18

The only time I've ever come across anything that was out of date is when I've stumbled upon some stack overflow answers on the beta. I've followed tutorials for Angular 2 before and not had any issues doing it in Angular 5.

To be honest, I'd rather the framework doesn't stagnate like AngularJS did being too afraid to make any change.

Also, it seems exactly the same with React. Except it's instead of Angular 2 or Angular 6 or whatever, you're actually dealing with Redux version changes (that's had breaking changes), or is it MobX people use these days? Or which version of React Router are they using Because version 4 is a lot different from version 3? What form validation library are they using?

React is a rendering library. To cover the full capabilities of a full framework like Angular you're dealing with a load of libraries for routing, state management, forms, animation etc. All these not only have different versions but completely different choices.

With angular, you look up a tutorial or SO post and there's a good chance everything will still apply. With React, that's only the DOM stuff, god knows what combination of other libraries and what versions they are using. And it's even more opaque because with Angular you just have to look at the "I'm using Angular 4" and you know exactly what they're using. With React, it's "I'm using React with Redux v3 and React Router v 4 with Redux-form!".

Ultimately both look to have similar churn, when you compare Angular to the React ecosystem, which is what it should be compared to.

5

u/Lauxman Oct 19 '18

There is no Angular 3 lol. Perhaps you don’t like everything you are ignorant about?

0

u/[deleted] Oct 19 '18

[deleted]

8

u/NoVABadger javascript Oct 19 '18

This sub is skewed toward people who are beginners (or at the dawn of their careers) and it really shows in the comments sometimes.

7

u/Fuego710 Oct 19 '18

Don’t hog your tasty subs, send a few over privately if you’d prefer!

0

u/[deleted] Oct 19 '18

[deleted]

3

u/Lauxman Oct 19 '18

Lol @ cscareerquestions being a good sub

0

u/[deleted] Oct 19 '18

[deleted]

7

u/FURyannnn full-stack Oct 19 '18

"hey i'm an upcoming grad who once wrote two lines of Python is this resume good enough for 130k salary???"

4

u/[deleted] Oct 19 '18

Just to say, you added absolutely nothing but flame to this discussion as well.