[ilaksh]

If you can't use Web Components (Polymer) then Angular is the next best thing. I think you should really try to use Web Components though if you can get away with it.

IMHO Angular is overly complicated once you try to dig in, for example to make your own HTML elements.

Building custom elements with Web Components/Polymer is the next step, along with promoting web components/polymer and working on getting compatibility in user's browsers.

People say its not ready for mainstream, which is true. _However_, if we all start taking Polymer/Web Components seriously, pretty quickly it _will_ be ready, i.e. it will work in new releases of Firefox, Chrome and probably Safari. And even IE 10 and 11. We just need people to start seriously trying to take advantage of it, patching things and pushing for compatibility/stability/adoption.

And someone might say something like "I think you are confused about what Angular and Web Components do.. blah Angular is going to take advantage of Web Components in the near future". So let me save you the lecture.

I have used Angular in 3 or 4 projects. I know what it does. I know it is going to use Web Components in the future.

But like I said, its too complicated. And most, if not all, of the things that you would do with Angular with/without using custom elements, you can take advantage of Polymer/Web Components features to do. And it will be much simpler to code and maintain, and not particular to any overall framework.

So as far as I'm concerned Angular is superfluous at this point, and a liability, if I am not constrained by immediately shitty browser realities.

If there is something that Angular does that can't be implemented with Web Components/Polymer, please let me know.

[AdrianRossouw]

Have you seen this presentation the [1] angular devs gave? A lot of the concepts are pretty analogous to each other, and I think they will possibly start moving towards that standard.

Not soon though, that is up to browser makers.

Angular is close enough tot he general idea though, that I think it's proving the approach is valid to an entire generation of devs. Devs who would never have known about web components if angular wasn't legitimising it.

[1] https://docs.google.com/presentation/d/1Gv-dvU-yy6WY7SiNJ9QR...

[ilaksh]

OK thanks, no I have not seen that.

What is left for Angular to do? Really would like to know the answer to that.

If they are serious about helping move the web forward, they will just change the Angular logo to the Polymer logo and start pushing to make that work. And stop saying things like browsers aren't ready.

Polymer works in new versions of Firefox, Chrome and IE. We don't need a new version of Angular.

If someone thinks we need to keep using Angular, give me a reason. That presentation on Google Docs that is linked in the parent just shows reasons for Angular to go away.

[AdrianRossouw]

they aren't ready. the standards aren't even ready for polymer to polyfill for the browsers to implement.

you need to be patient. open platforms are a very long term play.

i saw they reviewed a few of the polyfills for 2.0 inclusion, and there wasn't a lot that was really capable of being used yet, for a variety of reason.

I believe open platforms will win eventually, but it's not going to be tomorrow. it will be maybe 5-10 years from now. Just be glad there's movement.

[ilaksh]

10 years from now, we may not even be relevant as a species. I'm not kidding. Its unlikely it will happen that soon, but I actually believe that we will have super-intelligent AI within 4 decades at the latest. I think it is entirely within the realm of possibility for that to happen within 10 or 15 years.

I am looking at next year or maybe the year after that to see a massive surge in popularity and use of Polymer.

[Bahamut]

Polymer is also currently over 500 KB total. We are still a while away from Polymer being ready. It has been in alpha for almost a year now.