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

281–290 of 360 posts

Re: Angular 4.0.0 Now Available

#281

Post by WorldMaker »

merb wrote: post #257
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…

> - Compile time means that it takes more time to debug anything. how can this be an issue? even javascript needs to be concated minified and whatever to take it into production. it's not like that any human writes minified and mangled javascript with direct gzip. P.S.: I'm not a fan of TypeScript. But to say you need to compile it, is just an excuse.

The Typescript compiler is also happy to run directly inside the browser because it is itself written in JS. I've debugged projects where the TS is compiled at runtime inside the browser and F5 refresh is the entire build process.

Though it's just as easy to use a good IDE's build button (VSCode Ctrl+Shift+B for instance) or TS works well as a watch process that watches for saves and compiles them when you save.

Re: Angular 4.0.0 Now Available

#282

Post by abiox »

throwaywgsid wrote: post #265
Vinnl wrote: post #125

Earlier quoted context omitted.

It's interesting how OP says people are moving towards more functional-style Javascript, but also dismisses statically typed Javascript. The two work really well together.

I'm convinced functional style is a fad and nothing will change my mind. The style has been around for forever and there's a good reason most languages are still OOP. We're in the phase of the hype loop where everyone assumes language designers from 15 years ago are idiots. In another few years everyone will be talking about the revival of OOP

> nothing will change my mind

you seem a bit committed. is this an emotional thing?

> there's a good reason most...

is there? is this reason related to languages themselves or their use? does it necessarily imply anything specific about "functional style"?

Re: Angular 4.0.0 Now Available

#283

Post by tomku »

batat wrote: post #207
Eric_WVGG wrote: post #7

Earlier quoted context omitted.

"Angular 1" is now known as Angular.js and is effectively at the end of its line. Angular 2+ is now simply Angular. All new releases follow a naming of version X.Y.Z where X indicates breaking changes, Y non-breaking new features, and Z is bug fixes. Version 3 is being skipped over due to poor naming of the related Angular Router lib. http://angularjs.blogspot.com/2016/12/ok-let-me-explain-its-...

I thought upgrading from 2.x.x to 4.x.x shold break something according to SemVer. So why "it's backwards compatible with 2.x.x"?

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 not actually breaking the semver rules.

Re: Angular 4.0.0 Now Available

#284

Post by WorldMaker »

throwaywgsid wrote: post #265
Vinnl wrote: post #125

Earlier quoted context omitted.

It's interesting how OP says people are moving towards more functional-style Javascript, but also dismisses statically typed Javascript. The two work really well together.

I'm convinced functional style is a fad and nothing will change my mind. The style has been around for forever and there's a good reason most languages are still OOP. We're in the phase of the hype loop where everyone assumes language designers from 15 years ago are idiots. In another few years everyone will be talking about the revival of OOP

Functional style programming is not a fad so much as a different taste. Not everyone will always have the same tastes. It's like peanut butter and chocolate: you can love only one or the other, you can also love both or know that each has different strengths for different needs (projects/desserts).

Re: Angular 4.0.0 Now Available

#285

Post by abiox »

onion2k wrote: post #72
otto_ortega wrote: post #57

VueJS is the only of these JavaScript UI Libraries/Frameworks I can stand... The only one whose syntax doesn't make my eyes bleed!... I can't wait for Alibaba's Weex to be officially released so Vue can be used for developing mobile apps too. Reusing components across platforms and the web is the only reason why I would like to jump into the JS wagon!

The only one whose syntax doesn't make my eyes bleed. To me that sounds like choosing a tool based on the experience it gives the developer rather than the experience it gives the user. That's entirely the wrong way to pick what to build an app with. User experience is far more important. (That's not a comment about Angular or Vue. They're both great, and you should use whichever is best for the web app you're writin…

> rather than

i don't know that this is strictly true, nor that these notions are mutually exclusive.

Re: Angular 4.0.0 Now Available

#286

Post by parroquiano »

nrjames wrote: post #210
EugeneOZ wrote: post #153

Earlier quoted context omitted.

There was Ember.

Discourse uses Ember. It's pretty successful. http://www.discourse.org/

Ember has bad performance on Android[0]. The Discourse team had to write their own Virtual DOM renderer to work around this[1].

[0] https://discuss.emberjs.com/t/why-is-ember-3x-5x-slower-on-a...

[1]https://eviltrout.com/2016/02/25/fixing-android-performance....

Re: Angular 4.0.0 Now Available

#287

Post by nogridbag »

kitsune_ wrote: post #118
thewhitetulip wrote: post #87

Earlier quoted context omitted.

Despite being new to AJAX, I wrote a Vue app within a week, 4-5 weeks into reading Angular, I was still reading the docs. Edit: removed a brash statement.

Yes and no. It says as much about you as it says about Angular or Vue. Look, Angular is far from being my favorite framework, and I have nothing against Vue, I'm more of a ClojureScript / om.next guy myself. I'm just really allergic to brash statements about frameworks, or hype in general. How easy it is to get up and running with a framework doesn't actually tell me that much about the framework. Is the apparent sim…

Having used Vue for a month or so and Angular now for only a short period, I can easily say Vue is easier to learn for two reasons (neither of them being magic):

1. The documentation is excellent. It's short enough to read in one sitting and comprehensive in that every option is documented without needing to resort to third party websites. When a new feature is added even in a minor version upgrade, that new feature is in the documentation (and marked as NEW). The search is also great and separates results into "Guide" and "API" categories.

2. Vue itself is extremely cohesive and user friendly. User friendly can mean many things. One of those is simply terminology. For example, in both Angular and Vue, templates can have child content. AngularJS and Angular use the terms Transclusion and Content Projection while Vue templates can have "slots": a term which doesn't require a CS degree to understand the intent.

The Angular documentation is simply not good: the organization, navigation, search, and writing style are vastly inferior to Vue's docs. Many sections are written in tutorial form repeating the same information (or mentioning important information in an unrelated section). It's hard to find what you're looking for and in many cases things simply aren't documented. For instance, speaking of Content Projection, it's a major feature and it's nearly impossible to find in the docs unless you already know ahead of time that it's called "Content Projection". I had to learn about it from a third party blog which made me question if it was even safe to use. There's even an open JIRA item noting this:

https://github.com/angular/angular.io/issues/3099

Other things that bit me recently were key modifiers in which the possible options are only mentioned on the github issue page (not in the docs).

Re: Angular 4.0.0 Now Available

#288

Post by tomelders »

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 build a framework. As such, it's complicated and magical feels clumsy by comparison.

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.

I don't know what it is that makes Angular popular with back end developers, but they seem to be Angular's biggest supporters. I consider my self full stack, but front end first, and I've noticed that people like me tend to favour libraries over frameworks. There's obviously something that is informing each groups opinions on this matter, but I don't know what it is.

Re: Angular 4.0.0 Now Available

#289

Post by WorldMaker »

tomku wrote: post #283
batat wrote: post #207

Earlier quoted context omitted.

I thought upgrading from 2.x.x to 4.x.x shold break something according to SemVer. So why "it's backwards compatible with 2.x.x"?

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.

Re: Angular 4.0.0 Now Available

#290

Post by WorldMaker »

manquer wrote: post #229
ErikAugust wrote: post #4

Earlier quoted context omitted.

SEMVER - Semantic Versioning - http://semver.org/

Not exactly semver either, Angular 4 is backward compatible with 2.x.x. Following semver would mean it should continue to be in 2 series

It makes breaking changes that might break some users. That is following semver. Semver doesn't follow backward compatibility in the major number, it follows potential breaking changes that will impact downstream consumers.
Post reply on HN