Framework Comparisons Guide does not reflect recent changes in Polymer

[KenCarroll]

The Framework Comparison page can be important in helping decision making.

For example I've been using Polymer 2.0. The recent move to Polymer 3.0 and lit-html has provided an opportunity to take a fresh look at the options. Vue being one of them :-)

But the current comparison seems dated - for example it references Polymer 1.0.

Updating the frameworks page to compare Polymer (3.0 and lit-html) can help decision making. When I see the outdated comparison it does not help me in re-evaluate the Vue solution.

Thanks.
Ken

[chrisvfritz]

Thanks! We're definitely happy to update this to reflect any changes that have been made to Polymer. 🙂 Besides the reference to 1.0, what have you noticed that no longer applies or should be added?

[jsilvermist]

Polymer custom elements are authored in HTML files

Polymer 3 elements are written in JavaScript files.

Polymer recommends loading everything on-the-fly with HTML Imports

Polymer 3 elements use the import syntax from ES Modules.

you will have to use a special tool called Vulcanizer to bundle your Polymer elements

This has long been changed to be the Polymer CLI, and you can also use webpack or any other tool which fits your project.

[chrisvfritz]

Thanks! I just updated this, mostly just removing anything that's no longer true. 🙂 Let me know what you think.

[0polar]

Polymer is deprecated, but the beat part:

• component interface design (prop, event, slot)
• single file HTML template
• 2-way data binding
• behavior (mixin)

will long live in Vue