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

341–350 of 360 posts

Re: Angular 4.0.0 Now Available

#341

Post by nkkollaw »

danielpatrick wrote: post #192
nkkollaw wrote: post #91

Earlier quoted context omitted.

I have a question. Who thought it was a good idea to make Angular 2 incompatible with Angular 1? You had it, and you blew it. Most people aren't going to use any version of Angular, now, and have switched to React and Vue.

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…

This is ridiculous.

Give it another name, then.

You can't get people to adopt your framework, stop developing it leaving millions of projects in shit, and then expect people to do it all over again.

I'm glad that Google paid this strategic error dearly, having a huge percentage of people switching to React. Perhaps next time they'll think about it more deeply.

Re: Angular 4.0.0 Now Available

#342

Post by nkkollaw »

pasta wrote: post #106
nkkollaw wrote: post #91

Earlier quoted context omitted.

I have a question. Who thought it was a good idea to make Angular 2 incompatible with Angular 1? You had it, and you blew it. Most people aren't going to use any version of Angular, now, and have switched to React and Vue.

"Who thought it was a good idea to make Angular 2 incompatible with Angular 1?" This is so much discussed that I am not going to answer that. Google it. But according to the latest StackOverflow survey [1] Angular is still bigger than you think: AngularJS 44.3%, React 19.5% [1] http://stackoverflow.com/insights/survey/2017/

That's legacy projects I bet. Of course, big projects have to stay with a technology for at least 2 years, can't keep rewriting things every time a new framework comes out. In this case, they unfortunately picked a framework that was discontinued.

I talked to many devs who didn't accept a job because it was Angular instead of React.

Re: Angular 4.0.0 Now Available

#344

Post by boubiyeah »

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…

Angular is a huge framework with a very OO style written by java devs. You have to learn many things to be productive with it, including a really weird string templating language.

The most funny thing probably is the typescript sale pitch (I use and like typescript) where you actually don't beneficiate from typescript at all with half of angular (string templates means no type checking or intelliSense on component names, model properties, component apis, etc)

It's also pretty fat and not exactly performant. It's simply a no-no on mobile. Its niche use case seems to be backend developers who know OO well, FP not so much, developing low/average quality back-office apps quickly without having to care about what's going on behind the scene.

The angular core devs always favor magic and shortcuts over simplicity. Its API surface is enormous, so have fun keeping up with the versions. It's optimized to get started quickly and be decently productive as long as you only use the core directives.

It's not terrible, but it's just not good if you care about the UX and maintainability of your app.

Re: Angular 4.0.0 Now Available

#345

Post by agumonkey »

bigmanwalter wrote: post #204
agumonkey wrote: post #133

Earlier quoted context omitted.

All good points, but FP has been a solid paradigm for a very long time, from people that had time and wisdom. It reduces very quantifiable issues like shared mutations, lines of code. Now that doesn't make js revisitation of fp pristine but still it's quite a refreshing thing. I never used Ang2+ but Ang1 was such a heavy thing; it was a OOP theory in itself, flipped around the DOM (I forgot their terminology but basi…

Never forget "Transclusion" and "Prototypical Scope Inheritance" The angular team seems to hate simplicity and love made up words.

PSI looks like a fabulous alias for inheritance.

Re: Angular 4.0.0 Now Available

#346

Post by leshow »

jondubois wrote: post #324
leshow wrote: post #320

Earlier quoted context omitted.

> - It requires more planning to do anything That's the idea. You think about what you're going to write in a strongly typed language rather than just throwing stuff at the wall hoping that something will stick. > - The rigid interfaces mean that I need to spend more time researching how to use various modules/libraries I don't understand this. In one case you have an API where the types of all the functions is avail…

>> - It requires more planning to do anything > That's the idea. You think about what you're going to write in a strongly typed language rather than just throwing stuff at the wall hoping that something will stick. I think this is a valid point for developers who only have a few years of experience but I've been coding professionally for over a decade now - I don't need the compiler to artificially slow me down - I'd…

> I don't need the compiler to artificially slow me down

It's slowing you down because you've written code with errors. Those type errors are still in your dynamic code, you just can't see them.

> I spent many years programming in ActionScript 3 and then Java so I feel like I've given typed languages a fair shot.

I don't think you have, you've missed many wonderful modern type system features.

Algebraic types, for one, aren't present in either of those languages and are massively useful, replacing 'null' (with a type like Option/Maybe) and exceptions (with a Result/Either concept) in many languages that have them.

Not to mention, with a language that has type inference, you don't even have to write the type in many cases, and yet you keep the guarantees of a strongly typed language.

Re: Angular 4.0.0 Now Available

#347

Post by lenkite »

boubiyeah wrote: post #344
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…

Angular is a huge framework with a very OO style written by java devs. You have to learn many things to be productive with it, including a really weird string templating language. The most funny thing probably is the typescript sale pitch (I use and like typescript) where you actually don't beneficiate from typescript at all with half of angular (string templates means no type checking or intelliSense on component na…

The ionic developers are using angular 2. http://ionicframework.com/docs/v2/intro/installation/ . So it it isn't a 'no-no' on mobile as you put it. Angular 2 AOT produces very lean JS.

Re: Angular 4.0.0 Now Available

#348

Post by dbbk »

parroquiano wrote: post #286
nrjames wrote: post #210

Earlier quoted context omitted.

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....

That was over 2 years ago.

Re: Angular 4.0.0 Now Available

#349

Post by petar_prog »

danielpatrick wrote: post #312
zdragnar wrote: post #234

Earlier quoted context omitted.

I have built multi-10k+ line applications in angular 1, 2 and react. My personal preference is react by a mile. The concept of modules and dependency injection was nice before we had any sort of module systems, but at this point it's essentially entirely busy work, given tools like proxyquire when testing. Template compilation errors are a nice step up from 1, but those that I've seen have been very misleading and ha…

You've build multi 10k+ line applications in Angular 2? It was released 5 months ago.

With my team, we have developed using Angular 2.0 beta candidate mid-size banking application for one of the biggest swiss banks, plus complex hypothec management and transfer application which is public on the bank website. We pretty much managed to release the apps before actual Angular 2 official release, and then we upgraded apps to official versions. It was really interesting to experience and it all went really smooth but we had to use Redux (just a note). So yes, there are some of us who are doing production ready code before the actual frameworks are released. Bold move, but a smart one in our case. Apps are almost bug-free (really edge cases are minor bugs). I do have to note that we are all Full Stack Java devs who have experience in banking and complex applications for a long time, plus we focused a lot on Angular in the past, so this transition with Typescript and Angular 2 syntax was a charm for us.

Re: Angular 4.0.0 Now Available

#350

Post by nkkollaw »

pasta wrote: post #106
nkkollaw wrote: post #91

Earlier quoted context omitted.

I have a question. Who thought it was a good idea to make Angular 2 incompatible with Angular 1? You had it, and you blew it. Most people aren't going to use any version of Angular, now, and have switched to React and Vue.

"Who thought it was a good idea to make Angular 2 incompatible with Angular 1?" This is so much discussed that I am not going to answer that. Google it. But according to the latest StackOverflow survey [1] Angular is still bigger than you think: AngularJS 44.3%, React 19.5% [1] http://stackoverflow.com/insights/survey/2017/

It was a rhetorical question...
Post reply on HN