I've run into this question several times recently when trying to convince various clients to use web components and Polymer. The issue is that most businesses considering depending on a platform for real business use will need a more substantial commitment than, "Use it when you feel it's ready." People want to know when *Google* thinks it's ready for business use. (While the examples of Polymer apps out there are interesting, AFAIK, no one's bottom line currently depends on Polymer.) As you suggest, few dev leads/CTOs are going to be able to justify why they're using something that says "pre-alpha" and version 0.1.2.
Alex: I think it'd be great if Google could shoot for announcing that Polymer has reached 1.0 at Google I/O this year. Or, if not then, then to at least publish a roadmap to 1.0. That would be a huge help in promoting this to clients. On Thursday, January 16, 2014 8:12:23 AM UTC-8, Bobby Powers wrote: > > Hello, > > Alex Komoroske wrote: > > Work is progressing at a very fast pace in Blink to ship HTML Imports, > > Shadow DOM, and Custom Elements in the next few months. Custom Elements, > for > > example, is on track to ship in the next version of Chrome stable. Once > > those technologies ship, it will give me, personally, a lot more > confidence. > > It is great to hear that the timeframe for shipping/enabling HTML > Imports, Shadow DOM and Custom Elements in Chrome is on the order of > months rather than a year+. > > yours, > Bobby > 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/10e43aad-c2cd-4600-8aad-354510418b77%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
