The two are roughly equivalent in terms of functionality, so it comes down to what syntax you prefer. I have very strong feelings about this: I despise ejs syntax. All the special characters add noise to the code and increase your surface area for mistakes. Its takes longer to read, it takes longer to write, and it takes longer to find bugs. However, ejs syntax is an expansion of HTML where pug syntax is completely different, so I can see why some might prefer ejs. I would spend a little time writing in each, then decide which one works best for you.
Made complex JSON inspecting super easy. Created revolutionary free online tool(https://jsongrid.com) to visualize JSON as table and Connected every table cell to JSON element, awesome right!
That is a neat reply. I agree with you. I'm personally comfortable with EJS since I know HTML very well. But you know lately, I started digesting PUG script, where I don't see any tag, it's clean code. So, I think I will go with PUG, it's a little weird in the beginning but better in the later part. Anyway, thanks for the recommendation.
I'm personally comfortable with EJS since I know HTML very well
From my experience, this is important. Even though EJS is kind of ugly, IMO it's much easier to pass around between different people without confusion. With PUG, you're really buying into a wholly different universe, that's probably cleaner and easier to use in and of itself, but different in ways that can matter.
IMO EJS is the more practical solution, even if it isn't "better".
Made complex JSON inspecting super easy. Created revolutionary free online tool(https://jsongrid.com) to visualize JSON as table and Connected every table cell to JSON element, awesome right!
Thank you Ben, I share your view too. I had that experience today itself only when one of my colleagues saw my PUG script and freaked out. I thought I better go with EJS since everybody knows HTML. Anyway, Thanks for your input on this.
Made complex JSON inspecting super easy. Created revolutionary free online tool(https://jsongrid.com) to visualize JSON as table and Connected every table cell to JSON element, awesome right!
The two are roughly equivalent in terms of functionality, so it comes down to what syntax you prefer. I have very strong feelings about this: I despise ejs syntax. All the special characters add noise to the code and increase your surface area for mistakes. Its takes longer to read, it takes longer to write, and it takes longer to find bugs. However, ejs syntax is an expansion of HTML where pug syntax is completely different, so I can see why some might prefer ejs. I would spend a little time writing in each, then decide which one works best for you.
That is a neat reply. I agree with you. I'm personally comfortable with EJS since I know HTML very well. But you know lately, I started digesting PUG script, where I don't see any tag, it's clean code. So, I think I will go with PUG, it's a little weird in the beginning but better in the later part. Anyway, thanks for the recommendation.
From my experience, this is important. Even though EJS is kind of ugly, IMO it's much easier to pass around between different people without confusion. With PUG, you're really buying into a wholly different universe, that's probably cleaner and easier to use in and of itself, but different in ways that can matter.
IMO EJS is the more practical solution, even if it isn't "better".
Thank you Ben, I share your view too. I had that experience today itself only when one of my colleagues saw my PUG script and freaked out. I thought I better go with EJS since everybody knows HTML. Anyway, Thanks for your input on this.
I think it’s great to go through the process of asking this question. There’s no right answer but at least it’s not all in your head anymore.
Agree 100%. :)