Become a fan of Slashdot on Facebook


Forgot your password?
Google Java Microsoft Open Source Python News Technology

Google Says Angular 2 Will Support Python, Java ( 92

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.
This discussion has been archived. No new comments can be posted.

Google Says Angular 2 Will Support Python, Java

Comments Filter:
  • by Ralph Siegler ( 3506871 ) on Wednesday March 02, 2016 @05:56PM (#51624919)
    no one values a stable web platform any more? they have to use lastest fad thing?
    • by xxxJonBoyxxx ( 565205 ) on Wednesday March 02, 2016 @06:02PM (#51624949)
      >> 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?
      • 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.

      • by Zalbik ( 308903 )

        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?

    • no one values a stable web platform any more?

      There has never been a stable web platform for frontend.

      • Yes, it's called HTML.
        • 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.......
        • 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,
  • by MobileTatsu-NJG ( 946591 ) on Wednesday March 02, 2016 @06:03PM (#51624955)

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

  • Front end? (Score:5, Interesting)

    by roninmagus ( 721889 ) on Wednesday March 02, 2016 @06:07PM (#51624983)
    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.
    • 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?)
    • by Luthair ( 847766 )
      I'm guessing precompiled templates. (e.g. for a search engine)
    • Re:Front end? (Score:5, Interesting)

      by Anonymous Coward on Wednesday March 02, 2016 @06:59PM (#51625327)

      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.

      • Wait, what? You're saying that if I went to [] Directly I'd get the exact same HTML rendered out as if I'd gone to [] 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

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

    • Perhaps they aren't referring to the backend, but the language that one would use before compiling?
  • 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...

  • by ilsaloving ( 1534307 ) on Wednesday March 02, 2016 @06:46PM (#51625227)

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

  • by roman_mir ( 125474 ) on Wednesday March 02, 2016 @06:53PM (#51625287) Homepage Journal

    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.

    • by Anonymous Coward

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

  • by irrational_design ( 1895848 ) on Wednesday March 02, 2016 @08:32PM (#51625865)

    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.

    • 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 th

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

      • 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.
        • 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 []
    • Angular = Google, Microsoft and friends.
      React = Facebook and friends.

      Both platforms are going to be around for while, like J2EE.
  • 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.

  • 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)

    • by Anonymous Coward

      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 and scripts to make interaction with the content smoother (but purely being optional) ?

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

  • 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.
  • by sad_ ( 7868 )

    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.

  • Good job

Beware of Programmers who carry screwdrivers. -- Leonard Brandwein