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

Angular 4.0.0 Now Available

angularjs.blogspot.com

Post reply on HN
Print view View original

291–300 of 360 posts

Re: Angular 4.0.0 Now Available

#291

Post by kevindqc »

tomelders wrote: post #288
ssijak wrote: post #183

Hmm. I see that Angular is getting aaaaalot of hate here. I really tried to understand why but have not found really valid reasons, just preferences. I have used Angular 1.x a lot and have just tried Angular 2. It really enables me (somebody who comes from primarily strong backend dev experience) to work on frontend SPA apps productively and fast. It does not 'feel' heavyweight or that it gets in my way too much, but…

I've got experience with Angular 1, 2, React+Redux, with teams of 5+ For me, the real problems in web app development are 1. State management 2. Side effects 3. View layer performance Angular pales by comparison to things like React+Redux which were born out of necessity, and as such, tackle those issues with laser like focus. Angular doesn't feel like it was born out of necessity, but out of some desire to just buil…

>When combined with things like Immutable, Sagas, and ReSelect, the Redux/React style of architecture (feel free to swap out Redux or React for whatever you prefer) is so much more practical and useful compared to Angular.

You can use all that with angular 2. I am.

Redux -> @ngrx/store

Immutable -> same

Sagas -> @ngrx/effects

ReSelect -> same

Example here: https://github.com/ngrx/example-app

Re: Angular 4.0.0 Now Available

#292

Post by kevindqc »

danielpatrick wrote: post #221
alttab wrote: post #212

Earlier quoted context omitted.

What's been your experience with browser-side debugging? The one thing that scares me about typescript is you end up debugging something you didn't write.

Yes, good question. I use VS Code (with the Chrome debugger plugin) and that works like a charm. I don't debug javascript in the browser anymore. TS provides source mappings to map the compiled javascript back to the source (similar to a .dll's .pdb maybe?). It took me some time to set up the config file which proved to be a headache (because webpack was screwing with the source maps), but again once that was set up…

That's been my experience too. Also once angular-cli seems more stable, I will probably switch to it and delete webpack (I know angular-cli uses webpack behind-the-scene, but at least I don't have to deal with it directly)

Re: Angular 4.0.0 Now Available

#293

Post by softwarefounder »

I'm using Knockout JS along with a micro hash-tag routing framework for my SPA. Couldn't be happier. Knockout JS is mature, and doesn't change. Yet there's still PR's that fix things here and there.

JS frameworks these days are such job creators. Which is great for consulting, but I don't want such mutability for my own products.

Re: Angular 4.0.0 Now Available

#295

Post by kevindqc »

sova wrote: post #88

Man y'all niggas is trippin. Angular changed completely with angular 2.0. If you say 2 and 1 are the same you are plain lyin' to yourself. I am not kidding. They are not the same thing, and should not be named the same. Likewise, pretending that 1+2 = 4 is just fool's talk. I don't care anymore for angular; Having your app-state in-sync with your code is great, but changing your whole paradigm every 6 months because…

Angular 1 was released 6 years ago. Was 'every 6 months' a typo?

Re: Angular 4.0.0 Now Available

#296

Post by tomku »

WorldMaker wrote: post #289
tomku wrote: post #283

Earlier quoted context omitted.

You've got it backwards. If you make a breaking change, semver requires you to bump the version number. There is absolutely nothing in the semver spec requiring you to make a breaking change when you bump the version number. The spec only specifies one of those directions, you're free to bump the major version for any change if you feel like it. Doing so would make your versioning scheme much less useful, but it's no…

There's also nothing in the spec that stops you from taking a very conservative view of what constitutes a "breaking change". There are many types of changes that may be backwards compatible and you're mostly sure shouldn't break anything, but you want to signal that it might just in case. What constitutes a breaking change that warrants a major version bump is a subjective problem left to project maintainers.

Totally agree, and I think that's what's going on with Angular. Bumping the major version for a set of modules also communicates that you really should be using 4.x of all these modules together rather than mixing and matching with 2.x, even if some subset of them are technically backwards compatible.

Re: Angular 4.0.0 Now Available

#297

Post by tomelders »

kevindqc wrote: post #291
tomelders wrote: post #288

Earlier quoted context omitted.

I've got experience with Angular 1, 2, React+Redux, with teams of 5+ For me, the real problems in web app development are 1. State management 2. Side effects 3. View layer performance Angular pales by comparison to things like React+Redux which were born out of necessity, and as such, tackle those issues with laser like focus. Angular doesn't feel like it was born out of necessity, but out of some desire to just buil…

>When combined with things like Immutable, Sagas, and ReSelect, the Redux/React style of architecture (feel free to swap out Redux or React for whatever you prefer) is so much more practical and useful compared to Angular. You can use all that with angular 2. I am. Redux -> @ngrx/store Immutable -> same Sagas -> @ngrx/effects ReSelect -> same Example here: https://github.com/ngrx/example-app

But why? If you're adding all of that to make Angular work the way you want it, what benefits are you actually getting from Angular?

Re: Angular 4.0.0 Now Available

#298

Post by tukelully »

throwasehasdwi wrote: post #242
jondubois wrote: post #231

Earlier quoted context omitted.

I don't particularly like TypeScript. It slows me down because of several reasons: - Compile time means that it takes more time to debug anything. - The rigid interfaces mean that I need to spend more time researching how to use various modules/libraries (maybe code completion would offset this problem but this is only possible with a heavy IDE that has intellisense or similar - Not Atom). - When I want to test somet…

Your complaints against "heavy" IDE's don't make sense. All of the points you made either aren't valid or don't matter. - They're slow and clunky Not anything I've used. Eclipse and Visual Studio run nice and smooth on a decent machine. - The use up a ton of memory. Who cares. Slack and anything based on electron uses hundreds of megabytes. Chrome regularly uses gigs. Most of the IDE's I use take less than 500 megaby…

Alot of these things do matter and it seems to me like all you're doing here is excusing bloat via hyperbole. I don't even agree necessarily with a lot of the parent comment, but I disagree with yours.

Re: Angular 4.0.0 Now Available

#299

Post by droidist2 »

wyldfire wrote: post #211
danielpatrick wrote: post #192

Earlier quoted context omitted.

Angular 2 is a different framework, plain and simple. You can continue to use AngularJS 1.x if you were on that framework. I understand the frustration of someone who has used AngularJS 1.x. There is not really a straightforward and low risk path to upgrading a production app. But that is like saying there is not really a straightforward risk to switching from AngularJS 1.x to React. They're different frameworks. Ang…

> Angular 2 is a different framework, plain and simple. I wonder if, strategically, it would have been a better idea to give it a new name rather than a subsequent version number?

I always figured it was to give the illusion of stability and continuity (ironically). Like "Angular has been out since 2010, before React and Ember" especially since a common criticism of Google is that they frequently abandon their projects.

Re: Angular 4.0.0 Now Available

#300

Post by robwormald »

bshanks wrote: post #269
aprdm wrote: post #14

Even with SemVer versions it looks really weird to see a new Angular relase branded as 4.0.0. Angular 1 to Angular 2 made me drop angular entirely, that happened less than 6 months ago I believe. Just reading Angular 4 gives me the creeps. Is 4 widely different from 2? How am I suppose to know if you using semver and already have a really bad history?

I propose a variant versioning scheme that bumps the MINOR version for backwards incompatibilities and reserves MAJOR version bumps for subjectively "big" changes. http://www.bayleshanks.com/wiki.pl?proj-sanDiegoVersioning

This is what the AngularJS versioning scheme was, nearly exactly. Everybody hated it. Hence, semver :)
Post reply on HN