100-days-of-code VS mustache.js

Thinking about doing the #100DaysOfCode Challenge on X/Twitter? Well, you've come to the right place!

#100DaysOfCode Official Website | #100DaysOfCode

100 Days of Code Challenge is an initiative I am commiting to take, where I will be spending each day working on problem solving and personal projects to improve my skills and push my boundaries.

I'm participating in the #100DaysOfOSS challenge by OpenSauced. Inspired by the #100DaysOfCode challenge, #100DaysOfOSS is a challenge for everyone interested in open source to learn about open source, contribute, or maintain open source projects over 100 days, starting on July 24th.

Inspired by the great work of the #100DaysOfCode challenge, we're launching #100DaysOfOSS, starting July 23rd, and running through the end of Hacktoberfest, October 31.

When I started to learn Python, I joined #100DaysOfCode challenge on Twitter. Strangers supported me under my daily tweets and this helped me build a daily habit of coding. If I do something hard, I will need someone who cares and will cheer me up. It’s more important than it seems.

Here is the official site: https://www.100daysofcode.com/

So you're should be thinking: why I entered on the #100daysofcode challenge? Very simple: I'm a newbie in a lot of technologies and concepts. I focused all this time to learn PHP and Laravel, Linux and other stuffs to get a job and enter the market but now I have a new challenge to move on.

There's also -- https://www.100daysofcode.com/ -- I haven't explored their resources or curriculum tbh, but they seem to understand the importance of community.

Templating engine: SSGs rely on templating engines to define the structure of web pages. These engines enable developers to create reusable templates and incorporate dynamic content. Popular templating engines include Liquid, Handlebars, Mustache, EJS, ERB, HAML, and Slim.

I also enjoy simple templating engines. It makes it far easier to reason about a template and mentally step-through it. For existing art, there are:

DustJS which is a "logic-less" template engine (just loops and simple if-statements): https://github.com/linkedin/dustjs

and there is also mustache, which is very similar: https://mustache.github.io/

Personally, I've re-implemented DustJS in rust but its still a very alpha project: https://code.fizz.buzz/talexander/duster

I think the homepage states, "Logic-less templates"

Other popular templating engines include Jade, EJS, and Handlebars. Jade is a high-performance templating engine that is used for server-side rendering. EJS is a lightweight templating engine that is used for client-side and server-side rendering. Handlebars is a templating language that is based on the Mustache template language.

JSX just a templating language in this case, right? No reactivity at all? What's the benefit against using something like https://github.com/janl/mustache.js/ ?

You don't have to even program the replacement part yourself, because there are many libraries made specifically for that. For this example, I'd recommend mustache.

This is one of the least-bad names because it implements a non-Boost standard and it's named after that. I've used mustache in Python so knew immediately it was a templating language.

First, I setup mustache (npm package) as the templating language (the npm package hasn’t been updated in two years, so that’s great). Mustache is really simple, it provides a few helper utilities, like replacing variables, or iterating over data,

Once the array is ready and back in place, we need to display the information from the emails, and for that we can use the template node. This node uses the mustache system, which is a logicless template engine for creating dynamic content. In other words, it generates HTML code by using tags that are replaced by code.