# Why I choose Lua for this blog

**URL:** <https://forum.devtalk.com/t/why-i-choose-lua-for-this-blog/191367>\
**Category:** In The News\
**Tags:** via-news-bot, blog, lua, in-the-news\
**Created:** [16 March 2025 16:14 UTC](https://forum.devtalk.com/t/why-i-choose-lua-for-this-blog/191367 "2025-03-16T16:14:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![CommunityNews](https://forum.devtalk.com/user_avatar/forum.devtalk.com/communitynews/32/1113_2.png) [@CommunityNews](https://forum.devtalk.com/u/CommunityNews)\
**Post date:** [16 March 2025 16:14 UTC](https://forum.devtalk.com/t/why-i-choose-lua-for-this-blog/191367/1 "2025-03-16T16:14:11Z")

</div>

> This blog used to run using with a stack based on [Racket](https://racket-lang.org/)using [Pollen](https://docs.racket-lang.org/pollen/) and [lots of hacks on top of it](https://andregarzia.com/2022/05/How-this-blog-works-or-embracing-chaos.html). At some point I realised that my setup was working against me. The moving parts and workflow I created added too much friction to keep my blog active. That happened mostly because it was a static generator trying to behave as if it was dynamic website with an editing interface. That can be done really well — cue [Grav CMS](https://getgrav.org/) — but that was not the case for me.
> 
> Once I decided to rewrite this blog as a simpler system, I faced the dilema of what stack to choose. The obvious choice for me would be Javascript, it is the language I use more often and one that I am quite confortable with. Still, I don’t think it is a wise choice for the kind of blog…

Read in full here:

> **[Why I choose Lua for this blog • AndreGarzia.com](https://andregarzia.com/2025/03/why-i-choose-lua-for-this-blog.html)**
>
> AndreGarzia.com website