Angular 2.0 Website
angular.io
angular.io
There are currently two posts on Angular on the front page of HN. Both have quickly devolved into multiple rants decrying "breaking changes", which can be traced back to the initial Angular 2.0 announcement: http://angularjs.blogspot.com/2014/10/ng-europe-angular-13-a...
This really speaks to the importance of communication around these announcements. If you pay attention to what's actually communicated, yes, there will be a migration plan for 1.x apps. Yes, 1.x will be continued to be supported for much longer than the lifetime of most of your little startups - sorry to break it to you. Yes, 2.x is a much-needed step forward for SPA app development. BUT, when Angular 2 was announced, it was announced too early - they shared the fact that breaking changes were coming, and that AT THAT TIME, there wasn't a plan in place for migrating 1.x apps. That poorly phrased communication has since dominated any discussion about Angular 2, very much to the detriment of the project. It's the same thing as the Flickr, Instagram, Facebook, etc TOU changes that caused such a brouhaha in recent years, except that you would think technically-minded developers would be able to parse the actual information.
Compare it to Ember where they are bending over backwards to provide free improvements and a sane backwards compatible approach.
Why bet your entire business on a framework that has such poor communication skills? (Again: Assuming what you're saying is correct ;) )
Not sure how they can "recommend" 1.X when it's completely incompatible with 2.0. Might as well recommend Ember, React, or literally anything else.
I'm tired of people saying this. It's simply not true. The core team has said multiple times that there will be a migration path and they just announced today that you will be able to mix v1 and v2 components within the same project.
"Express your ideas with clean, understandable code. Angular is simple to build on, easy to change, and friendly to the way UX designers work. Create a UI that is beautiful by default, with material design and support for web components."
I think a lot of us already see AngularJS as a development framework. A big part of developing something is also UX design. Do you have UX designers on your development team? I know that I do, and I can help sell Angular to them if they feel represented (as they should be).
I was just commenting on the fact that they are marketing it as such. Previously, they didn't really seem to use such language.
I think it's a great move on their part, and it seems like it's a useful tool for rapid prototyping.
What am I missing here?
For reference: http://imgur.com/zdaMTFe
This looks and feels entirely different, and I don't care to start from scratch.
Angular 1.* will be around for awhile. It won't simply stop working. Eventually they'll stop adding new features, and eventually they'll stop fixing bugs. I don't know what the timeline is for that but it's far from immediate.
there is a weird "rawgit traffic error" banner across the site.
angular = php : obtuse and a little nonsensical at times, yet by far the most popular tool out there in industry.
ember = ruby : highly decorative and alluring, and it's even built by refugees of rails
react = haskell : esoteric, functional, and strange enough to come with its own dialect of js; it's literally the framework built for framework developers (to learn from)
backbone = C++ : fast because it has so little and therefore so little to slow it down
jquery = C : at some level, everything else seems to be built on this
meteor = computer language when portrayed on a Hollywood movie : you know, like in the first Wolverine Xmen movie, whatever language that they used to program Ryan Reynolds with that allows the user to just type in something like "Kill him" into the terminal and Ryan Reynolds then attempts to kill wolverine (sorry spoilers). I don't know if there are any commands other than "kill him", but it handles the "kill him" command with incredible automagic.