Giving up on polymer. Is there something I should know?

[Anique Tahir]

https://www.pvp.guru/bank

Works well on the latest version of chrome. Fails at something or the other in just about everything else. I know its still in developer preview but its just too ... bad compared to something like angularjs or React.
One of the things that I have noticed is that you have to write comparatively a lot more code for small web apps.
Since its going to be designed for evergreen browsers only, you're losing half of your userbase from the start. Its diverting the focus away from building a robust and functional web app. That is my first impression. I would love to know where im wrong?

[Scott Miles]

On Wed, Dec 17, 2014 at 1:47 PM, Anique Tahir <aniqu...@gmail.com> wrote:

https://www.pvp.guru/bank

 

Works well on the latest version of chrome. Fails at something or the other in just about everything else.

We are working with evolving new web-standards. That aspect by itself creates an imperfect surface across browsers which have varying levels of standards support. 

 

I know its still in developer preview but its just too ... bad compared to something like angularjs or React.

You answered your own q

 

One of the things that I have noticed is that you have to write comparatively a lot more code for small web apps.
Since its going to be designed for evergreen browsers only, you're losing half of your userbase from the start. Its diverting the focus away from building a robust and functional web app. That is my first impression. I would love to know where im wrong?

Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/360cba48-51db-484a-9f07-aa26114faa40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Scott Miles]

Sorry, send fail on that last one.

On Wed, Dec 17, 2014 at 1:47 PM, Anique Tahir <aniqu...@gmail.com> wrote:

https://www.pvp.guru/bank

Works well on the latest version of chrome. Fails at something or the other in just about everything else.

We are working with evolving new web-standards. That aspect by itself creates an imperfect surface across browsers which have varying levels of standards support. 

 

I know its still in developer preview but its just too ... bad compared to something like angularjs or React.

You answered your own question there.

 

One of the things that I have noticed is that you have to write comparatively a lot more code for small web apps.

I believe this is not generally true. We'd have to discuss it more specifically however.

Since its going to be designed for evergreen browsers only, you're losing half of your userbase from the start. Its diverting the focus away from building a robust and functional web app.

That's a trade-off we are making for mindshare, no argument there. Can you explain how it "diverts focus" from building robust apps?

[Aleks Totic]

Just took a brief look at your code. Written like that, Polymer is not a good fit.

If you took full advantage of the platform, it'd be a lot smaller, and easier to write:

- use core-xhr instead of raw xmlhttprequest

- use polymer computed properties instead of writing getter//setter.

Right now, there is no "Polymer patterns" book, and figuring all this out requires multiple readings of the succinct documentation, and existing code.

Css and shadow dom do cause layout problems, but they are always fixable with css selector tweaks. Personally, I am happy to give up some cross-platform compatibility for ShadowDOM encapsulation.

Aleks