201–210 of 360 posts
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.
(They don't understand TypeScript. The argument is as stale as the 0.8 release)
I have been leading a good sized Angular app for work for the past 8 months, and upgrading from v2 to v4 has been painless, even while having an AOT compilation build pipeline set up - the only modifications we had to do was switch OpaqueToken to InjectorToken, to , and Renderer usage to Renderer2, and these weren't required to be done yet. We only did those changes to get ahead of the curve from the deprecation mess…
Earlier quoted context omitted.
Is ironic just yesterday I read almost the same thing but trashtalking pseudofunctional programming in js, declarative components, microframeworks and dependency hell over all-in solutions, etc etc... The reality is you don't really have any idea of what future of web development is, as anyone has. The community is not oriented in any way... rather we are probably in the time of biggest uncertainty and most frequent…
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…
Earlier quoted context omitted.
Is ironic just yesterday I read almost the same thing but trashtalking pseudofunctional programming in js, declarative components, microframeworks and dependency hell over all-in solutions, etc etc... The reality is you don't really have any idea of what future of web development is, as anyone has. The community is not oriented in any way... rather we are probably in the time of biggest uncertainty and most frequent…
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…
The angular team seems to hate simplicity and love made up words.
Earlier quoted context omitted.
"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/
Most companies don't switch quickly. We have a huge Angular 1.x app, but after hiring some new developers for our team we found the pool of React devs was huge compared to Angular devs. So much developer goodwill and mindshare has been lost. After carefully evaluating the technical aspects of Angular and React and externalities like the above, we decided to start building new software with React. Angular won't go awa…
Angular is actually better off with the break as new graduates may use it to replace vue as the new fad once vue has replaced react.
Earlier quoted context omitted.
"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/
Because Angular was the only real choice for awhile. That's like saying PHP is still bigger than you think because half the web runs on PHP but that is old legacy shit. Almost othing new and serious is using it.
I'm so out of the loop… Feels like a week ago everyone talked about how cool and performant v2 will be when it's finally out of the beta and officially ready for production, and now there is v4 release. What's going on with versions?
"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-...
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…
That being said, Angular is still a valid option (haven't tried Angular 2, but from what I've read it's a nice upgrade over Angular 1). I'd still take React any day of the week over it, just for the simplicity it brings. Of course there are other drawbacks to using it, but nothing's perfect.
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…
Earlier quoted context omitted.
Because Angular was the only real choice for awhile. That's like saying PHP is still bigger than you think because half the web runs on PHP but that is old legacy shit. Almost othing new and serious is using it.
There was Ember.