The Pain of Technology Selection: Fighting with the Toolchain Every Day#
As a long-time user of static websites, my old site was built on a purely static architecture, lightweight enough to run smoothly on a Raspberry Pi. The source code repository still maintains a refreshing "one-click deployment," and I thought I would continue to delve into the static site field—until I suddenly had the idea to add a blog module to the website.
The old site's code has been open-sourced, give it a Star meow.
I originally planned to build a modern blog using Astro + Tailwind v4, but suddenly realized that the ecosystem was not ready, leading to a breakdown in developer technology selection: shadcn/ui's support for Tailwind v4 is still in a state of Schrödinger's support, meaning the CLI hasn't kept up at all. As a fallback, I tried DaisyUI v5 Beta, after all, this version was developed in conjunction with TW4, but in reality, the page harmony felt like it had been hit by a meteor—attempting to mimic the dynamic information flow layout of Xiaohongshu, ultimately presenting a "90s portal website revival style" aesthetic.
⏱️ Subsequent Progress:
Spent 20 hours adjusting the UI → The design draft became uglier → Deleted node_modules in anger before even halfway through the startup → Experienced breaking changes with the dependency library that broke myself → An eighty-year-old old maker fled the front-end universe overnight
The Trap of Self-Development: Why I Advise You Not to Reinvent the Wheel#
When a person starts to self-develop a blog framework, the following scenarios often occur:
- Estimated Cost: 3 days to quickly create a minimalist blog
- Reality Script:
• Day 1: Struggling with the dark magic of the MDX rendering engine
• Day 3: Deeply trapped in the hell mode of adaptive layout
• Day 7: Experiencing various rendering errors while discussing SSR and CSR mixed programming
• Day N: Watching the Problems and feeling youth slipping away
Final Awakening: Using ready-made solutions is not shameful! Those "elegant frameworks" (Astro/Hugo, etc.) that make developers contribute their mental energy are merely a slow poison that makes everyone who fixes bugs at dawn feel elegant.
xLog: The Dimensionality Reduction Strike of On-Chain Blogs#
My thoughts when I stumbled upon an on-chain blog platform:
"Isn't this just an ordinary Notion-style editor? ... Wait! Markdown direct output + IPFS storage + on-chain proof? Article asset autonomy? Mom, I've found my dream blog!"
Blood and Tears Experience: The Ultimate Survival Guide for Technologists#
- Lightweight ≠ Maintainable: While static sites are appealing, extensibility is the lifeblood of long-termists
- Be Cautious with UI Library Choices: New version releases can become a scene of technical debt explosion (Tailwind victims share their stories)
- Open Source ≠ Worry-Free: Unless you are prepared to contribute PRs to the community weekly as tuition
Moment of Enlightenment
Now my blog has completely moved in, and I finally understand: the highest wisdom of technologists is not to reinvent the wheel, but to grasp the alien technology that significantly leaps productivity. After all—life is short, rather than spending 50 hours tweaking CSS to achieve button click effects, it’s better to use that time to write a few more on-chain blog posts that can serve as digital legacies!
Important
So now, Hello xLog.