Templating languages: The hidden costs - Fun Fun Function

💖 Support the show by becoming a Patreon https://www.patreon.com/funfunfunction # Videos mentioned: 🔗 Declarative programming: https://www.youtube.com/watch?v=yGh0bjzj4IQ 🔗 Reduce basics: https://www.youtube.com/watch?v=Wl98eZpkp-c 🔗 Currying: https://www.youtube.com/watch?v=iZLP4qOwY8I # Hot spots in the video: 04:23 Expressive 11:23 Declarative 15:41 Complexity 18:06 Social cost 21:32 Loss of tools 🔗 mpj on Twitter https://twitter.com/mpjme 🔗The camera I use http://amzn.to/2kwlpAD 🔗 The microphone and sound recorder I use http://amzn.to/2kwli8e http://amzn.to/2lcVSfd 🔗 The lights I use http://amzn.to/2ld8jrX # Partial script Today I’m going to compare templating languages, like Handlebars, to generating DOM with JavaScript, like React does. There are two main arguments for using templating languages - that they are expressive and declarative. But there are also three big costs of using template languages, complexity, social cost, and loss of tools. Five years ago or so, the industry standard way of rendering DOM was to use a template language to glue your business logic together with your HTML. Then a few years ago React arrived on the scene, and did away with templating languages completely, and instead just using a JavaScript in place of the templating language. The native JavaScript approach is gaining a lot of traction, but a lot of developers still hold template languages in high regard, and are not convinced that the native JavaScript approach is a step forward. In this video, I’m not going to talk about some cost and benefits of template languages. Some feel that templates language vs. native JavaScript is just a matter of taste - I don’t agree with that. I totally recognize that computer science isn’t physics and there isn’t a clear-cut right or wrong, but there are benefits and costs that we can and should reason about. The two big benefits of templates are that they are expressive and declarative. Expressive. Templati