Those names are well supported by editors and enable syntax highlighting. If we named them anything else it wouldn't work without extras tools.
Those names are well supported by editors and enable syntax highlighting. If we named them anything else it wouldn't work without extras tools.
One of my primary criteria in choosing a technology to work with its how accessible is community support, documentation, third party articles and writing.
It had better be a compelling technology that names its main things exactly the same as the biggest concepts in web development, thereby making it a battle to resolve questions and issues and adding unnecessary confusion.
I do use a nodejs library called "Postgres" which provides a Postgres SQL driver but I really hate the fact that searching for documentation/issues is essentially impossible. I use it because I feel I had no choice, it's the best possible technical solution.
Names matter.
Searchability matters a huge amount.
Template literals are just a feature of javascript, it's not even anything that bespoke. That's why it's called "lit". The output of those tag functions are just rendered with standard DOM features too.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
Did you see a code snippet and want to learn more?
`html` and `css` are just functions we vend. They're important ones, but two among many. The names need to be short and intuitive so that when you see something like:
html`<p>Hello world</p>`
both the developer and tools know what to expect of the string content. Naming them something unique would really harm readability, IMO.