Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why this? #1

Open
trusktr opened this issue Aug 5, 2018 · 2 comments
Open

Why this? #1

trusktr opened this issue Aug 5, 2018 · 2 comments

Comments

@trusktr
Copy link

trusktr commented Aug 5, 2018

For example, there's other ways to create DOM with template-like functionality (f.e. Handlebars, Angular, React, Vue, etc). Why would you like to use this over the others? Is it mostly just because it's easy for small projects / prototyping?

@trusktr
Copy link
Author

trusktr commented Aug 5, 2018

Check out this new proposal I just stumbled on, effectively "template syntax" for <template> elements: https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Template-Instantiation.md

If this feature lands in browsers, it would effectively provide everything entities.js provides, but in a more robust way without relying on strictly on global scope. It would be further possible to implement an entities-like syntax for template elements.

@madmurphy
Copy link
Owner

Hi @trusktr ! Thank you for your message.

If I am not wrong the <template> element already landed in Firefox long ago, but I do not see how it might improve my entities.js. Any example?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants