First of all, I ’m sorry for the technical question.
It will be the same as the title,
The template engine for writing HTML, "Pug",
Are you going to be a required skill in the future?
For non-engineers (sales, designers)
"'Pug' is a bad thing" (meaning good = good)
"If i am an engineer, you should n’t hate hair, you ’ll be late for the convenience of the world."
My situation is that only the server side is in charge,
I haven't written HTML for about 4 years.
But I still have the skills to write HTML directly.
However, the evolution of HTML and CSS over the past few years is not known, and even now, it is a fact that it is faster to write HTML directly.
I would like to hear the opinions of those who are familiar with HTML and who are actively introducing Pug.
Answer # 1
No one knows the future.
Answer # 2
Pug has been known since the Jade era, but I think that only some people will use it in the future.
I think the format for creating HTML with indentation started with Haml (if you have an older version, please let me know). At that time, when Ruby on Rails began to become popular, embedding HTML tags like PHP in the past with ERB was painful, and it was a thing that responded to the demand to make it easier to write. Although Haml has received a lot of attention (in the Rails area), it is still redundant, so Slim was created to make Haml easier to write, and gained some status (in the Rails area).
Now there are two kinds of lazy people in programmers. People who do not neglect learning because they are too lazy to write code. People who have neglected to learn and the code can be redundant. There are many companies that don't pay for self-learning but pay for the time spent coding, so the latter are overwhelming. And for the latter people, remembering grammar different from HTML like Haml, Slim, Pug was "no money" and didn't try to remember.
In the case of development with one small person or a very small number of people, it is okay because the former people can prepare development staff, but the latter people will surely enter when the scale increases. They are also cheaper than the former (and they don't realize the fact). If that happens, you will not be able to adopt something new to remember, such as Pug, in development.
Most famous large-scale Rails apps (such as Redmine) use ERB instead of Haml and Slim (I thought Mastodon was Haml, which is an exception). This is the situation even in the Ralis neighborhood where Hamml, who adopted the indent method for the first time, was born. I can't help saying anything else.
In the end, most people only do what they know now, or something similar, than the better. The reason why SCSS format is more mainstream than SASS format in Sass, and why CoffeeScript is abolished is the same place. And in the end, I think Pug will only stay alive without being used by some other mania (including myself).
Answer # 3
I don't use it at least at my site.
Well, it's time, case and purpose.
- html : When the screen width increases, the layout goes to the left, but it needs to be in the middle, how can you fix it?
- html - how to check the display on a high resolution screen
- html - i want to unify the image size with css, but it sticks out
- html - i want to save with vscode open half-width
- i want to resolve a php error syntax error, unexpected end of file
- html - bootstrap container doesn't work (padding doesn't work)
- html - windowonload event works or doesn't work with webpack commands
- html - if you click it, class will turn on, and if you click it again, it will turn off
- html - in nuxtjs, i want to dynamically change the query parameter of the href url when transitioning from the list screen to th
- html - i want to show/hide a large range with tabs