The old browsers are holding back progress and supporting them consumes enormous amounts of time and effort better spent on new development. Please let them die, just put a Chrome install link on your web site.
For internal/Intranet type of web applications it is even easier, as you can just say that your application platform is Chrome. One of our customers went all "nervous" on us about not supporting IE8 as this is their "browser standard". To that we replied with two facts: - We could have developed it as a Winforms application and we know that they would have accepted that, so what's the difference? - Chrome can coexist with another browser and also supports Enterprise environments. That was the end of that discussion. On Saturday, June 28, 2014 6:48:32 AM UTC-4, [email protected] wrote: > > *Polymer is amazing! (but you probably know this)* > Polymer and Material Design was one of the most exciting things I have > since in a while! > > I really liked the idea you could build apps with UI standards for Native > device also across the web -- these days so many people think that the web > is dead: because Apps are dominating in Mobile and Mobile is quickly > dominating the web. > I also especially liked transitions/animations which I think is the next > paradigm and really can improve UX. The whole Material Design is amazing. > Really really really amazing! I found myself watching as many videos as > possible on Polymer and Material Design and there are now quite a few! > > *Browser compatibility: will Polymer be usable in the next 3 years?* > But the one big BIG disappointment is browser compatibility. I was > disappointed when I say the compatibility guidelines: > http://www.polymer-project.org/resources/compatibility.html > But somehow I couldn't beleive it and I just hoped it somehow degraded > nicely on older browser. I was very disappointed when I found it really > doesn't degrade beautifully at all on things like Safari 5 or IE9. It just > completely falls appart. Apparently even Android web-view in some cases > Polymer will completely break. > > So everything that was exciting about it especially being cross-device > suddenly looked very over-stated at best. I mean we are all still hoping we > can finally put IE6 behind us... So Safari 5, IE10, or older versions of > Chrome & Firefox: that's at least 3 to 5 years *at best*! > > I am surprised more efforts were not put to help adopting Polymer by > creating a smoother transition by having ways to degrade Polymer > beautifully on older browsers. Even if that meant loosing the benefits of > Polymer for any of these Browsers. > Have I missed something? Is there a way to degrade beautiful Polymer to > support the majority of browsers? Will browser compatibility improve: is > that somewhere on the near future of the product roadmap? > > Note: Attaching screenshot of Polymer demo running on Safari > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/261a46aa-5b6e-4854-9394-2028aceb871f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
