Joern, There are various 'slack' channels for polymer-related discussions. Here is one related to polymer 3.0. https://polymer.slack.com/messages/C6SLBGSHJ/details/ ... perhaps some of the core developers might be more responsive on there.
Good luck, Colum On Monday, September 11, 2017 at 2:04:54 PM UTC+1, Joern Turner wrote: > > Really? Nobody? > > Is this the wrong place to ask/discuss design questions or am i asking too > much at once? Nobody else concerned about such questions? I would be really > thankful if anybody could point me to the right location to ask such > questions. > > Again - i'm an enthusiastic user of Polymer 2 and do quite a lot of > applications with it but i'd like to learn about where actually Polymer > project is heading and to unserstand the choices. Otherwise it's getting > very hard to commit to it and to see if it's still a fit to my needs. > > Any comments welcome. > > -Joern > > Am Freitag, 8. September 2017 13:17:12 UTC+2 schrieb Joern Turner: >> >> Hi, >> >> just read the blog article " >> Hands-on with the Polymer 3.0 preview" >> To start with: i'm a huge fan of Polymer and trying to push it whereever >> i can in our projects. I appreciate the hard work of all developers of that >> fantastic project. >> >> >> In that light please allow me some criticism: >> >> >> Seems that Polymer 3 is bringing another toolchain with it again (yarn). >> Polymer tools are fine and you want them for productivity. I'm not opposed >> to learn new things when they bring significant value. However having to >> learn a new way of doing things with every major release is also a burden >> for each Polymer user that doesn't eat every newest tool for breakfast. - >> would be great if you guys give it a thought next time. >> >> But now for the important things: >> >> >> i can live with the removal of link imports though i personally liked >> them but another syntax does equally well here. >> >> >> But i'm kind of shocked by the prospect that Polymer 3 seems to drop >> declarative templates in favor of string jungle. Imagining to build >> complex templates as strings gives me a shiver and makes me doubt about all >> the work i put into Polymer 2 apps now. >> >> >> IMO HTML templates are one major selling point for me to work with >> Polymer (and to convince others of the innovation Polymer brings). I don't >> want to imagine bulding complex templates with strings. >> >> >> Furthermore - turning the representation into a pure javascript one does >> harm the component metaphor IMHO. A compoment (of course my view of things) >> is built on-top of a custom HTML Element. As such it's natural that a web >> component is a html snippet. I always especially liked that about Polymer. >> And wasn't there something like "everything is an element" slogan? Is that >> deprecated? Sorry but representing an element as a ES6 module doesn't feel >> like the 'next generation' but more like 'yet another JS framework'. >> Always speaking for myself - but this is a big step backward. >> >> >> >> Sorry if my complaint directs in the wrong direction - i don't follow the >> W3C Web Component group, Apologies in that case. >> >> >> As i doubt that my personal opinion will influence the flow of things >> here's my question: will there be any way to work with declarative >> templates in the longer term? Maybe as an option? >> >> >> What about CSS and ES6 modules? No example of that in the blog post? >> >> >> Lots of questions and complaints i know but i would really appreciate >> your opinions/comments. >> >> >> Joern >> > 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/b095f1a6-5207-453b-b988-b755780ee29b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
