perfectmotherfuckingwebsite VS neovim

>However, the expectations for a statically generated site have drastically gotten higher over the years. Readers want (rich) content served fast

No, readers just want content served fast. Nothing beyond simple markdown or static html with some images or video embeds inside.

>Writers want dead simple (but expressive) writing and publishing. They want control over how their writing looks.

Who are those "writers"? If you're making a "static site as a service" perhaps that's a concern.

If you're making your own static site, you can use the simplest Markdown or whatever else you prefer, writing it manually, with or without a generator. You could even use the Motherfucking Website standard (https://motherfuckingwebsite.com/) or the Better Motherfucking Website RFC (http://bettermotherfuckingwebsite.com/) or the Best Motherfucking Website recommendations (https://thebestmotherfucking.website/) or go fancy and use the cutting edge Perfect Motherfucking Website ones (https://perfectmotherfuckingwebsite.com/).

Well in that case you may want to see this then this

⁠https://perfectmotherfuckingwebsite.com/

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.