Polymer 0.8 prototype

[jonatha...@gmail.com]

Hi Polymer team,

I'm starting to write a quick prototype using Polymer 0.8-preview.  Nothing fancy or long-lived; I'm porting my previous startup's UI to Polymer to see how emerging web technologies might've changed its development (and will likely do the same with React just to get a sense of the competition).  In the process, I've come across over a dozen "bugs".  I have that in quotes because they aren't bugs as in "this doesn't work as specced" (in general, everything seems to be pretty in-sync with the Primer), but rather bugs where "my expectations as a user were violated" or "this combination of features from the Primer results in odd results when I combine them" or just "I tried this and it didn't work".

Should I report these as I run into them, as issues against the Polymer/polymer project?  Or should I hold onto them and report them if they're still not fixed when 0.8 officially launches?  Also, are folks interested in general impressions/opinions about working with Polymer to build an app?

- Jonathan

[AJ Ortega]

It would certainly be valuable if you filed them against Polymer/polymer. The team is currently working on processing a lot of internal feedback, so the bugs may or may not get attention until later in the development cycle, but it'd be unfortunate to lose potentially useful information.

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/9a573b5f-1712-4ea3-82f8-699964e134e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

AJ Ortega | Software Engineer | a...@google.com | 626-872-5064 

[Taylor Savage]

+1 to AJ's response, it would be great to capture the feedback as GH issues along with your reasoning, with the only caveat that it might be addressed post-0.8 as we're trying to get 0.8 out there in a complete, usable form ASAP. We've been developing 0.8-preview out in the open for this exact purpose, at the risk of some early FUD cropping up based on experimental, not-yet-ready-for-prime-time features being public - I think the tradeoff is absolutely worth it.  The road from 0.8 to 1.0 will be critically important in getting the rough edges ironed out and to get the right balance of tradeoffs, so feedback and PR's will be crucial and very welcome!

The team also takes feedback really, really seriously - we've been known to spend days pouring over the relative merits of a single tweet - so use-cases, usage data, and of course PR's go a very long way.

Really appreciate the note - would love to hear more about your experiences so far.

Taylor

To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAKf8-xg04nMMeGAQhSi4F0UKPwF_aEqS2JqyQL-iJJ5vyCqhdQ%40mail.gmail.com.

[Rob Dodson]

Btw, if you prefix your issue with "[0.8]" it will help us triage

To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAN-z2fuoDkPq4gn99jJXzK%3Do5c0w3_wWqF7NOn0TsSfmFs8msg%40mail.gmail.com.

[Scott Miles]

Hi Jonathan,

Sorry for the late reply. 

I'm very much interested in your feedback, especially around the 'bug-not-bug-gray-areas' you mentioned. I'd be grateful to receive said feedback in whatever form is most convenient for you, including direct emails to me. 

Any information you can supply is top priority from my perspective, since I'm mainly responsible for the product gestalt, and as I value your opinion so highly.

Regards,

Scott

On Fri, Mar 6, 2015 at 12:21 PM, <jonatha...@gmail.com> wrote:

Follow Polymer on Google+: plus.google.com/107187849809354688692