Slashdot Mirror


Google Says Angular 2 Will Support Python, Java (thenewstack.io)

An anonymous reader writes: Google will release a faster beta version of Angular 2 in about two weeks, with a smaller version targeted for April. "We're improving our ability to handle different languages," says Google's Brad Green, noting that 213 contributors are currently working on Angular. "Our plan is to have versions that will work with many server-side technologies, from Java to Python." Microsoft has already demonstrated how it's building Angular into ASP.NET and Google is also working with the Drupal team. But Green says they'll also continue supporting Angular 1 for at least another year, until a majority of users have transitioned to the new syntax. Google says there are currently 21.3 million developers using Angular 1, compared to just 300,000 using Angular 2. "We've got a ways go to," Green admitted.

92 comments

  1. js crapware fad of the month by ralphsiegler · · Score: 5, Insightful

    no one values a stable web platform any more? they have to use lastest fad thing?

    1. Re:js crapware fad of the month by xxxJonBoyxxx · · Score: 5, Funny

      >> no one values a stable web platform any more

      To their credit, they did the right thing in incrementing the major version number.

      >> Google's Brad Green, noting that 213 contributors are currently working on Angular...Google says there are currently 21.3 million developers using Angular 1

      1 developer for each 100,000 users. Coincidence...or aliens?

    2. Re: js crapware fad of the month by Anonymous Coward · · Score: 0, Interesting

      I have used angular2 for a month now and I hate javascript. But I have to say that this is the best Javascript framework I have seen. The component architecture makes it possible to create actually generic and reusable components. I still think that .net will go away soon but angular2 will probably be the most important and used thing in the net. And quite soon even. Within 1 or 2 years.

    3. Re:js crapware fad of the month by Anonymous Coward · · Score: 0

      All so they can add some shit 3D video effects or scrolling image galleries that go SIDEWAYS! AWEEE!

      Anyone that mentions JS library to me gets called a cunt and blocked.
      Worst type of Web Developer. Seriously.
      I've never met one that isn't a total insufferable douche.

      "b-b-but JS is so broken and complex i'm a blabbering retard with an IQ less than a stone pls help"
      JS is fine. 90% of the broken crap was fixed OVER FIVE YEARS ago.
      The rest is retards using beta stuff that they shouldn't be using in production then whine when the standards get finalized and the interface usually gets changed, and Microsoft just refusing to comply with every other web browser vendor. (although admittedly they have gotten better with recent browsers)
      Oh, and class-loving morons trying to apply class-based code to prototypes. Durr. The funny thing is the new object system is literally syntactic sugar on top of prototypes. Yeaaah, even slower websites. I'm proxy-blocking people that use objects on their sites, they are too stupid to be web developers.

      The only thing wrong with JS is the DOM, which needs to be scrapped entirely and rewritten from scratch and made completely incompatible with any code that exists now. Backwards compatibility is the reason Webdev is crap. The amount of BLOAT caused by that crap is awful.of script is the new one.
      JS Harmony would make a great place to rip the DOM out and replace it with something that doesn't suck 21 kinds of ass, since Harmony isn't compatible with current JS.

      I'm going to sleep. Thinking about moronic developers has given me brain herpes.

    4. Re:js crapware fad of the month by rasmusbr · · Score: 1

      1 developer for each 100,000 users. Coincidence...or aliens?

      Either one of those, or a sudden resurgence of feudalism. You might want to join as a contributor just to be sure.

    5. Re:js crapware fad of the month by Zalbik · · Score: 2

      1 developer for each 100,000 users.

      That sounds *exactly* like the thinking of a machine to me.

      Where's Keanu Reeves when you need him?

    6. Re:js crapware fad of the month by Anonymous Coward · · Score: 0

      "b-b-but JS is so broken and complex i'm a blabbering retard with an IQ less than a stone pls help".

      I've talked to quite a few guys who have that attitude. Upon being quizzed about what's broken, here's what I usually get:

      * A bunch of crap they've read on various web sites but can't even understand enough to explain what they think it means
      * They think Javascript can't do something it does quite well but that they don't know how to do
      * They start complaining about the DOM, with most of those complaints being about its verbosity

      It's a perfect example of a poor craftsman blaming his tools.

    7. Re:js crapware fad of the month by Anonymous Coward · · Score: 0

      We use it, and it's gotten pretty stable after Microsoft took it over and ended all innovation. Expect it to be stable, err, stale.

    8. Re: js crapware fad of the month by Anonymous Coward · · Score: 0

      Microsoft promised that their proprietary language would evolve to better support Angular. That hasn't happened.

    9. Re:js crapware fad of the month by Anonymous Coward · · Score: 0

      Your commentary and the upvotes confirms one thing: slashdotters have no interest in learning new things. I expected more of my elder peers.

    10. Re: js crapware fad of the month by Anonymous Coward · · Score: 0

      You seem very angry, who hurt you? TypeScript?

    11. Re:js crapware fad of the month by Anonymous Coward · · Score: 0

      Yeah, ever since JS got popular it's been attracting a lot of bullshit. It makes it difficult to pick out the good stuff.

    12. Re:js crapware fad of the month by Anonymous Coward · · Score: 0

      How the fuck is this insightful? JS gives superior UX and reduces the amount of web traffic and your server load by multitudes. You Sir are a moron.

    13. Re: js crapware fad of the month by Anonymous Coward · · Score: 1

      I still think that .net will go away soon

      You think that because you're ignorant and don't know WTF you're talking about. If you think that .net exists only for web development then you don't know .net and if you think that web or phone is the only type of computing we'll need in the future then you're really out of it. The part of the software world that most consumers see on a daily basis is actually a very small part of what's out there and arguably it's not even the most important part.

    14. Re:js crapware fad of the month by Anonymous Coward · · Score: 0

      Your commentary and the upvotes confirms one thing: slashdotters have no interest in learning new things. I expected more of my elder peers.

      We've been around long enough to have seen the last 4 or 5 new things, you know the ones that nobody talks about anymore and only we remember, and we've learned that newer is not always better. In fact, it's very often worse. If a technology is used and improved continuously for 10+ years and people are still using it, improving it and talking about it after all that time, it may be worth something. You may learn that eventually if you can survive long enough in the software business. Here's another pro tip: the needs of Facebook, Apple, Netflix and Google (aka the F.A.N.Gs) are not necessarily your needs. Why make their problems your problems if you don't have to?

    15. Re:js crapware fad of the month by phantomfive · · Score: 2

      no one values a stable web platform any more?

      There has never been a stable web platform for frontend.

      --
      "First they came for the slanderers and i said nothing."
    16. Re:js crapware fad of the month by Anonymous Coward · · Score: 0

      welcome to computing.

    17. Re: js crapware fad of the month by Anonymous Coward · · Score: 0

      Your cranky developer shtick is dreary. You are boring and wrong.

    18. Re:js crapware fad of the month by grumpy-cowboy · · Score: 1

      Yes, it's called HTML.

      --
      Will $CURRENT_YEAR be the year of the Linux Desktop?
    19. Re:js crapware fad of the month by Anonymous Coward · · Score: 0

      UX

      Go back to HN/reddit.

    20. Re:js crapware fad of the month by Anonymous Coward · · Score: 0

      Except for that side path for XHTML where, I had to re-learn how to code HTML whilst listening a lot of gas about how great XML conformity would be...

    21. Re:js crapware fad of the month by phantomfive · · Score: 1

      Yeah, stable, unless you want to have a div that is relatively positioned, clickable, and also has some transparency. Because IE will chop off the bottom of the div (don't ask me why). And a myriad of other instabilities over time.......

      --
      "First they came for the slanderers and i said nothing."
    22. Re:js crapware fad of the month by phantomfive · · Score: 1

      I should change my previous comment, because it wasn't very good. Here is what I meant:

      If you look at a web page from the 90s, here's an example so you can remember, it's not going to be acceptable to modern users. It looks ugly. Furthermore, the tools used to build it (like tables) are outdated, and your coworkers will yell at you if you use them now.

      Moving forward, in the early 2000s, everything looked really square, so now, if you don't add a radius to the corners of your divs, then people will say, "Oh, your website looks old."

      More importantly, in the last two or three years, we've seen the advent of the responsive web. The way the 'responsive web' was designed means that anything built before 2012 looks rather lousy on cell phones.

      Now, of course, you are right that the web page from 1997 will probably still render, but it will look really bad everywhere. Compare that to TCL-TK which apps built in 1997 actually look really good right now.

      --
      "First they came for the slanderers and i said nothing."
    23. Re:js crapware fad of the month by Anonymous Coward · · Score: 0

      You're obviously a fucking pussy. Real developers use assembly.

    24. Re:js crapware fad of the month by Anonymous Coward · · Score: 0

      Is that anything like asm.js?

  2. Re:JAVA? by Anonymous Coward · · Score: 5, Funny

    Who uses Java anymore? I thought that stuff was virus-prone. I haven't installed Java in years.

    It's depressing that I can't know for sure if you're trolling or genuinely that stupid.

  3. What is Angular? by MobileTatsu-NJG · · Score: 4, Funny

    I'm assuming this is some sort of fishing-related framework.

    --

    "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    1. Re:What is Angular? by Harold+Halloway · · Score: 1

      Who knows? You can be sure the /. won't tell you.

    2. Re:What is Angular? by Anonymous Coward · · Score: 0

      It wouldn't be Slashdot if the editors, you know, editted.

    3. Re:What is Angular? by Anonymous Coward · · Score: 0

      It's sad when people on /. don't know of a major web application technology.

    4. Re:What is Angular? by Anonymous Coward · · Score: 0

      Way to miss the fishing pun, Moss.

    5. Re:What is Angular? by Anonymous Coward · · Score: 0

      It is the stupid shit users post more than the editors. Off topic (Score:5 Speculation)

      Retards!!

    6. Re:What is Angular? by Jack+Griffin · · Score: 3, Interesting

      I thought this was news for nerds, not news for web app developers....

    7. Re:What is Angular? by irrational_design · · Score: 1

      Not all nerds are web developers, but all web developers are nerds?

    8. Re:What is Angular? by Anonymous Coward · · Score: 0

      Dont quote me on this but I believe it is a geometry framework pioneered by the pioneer pythagoreus :p

    9. Re:What is Angular? by Darinbob · · Score: 1

      No, web app people treat development as a day job, to tide them over until that acting gig kicks in.

    10. Re:What is Angular? by Anonymous Coward · · Score: 0

      Right, because everyone here is a fucking web developer and IT consists of no technology other than web sites.

    11. Re:What is Angular? by Anonymous Coward · · Score: 0

      No. Web dev actually has some cool things going for it. The web has become the real "write once run anywhere" platform that Java promised years ago, and JS engines have been optimized to within an inch of their lives. Not a patch on C/C++, but it kicks Ruby into a cocked hat.

      On the other hand, there's the continual library churn. Half of everything you know is obsolete in five years. People here on Slashdot get annoyed just hearing about it. It's a mixed bag, but there are reasons to want to do web dev exclusively.

    12. Re:What is Angular? by irrational_design · · Score: 1

      What?! You mean this 6-figure job I've been doing at a fortune 50 company for the last 14 years is just a temporary gig? Why didn't anyone tell me?!

  4. Re: JAVA? by pchasco · · Score: 2

    Apparently a lot of people still use Java: http://spectrum.ieee.org/compu...

  5. Re:JAVA? by Anonymous Coward · · Score: 0

    He probably means the JAVA web plugin, which is a notorious virus prone plugin.

    I guess they are integrating it for server side java? im guessing scala, or play, or w/e

    Anyhow, as the majority of the people who have posted have said: DO NOT WANT REGARDLESS

  6. Front end? by roninmagus · · Score: 4, Interesting

    Can someone explain why the backend matters? I've not used Angular 2 but have used 1 extensively, and it always just calls a rest service for JSON. I understand others will have other needs, but won't you always just be calling a URL to get or submit data? That service could be written in BASIC for all I care.

    1. Re:Front end? by xxxJonBoyxxx · · Score: 2

      Long story short, I think it's that major IDE's (e.g., Visual Studio, Eclipse?) will now be "compiling to typescript" where the typescript will be leveraging the Angular 2 framework. (Anyone...accurate?)

    2. Re:Front end? by Luthair · · Score: 1

      I'm guessing precompiled templates. (e.g. for a search engine)

    3. Re:Front end? by Anonymous Coward · · Score: 5, Interesting

      The main case for backend support is isomorphism.

      You run into a few problems when you put angular1 or 2 apps into production on the SEO side of things and also on the first hit performance side of things.

      For the SEO side of things, even though the google bots do execute javascript they do not wait for async actions to complete. Angular Apps usually load some templates via XHR and/or json data from a service, so these won't complete and google will index a broken site where nothing works.
      ( Don't mention prerendering via a headless browser, this does not work and will never work )

      On the other side of things even if you inline and minify templates etc... you will always either have a big bundle of templates to download on the first hit ( more than you acutally need ) or load them individually... So you end up with a lot slower first hit experience than you might want.

      Enter isomorphism: The idea is to have your client side routes also exist on the server, so that when a user or google comes in the server can render out the necessary templates and even service data directly to the returned page, so zero async calls are required and rendering can start immediatly .all while downloading the EXACT content needed for that. and no more.

      Afterwards the normal rendering process takes over and its business as usual.

      This requires server support ( we had to write it ourselves for ASP.NET Core 1.0 in my last project ) and ideally should be DRY....
      We currently configure our angular ui-router routes just on the server specifiy template and data dependencies and the server renders it out exactly like that ( prepopulating the template cache and the data cache of angular 1 )

      We have gotten our first hit time to a fully rendered page ( neglecting any networking latency ) down to 50ms that way, and we have no extra work anymore to keep the SEO people happy.

    4. Re:Front end? by Anonymous Coward · · Score: 0

      ... god help us.

    5. Re:Front end? by gohmifune · · Score: 2

      Perhaps they aren't referring to the backend, but the language that one would use before compiling?

    6. Re: Front end? by Anonymous Coward · · Score: 0

      Haven't you heard? We should all be calling isomorphism "Universal JavaScript" apparently.

    7. Re:Front end? by Anonymous Coward · · Score: 0

      Oh, thats just where ALL the business logic resides, you know unimportant stuff like customers, products, inventory, orders and so on. Atleast in basic we get to use goto so what the heck, why not!

    8. Re:Front end? by Anonymous Coward · · Score: 0

      Huh? What is typescript?

    9. Re:Front end? by cyclomedia · · Score: 2

      Wait, what? You're saying that if I went to http://example.com/x/y/z Directly I'd get the exact same HTML rendered out as if I'd gone to http://example.com/ and clicked a link to /x/y/z ?

      So basically, after forcing all this ajax on everyone for years you're finally getting back to Web 1.0 with proper links that actually link to stuff instead of linking to a pile of javascript

      --
      If you don't risk failure you don't risk success.
    10. Re:Front end? by Hevel-Varik · · Score: 1

      This is a 5 comment. Not sure why it isn't up there.

    11. Re:Front end? by Anonymous Coward · · Score: 0

      > Huh? What is typescript?

      Here you go

  7. Highly Questionable Messaging by Anonymous Coward · · Score: 0

    The leadership of the Angular 2 team is at it again. They have an amazing habit of twisting the truth. Watch closely what they say at public conferences from the stage and compare that to what is actually happening and it becomes obvious (even more so if you go read their design docs and meeting notes yourself).

    21.3 million developers using Angular 1? I don't think so. They are taking their web site traffic, or the number of people "trying out" the framework and assuming that equals numbers of active developers. The same goes for Angular 2. That's highly misleading.

    The whole server-side thing is marketing garbage too. A front-end framework should be able to work with any server-side technology out of the box. They are making it sound as if other frameworks and libraries don't work well with Python, for example. The Microsoft example they give is based on a prototype that one developer inside Microsoft did in a couple of weeks. Microsoft has said they are planning to support other frameworks with their technology too. So, this is an Angular play at making it look like they are the only thing compatible with Microsoft tech.

    What a bunch or rubbish.

  8. Should work with any type of server side technolog by jjn1056 · · Score: 4, Informative

    Angular.js is a framework that runs on the client, typically a web browser. At the minimal you need a web server written in any old language and it communicates to the server via existing protocols, AJAX, HTML forms, etc. Any backend language will work. I use Angular2 beta right now with my Perl based web application.

    Maybe they intend to release tools and plugins for popular frameworks to make it easier? I have no idea...

    --
    Peace, or Not?
  9. They should call it !Angular by ilsaloving · · Score: 2, Interesting

    I was a major fan of Angular until all this crap with Angular 2.

    Was it *really* necessary to make fundamental changes to the syntax, thereby making it completely incompatible with Angular 1? It's dishonest to even call it Angular 2, when it has almost nothing in common with the previous.

    And everyone thought Java's constantly revolving APIs were bad...

    1. Re:They should call it !Angular by Anonymous Coward · · Score: 0

      Wait... What? Java's APIs are among the most stable of any language. It's one of the major complaints actually. Java 1.2 code can run comfortably on a 1.8 JVM.

    2. Re: They should call it !Angular by Anonymous Coward · · Score: 0

      Half-way through writing a large app in Angular I began to really like it. Towards the end of that same project I realised it was crap. It's slow and doesn't make any sense. They added controllers that ended up being useless and the whole framework doesn't work unless you use a third-party router. Also their module system is kind of at odds with ES6 or commonjs modules.

      Directives are about the only worthwhile feature remaining but the rest needed a total redesign hence Angular 2. React JS is much better and if Web Components gains browser support it would be great too. Not sure I want to invest any more time in a framework that it's own creators don't even bother using very much.

    3. Re:They should call it !Angular by Anonymous Coward · · Score: 0

      Angular has always tried to bill itself as a nextgen technology. The future of HTML and the future of JS.
      However the future of JS is typescript. This solves ALOT of the problems that Angular solved, but solves them differently. In truth Angular looks to me like ECMAScript v6 with 2 way data binding and some tools to make templating easier.

      I used Angular 1 for as far back as it's been a real product. I don't like this new syntax, but I do like what it brings to the table.
      You can't allow yourself to be an oldschool curmudgeon and expect to remain relevant in this space.
      You're going to need to get used to this stuff if you wish to remain relevant and employed in the industry.
      It's what's new and what's next. If you don't like it you really need to get involved and change the bits you don't like.

    4. Re:They should call it !Angular by Anonymous Coward · · Score: 0

      Was it *really* necessary to make fundamental changes to the syntax, thereby making it completely incompatible with Angular 1? It's dishonest to even call it Angular 2, when it has almost nothing in common with the previous.

      Angular is a Google project, which means it's "as-is", subject to change at the drop of a hat and backwards compatibility is out the window. I don't use projects and frameworks from Google for that reason, among others. I'd rather not make my production code dependent upon their hobby projects.

    5. Re:They should call it !Angular by ilsaloving · · Score: 2

      The core language was stable, but because they didn't differentiate between the language and the support libraries, it basically amounted to them continually 'changing' java. Java now has a bajillion different ways of doing the same things. There are multiple windowing toolkits (AWT, Swing, etc), and don't get me started about server side stuff. JSP. Faces. It's ridiculous, and makes it unnecessarily difficult for people to get into java development cause there are too many equally valid sub-technologies to learn, and many (bad) projects may even mix and match between them.

    6. Re:They should call it !Angular by Anonymous Coward · · Score: 0

      You're going to need to get used to this stuff if you wish to remain relevant and employed in the industry.
      It's what's new and what's next. If you don't like it you really need to get involved and change the bits you don't like.

      What's new is not necessarily what's next. That's actually a big part of the problem. Constantly creating new tools and then dumping support for them and moving on to something else, with complete disregard of the hundreds of hours a developer has devoted on mastering them.

      You can stay relevant without trying to figure out how to leverage the framework-of-the-month. You have to figure out on which tools you need to invest your efforts. That is not an easy thing to do, but it's a lot easier and less expensive in the long run than the alternative (the alternative being perpetually trying to catch up with every new thing that comes along, and constantly wasting your time shifting to something else).

  10. So when will this majority switch exactly? by roman_mir · · Score: 4, Insightful

    I don't see how it is possible to have the majority switch to anything from their existing code base. I predict a gigantic fail for this plan of switching people from AngularJS 1 to AngularJS 2 in a year. It's nonsense.

    Let me explain something to Google here: vast majority of projects will not be rewritten with AngularJS 2, if they have AngularJS 1 as the code base, they will stay AngularJS 1 and will continue being developed as AngularJS 1. It takes MONEY to switch from one framework to another, money that most projects already spent on design, development, testing and releasing into production in the first place.

    1. Re:So when will this majority switch exactly? by Anonymous Coward · · Score: 1

      It's going to be python2/python3 all over again.

    2. Re:So when will this majority switch exactly? by Anonymous Coward · · Score: 0

      vast majority of projects will not be rewritten with AngularJS 2, if they have AngularJS 1 as the code base, they will stay AngularJS 1 and will continue being developed as AngularJS 1. It takes MONEY to switch from one framework to another, money that most projects already spent on design, development, testing and releasing into production in the first place.

      Google stops supporting AngularJS 1 and your production code is now dependent upon abandonware that's no longer supported. Eventually it's hard to find anyone who's heard of or still works in AngularJS 1 and maybe then you learn a valuable lesson about integrating Google projects into your production code.

  11. Still supporting by Anonymous Coward · · Score: 0

    Oh good, they are still supporting Angular 1 for a few more months, which isn't compatible with Angular 2. Then they will come out with Angular 3. Why do people continue to depend on these throwaway frameworks and languages like Swift and Rust? They aren't worth the investment of your time as they end up getting thrown into the bin in a couple of years.

  12. Ugh... by Anonymous Coward · · Score: 0

    you know, at one time I thought hey, this toolkit might be something worth taking a look at until I saw people using it. Imagine what happens when J2EE developers(inept ones) try to code web front ends. Goddam templating tags everywhere. They had a "mysterious" web page that they didn't know where it came from and didn't even know what the console was for. So yeah, that launch was delayed a quite a bit. Stay away from it. Keep your team off of it. I'm even going as far to say that i'm not going to hire anyone with it on their resume, ever. period.

  13. React by irrational_design · · Score: 2

    I've never used Angular or React, but I keep up with the JavaScript news and from everything I've read over the last year many developers have moved from Angular to React. My gut feeling is that Angular 2 will be too little too late. Or maybe that is too much too late since many developers seem to be moving away from monolithic frameworks like Angular to using best in class libraries (which many consider React to be). Only time will tell I suppose.

    1. Re:React by Anonymous Coward · · Score: 0

      Equally as valid, I know of no one making a move from Angular to React. Nothing wrong with React but what Angular does it just does so much better and cleaner than React can. I've never seen any use case for react that isn't handled better by Angular.

    2. Re:React by clenhart · · Score: 1

      The difference between Angular and React is that Angular is code in an HTML document and React is HTML in a JS file. So Angular favors designers who do little or no JS coding. React requires everyone to code JS.

      It's a team skillset question, rather than which is superior.

    3. Re:React by Anonymous Coward · · Score: 0

      many developers seem to be moving away from monolithic frameworks like Angular to using best in class libraries (which many consider React to be). Only time will tell I suppose.

      This isn't true.

      One thing using Angular has done for developers is make it easy to transfer knowledge.

      If developers used random libraries to build websites, every job you take would require having to learn an assortment of libraries of varying quality and design, and that's not easy or fun. If you haven't noticed, developers change jobs fairly often these days. Angular has allowed many developers to work on many projects without having to re-learn or re-invent the wheel. It allows developers to get up to speed quickly and be productive right away. I'd really not like to have to go back to using random libraries from job to job.

    4. Re:React by phantomfive · · Score: 1

      Angular = Google, Microsoft and friends.
      React = Facebook and friends.

      Both platforms are going to be around for while, like J2EE.

      --
      "First they came for the slanderers and i said nothing."
    5. Re:React by phantomfive · · Score: 1

      I'm not sure that's accurate. My team was using Angular, and there was a lot of Javascript all over the place, to the point that it felt like all Javascript. Maybe other teams use it differently, though.

      --
      "First they came for the slanderers and i said nothing."
    6. Re:React by Anonymous Coward · · Score: 0

      Actually J2EE is JEE and has been for almost 10 years.

    7. Re:React by Beezlebub33 · · Score: 1

      Agreed. We use Angular 1, and it's all javascript, all the time. Shameless plug: it's a composable dashboard with a widget library; you can see it here

      --
      The more people I meet, the better I like my dog.
    8. Re:React by phantomfive · · Score: 1

      That's pretty cool. I notice it gets weird when I shrink the screen, might I suggest giving it a "responsive" design?

      --
      "First they came for the slanderers and i said nothing."
  14. Long term support by manu0601 · · Score: 1

    Angular 1 for at least another year, until a majority of users have transitioned to the new syntax

    Who wants to code on an API that has precedent of being broken so quickly? This is the promise of either redo the same thing every coupe of years, or forget about security updates.

  15. What will the Cool Kids use? by Required+Snark · · Score: 2
    When it comes to web stuff I see a lot of fad driven behavior, i.e. new=cool=good.

    I have also been trying to choose between React and Angular for my next web effort. Without any clear release schedule for Angular 2, it seemed a tossup. Now that I've found out how far along it is the only rational choice is Angular 2.

    So Google has 231 confirmed contributes for Angular 2, and React has how many? Does anyone actually know? And since Google will be shifting resources from Angular 1 to Angular 2, it's clear that Angular 2 will be very well supported in the future. What kind of guarantee is there that React will get the same level of support that Google will provide in the next three years?

    If you RTFA, you'll notice that Google is using it internally for CRM and will be testing it in public with weather.com. Google is not infallible, but they do have skin in the game as far as their reputation is concerned. It will be solid and the roll out will be on time.

    So for an organization of any size that depends on it's web presence, do you think they will go with Google or with Brand X? At some level, it doesn't make any difference if Brand X is better. And once the network effect kicks in, Angular 2 will dominate. The race has already been decided.

    It seems like React is the Cool Kids choice. It's New! Of course, there is a cost associated with new stuff, because it is not wrung out yet. But being ahead of the curve is a powerful inducement for a lot of people.

    The fact that Google re-architected Angular means that they took the lessons they learned the first time and made it better. Somehow that is not cool, even though it is good engineering practice.

    As for whining about changing the API, grow up. When the choice is a syntax change vs a completely different system, which is the better investment? There is the cool answer, and then there is the right answer.

    Arguing that so many people use Angular 1 that Angular 2 will be dead in the water is foolish. When Google ends support for version 1, do you think that the internet hoards will leap into action and take over maintenance and development? Or is it more likely that there will be a well defined process to move from 1 to 2, and 2 will become the de facto standard?

    If you want to use React, great. It might be the future. However if you are interested in having a known quantity with good support and large user community, Angular 2 will meet your expectations. Even if it is not cool.

    --
    Why is Snark Required?
    1. Re:What will the Cool Kids use? by Anonymous Coward · · Score: 0

      I would caution backing Angular just because Google has developers working on it. Do you remember the Google Web Toolkit? A company I worked for decided to adopt GWT since 1) it had Google's backing and 2) they could just hire Java developers to write the Web apps. Needless to say, Google dropped GWT like 3rd period French, along with projects sent to the graveyard. And now they have a bunch of projects no sane developer wants to work on.

      For what it's worth, my biggest problem with Angular 2 is that TypeScript is being used, rather than plain-old JavaScript. While JS might not be the best, it is native to the browser. And after having to deal with a Java -> JavaScript translation, I don't really want to deal with a TypeScript -> JavaScript transpiler.

    2. Re:What will the Cool Kids use? by irrational_design · · Score: 1

      Brand X? React is developed by Facebook. And unlike Google, Facebook actually uses React extensively.

  16. So when will we ever see useful results? by WaffleMonster · · Score: 1

    When will websites be more functional? When will they be faster and less riddled with glitches? I see an increasing number and variety of fancy "loading" dialogues someone somewhere must have spent a lot of time on but never a logical explanation of why I should have to wait in the first place for seemingly superficial reasons (loading cesspools of JavaScript frameworks) or why navigation is so painful (moar round trips!!) with browsers stuttering to keep up and basic navigational elements (back, forward) no longer operative.

    Over the past few years my experience as a user has gotten worse not better.

    Where's the pudding?

    1. Re:So when will we ever see useful results? by Anonymous Coward · · Score: 1

      I too wonder what happened to the idea of the actual content being in the HTML delivered and addressable by an URL, the optics being in CSS (and resources linked from that, see http://www.csszengarden.com) and scripts to make interaction with the content smoother (but purely being optional) ?

    2. Re:So when will we ever see useful results? by Anonymous Coward · · Score: 0

      Well, obviously Google keeps thinking that what they have done in the past is completely "Wrong! Do it again!" Not just for Angular. Makes it quite risky to invest my time in learning to use their tools.

      As for your last question, if you don't eat yer meat, you can't have any pudding! How can you have any pudding if you don't eat yer meat?

  17. Re: JAVA? by Anonymous Coward · · Score: 2, Funny

    You are on slashdot. Odds are he's technically illiterate but thinks he's really in the know because he "hacks on linux".

  18. I don't get it by MichaelSmith · · Score: 1

    I am just wrapping up a project with django+python on the back end, and angular on the front end. Works fine right now.

  19. backwards compatible by Anonymous Coward · · Score: 0

    Obviously a phrase unknown to Google. Just keep breaking stuff to "make it better."

  20. Re: JAVA? by Anonymous Coward · · Score: 0

    Oregon seens to be thinking about about making k-12 kids learn java. Maybe thinking is the wrong word.

  21. 1.3m Angular 1 devs by aegarland · · Score: 1

    Bad typo there, the linked story says 1.3 million not 21.3 Also, it is an odd way to count, based on monthly unique visitors.

  22. python by sad_ · · Score: 1

    i hope they do better then python, the switch to python 3 is still going on, with so many people staying on python 2 because module x & y don't work yet on 3.
    If they can pull it off, perhaps the python community can learn from it and clean up the current mess they have on their hands.

    --
    On a long enough timeline, the survival rate for everyone drops to zero.
  23. Good job by kiz36 · · Score: 1

    Good job