r/Angular2 • • Oct 18 '18

Announcement Angular 7.0.0 released

119 Upvotes

56 comments sorted by

13

u/[deleted] Oct 18 '18

17

u/snoob2015 Oct 18 '18

so where is the Ivy renderer 🤔?

2

u/DerpsMcGeeOnDowns Oct 18 '18

Broken as fuck

4

u/benduder Oct 19 '18

Really? source?

3

u/AbstractLogic Oct 19 '18

It was not released because it's not working yet. The team has changed the release to be sometime later in 7 but before 8. It should be backward compatible so they feel comfortable releasing it in a minor instead of a major.

1

u/DerpsMcGeeOnDowns Oct 20 '18

Source: Spin up a new ng project and pass the experimentalIvy flag to it.

0

u/[deleted] Oct 18 '18

[deleted]

5

u/[deleted] Oct 18 '18

16

u/JamesHalloday Oct 19 '18

That changelog for a "major" release sure does look like its just a bunch of bugfixes

14

u/DOG-ZILLA Oct 19 '18

The Angular versioning makes no sense.

5

u/AbstractLogic Oct 19 '18

They originally intended to release the Ivy compiler which would have been a good Major release but it's not ready.

It feels like they just put out 7.0 so they could hit their release date.

1

u/fridder Oct 29 '18

Supporting Typescript 3.1 is nice....

2

u/AbstractLogic Oct 29 '18

I noticed that as well. What is in typescript 3.1 that you are looking forward too?

7

u/A-Grey-World Oct 18 '18

I was googling this earlier today wondering it must be soon.

Shame there's no Ivy yet though.

9

u/Cloud_Strifeeee Oct 19 '18

Why ppl aren't excited about Angular theses days its all React ?

9

u/MJomaa Oct 19 '18

Same happening with React and Vue.

Frontend frameworks in general lost a bit of public interest because Angular, React and Vue fulfill most needs.

-6

u/systemadvisory Oct 19 '18

Or are totally unnecessary

1

u/jacobedawson Oct 19 '18

Not sure why that was downvoted - I totally agree - we shouldn't use frameworks by default, they are solutions to very particular problems. Sometimes using a full framework / library is simply overkill.

6

u/Lauxman Oct 19 '18

Many people here aren’t just rolling static blog sites. I’d venture to say that most are working at companies on web applications.

2

u/jacobedawson Oct 19 '18

I said I didn't understand the downvote just for voicing a reasonable opinion. As a professional dev I use frameworks when I need to to & vanilla JS when I don't.

There will be just as many newbies here as professional devs IMO, and a lot of them will start using a framework before even understanding JS under the hood, it's useful to know it's about choosing the right tool for the job :)

3

u/i_spot_ads Oct 21 '18

Totally unnecessary is a way of saying unnecessary in all cases, which is wrong as fuck. Some of us are creating web tools, not just blog websites, so we need frameworks, just like you would need a framework when you want to create an android or iOS app.

That's why the guy got downvoted

1

u/jacobedawson Oct 21 '18

I read his comment along with the previous guy's like a switch statement, in which case it's still fine ;)

3

u/Lauxman Oct 19 '18

React is easier to learn and use.

1

u/fatboycreeper Oct 19 '18

Personally, I lost interest because of the (IMO) insane versioning scheme they've got going on. I've read before why they decided to do it, but I'm clearly not convinced. Personally I prefer Vue over React too, but I'm not deep enough into any of them for my opinion to carry much weight, so there's that too. ;)

10

u/2uneek Oct 19 '18

Personally, I use frameworks I'm being paid to build with.

3

u/fatboycreeper Oct 19 '18

A very valid point, and I agree with that as well. My comment was more in regards to the idea of "excitement" but apparently I offended a few folks. lol

8

u/bfgenis Oct 18 '18

Good, now it’s time to wait for minor updates before it’s worth updating.

9

u/i_spot_ads Oct 18 '18

as per standard protocol

5

u/AbstractLogic Oct 19 '18

Seems like nothing special. Which is good from time to time. Just doing to needful.

5

u/kanto_squirtle Oct 19 '18

Just finished updating our enterprise app, and there’s another speed boost to it. Not as major as 5-6 but still a nice thing to have.

1

u/AbstractLogic Oct 19 '18

What feature gave you the speed boost?

2

u/kanto_squirtle Oct 19 '18

The most noticeable thing would have to be dialogs. They seem to open immediately now.

2

u/abdulkareemsn Oct 19 '18

I'm waiting for next zone.js release
There are fixes on trunk like proper pipeable rxjs support
Only zone.js is holding us back from removing rxjs-compat

5

u/E2Ehh Oct 19 '18

Interesting - what are the issues you have? We have been on RxJS pipeables (with no rxjs-compat) for quite a while now, haven't noticed any problems

0

u/abdulkareemsn Oct 19 '18

Our app run in very peculiar environment (it's kind like ie11 but not exactly ie11) so we use zone patching for rxjs to get change detection properly.

The current patching release requires rxjs-compat

1

u/blaster151 Oct 19 '18

Interesting, I'm not up to speed - will it be possible to get rid of all the annoying .pipe(...) wrappers and go back to just chaining operators together again?

1

u/sarunint Oct 20 '18

Unfortunately, it wouldn't happen, since operators chaining is not able to be tree-shaken.

2

u/NashobaSoft Oct 19 '18

Has it been 6 months already? Goodness, I understand the rationale, but versions used to mean something other than "age," which is what this versioning system is starting to amount to. Features will soon be thought of in terms of when they were released, rather than what they bring to the table. :(

3

u/AbstractLogic Oct 19 '18

Do you ever check what version Chrome is? You don't because it's updated constantly. Angular want's to be more like Chrome. They want to constantly upgrade and version is more about which set of files belong together as opposed to 'get the latest feature'.

You can tell this is the direction because they rely on ng-update and schematics now. The intent is that an upgrade will be nothing more then ng-update and any breaking changes will be auto-fixed with Schematics.

2

u/dustofdeath Oct 18 '18

Don't see a tag for it - last is RC1

4

u/beeman_nl Oct 18 '18

Doing the release takes a bit of time, but this is the official 7.0.0 release!

1

u/TotesMessenger Oct 18 '18

I'm a bot, bleep, bloop. Someone has linked to this thread from another place on reddit:

 If you follow any of the above links, please respect the rules of reddit and don't vote in the other threads. (Info / ^Contact)

1

u/weirdfishesza Oct 19 '18 edited Oct 19 '18

@ngtools/webpack version 7.0.1 for AOT builds now forces you to update to Webpack version 4

-11

u/sharath725 Oct 19 '18

I start learning Angular 2 and they release Angular 6!!

10

u/i_spot_ads Oct 19 '18

There is always that one guy in threads like this smh...

5

u/warhead71 Oct 19 '18

Its more like 2.6 - some call it angular 2.x (oppose to angularJS)

5

u/showsamorten Oct 19 '18

I started learning android 7 and they release android 9!!

4

u/E2Ehh Oct 19 '18

If you'd like to learn more about why the versions change so often you can have a read of this website:

https://semver.org/

Many many programs / frameworks / libraries all follow this same standard for updating their software.

There are more details on how Angular uses semver here: https://angular.io/guide/releases

0

u/[deleted] Oct 18 '18

[deleted]

8

u/gaytechdadwithson Oct 18 '18

meh, a lot of stuff but very possible nothing you HAVE to have.

3

u/alanjhonnes Oct 20 '18

Typescript support bumped from 2.9 to 3.1, so that is a very good addition.

0

u/[deleted] Oct 19 '18

[deleted]

1

u/showsamorten Oct 19 '18

What are you talking about? Angular release schedule have nothing to do with phone iteration, Angular have a 6 month release cycle, just like Chrome and Firefox have a scheduled release cycle, where they also update their major version number.

9

u/[deleted] Oct 18 '18

[removed] — view removed comment

8

u/cactussss Oct 18 '18

As per Changelog there are none.

There are Dependency updates though

12

u/swyx Oct 19 '18

soo does it technically have to be a major version bump? the api is unchanged

12

u/[deleted] Oct 19 '18

Angular do a major version bump every 6 months regardless of breaking changes.

This was put in place after community feedback over breaking changes in every RC.

It makes as much sense as React going from 0.14 to 15.0, frameworks are weird.

6

u/JimmyTheJ Oct 19 '18

Vue.js seems to have the most sane versioning.

3

u/flying-sheep Oct 20 '18

The react thing made a lot of sense.

React actually has breaking changes (with a sane deprecation policy), so major version changes made sense.

People referred to e.g. react 0.13 as “react 13”, so they didn't want to confuse anyone by going from “13” to “1”. But they also wanted to signify stability (few bugs, sane deprecation policy, production-level performance), so they had to get away from 0.x

Therefore that change