Hey Joern, Although you have valid points, I'm afraid your message may not get much visibility on this thread. I believe your comments may be better served on the pull request that officially introduces Polymer 3 to the world here: https://github.com/Polymer/project/pull/46. There was also another discussion on that same polymer github repository, but I can't find it at the moment.
Good luck, and I'm sorry the Polymer future has disappointed you :( On Mon, May 14, 2018 at 11:04 AM Joern Turner <[email protected]> wrote: > First of all - congrats to the new release. > > I'd like to thank for the marvelous work of the Polymer team during the > last years. > > I've complained here before and i know that's it's not the right address > but i hope that somehow these words find the way into the discussions > elsewhere: > > when i consider Polymer 3 i mainly see a huge paradigm shift - and - > sorry to say that - for me personally i don' t like it. Maybe my > understanding of a > Web Component was blurred by my personal wishes but i my view a Web > Component is a custom-element with behavior and styling. This has been true > before Polymer 3 - > we had a single file containing a component with all their parts in a > natural representation - HTML being HTML, CSS being CSS and JS ... you got > it. > > Now JS has taken over and a lot of the initial charme has gone - what > about 'there is an element...' idea? Instead this has been eaten by (i > guess) performance and efficiency > considerations that push ES6 in front. Now we end up with the maybe more > efficient but awful template literals that are a big productivity drawback > - my IDE does not support syntax coloring, > pretty-printing and inspection inside of literals. > > That much for the architectural view but IMHO this is a major stepback. > I'm aware that the Polymer templating was an extra given on-top > but i heavily used (and will use) Polymer 2 for exactly that reason. It > feels good and natural to work that way - defining an element as what it > is: an element and using that as a container of all its aspects. > > At this very moment i don't see much reason to switch to Polymer 3 - i > have pure ES6-style Polymer 2 applications running and i guess i'll > continue on that track until hopefully there'll come a better solution > that somehow allows for descriptive templates again. Sorry - LitElement > doesn't look like a future friend of mine. > > Again - i'm aware that the Polymer team is somehow bound to follow the > development of the specs - i've been there myself before and in my > experience not every decision of standards commitees are right. > > Sorry for the somehow negative criticism but i'm a enthusiastic user of > Web Components and Polymer and i have a position to defend inside of our > small company. > > Thanks for listening, > > 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/f757bc87-bad2-4ced-8f71-90d5dfe21913%40googlegroups.com > <https://groups.google.com/d/msgid/polymer-dev/f757bc87-bad2-4ced-8f71-90d5dfe21913%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- mark 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/CAFfkm%3DJLRA6AsECnYMCXgdXO0o8PwX4m9QAcwHXn%3D1jn9JkEFw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
