147 posts · Page 5/5
(*) — Journal
Journal.
Notes on web, automation and AI from our team.
(133)
WebGPU finally lands — what to actually build
WebGPU shipped in Chrome, Edge, Firefox and Safari by late 2025. Now what. Browser-side ML inference is the killer app.
→
(134)
Feature flags for web apps — what to use
Without feature flags, big features turn deploys into rituals with rollback drills. What to use for small and mid teams.
→
(135)
Deploying a PWA on shared hosting
Not every project gets a Vercel budget. Standard PHP shared hosting still works for PWAs in 2026.
→
(136)
Postgres is enough for 99% of projects
You probably don't need MongoDB, ClickHouse or DynamoDB. Postgres handles JSON, full-text search, time series and queues fine.
→
(137)
Next.js vs Nuxt 3 — pick by your team
Next.js for React teams, Nuxt for Vue. Technically equivalent. Pick by what your team already knows.
→
(138)
Tilda export — what gets lost
Tilda Business plan offers HTML/CSS export. The exported site is not the full site. Here's what gets lost.
→
(139)
Corporate site 2026 — what's required now
What was OK in 2018 is below baseline in 2026. The list of must-haves for a serious corporate website.
→
(140)
SaaS landing anatomy 2026
The structure of an effective SaaS landing has shifted. "Hero + features + CTA" is no longer enough. What's in a 2026 landing.
→
(141)
Leaving WordPress in 2026
WordPress still runs a large share of the web, but some teams outgrow it. Where they go, what migration really involves, and when staying is the better call.
→
(142)
Multilingual site 2026 — picking a structure
/en/, en.example.com, or ?lang=en — three approaches to multilingual sites. SEO and ergonomics differ.
→
(143)
Stripe vs Lemon Squeezy for SaaS in 2026
Stripe is the standard. Lemon Squeezy handles tax compliance globally. For solo founders the second is often the better deal.
→
(144)
The case for boring tech in 2026
Every framework promises 10x velocity. Most teams ship faster on Postgres, nginx and PHP than on the framework of the month.
→
(145)
The slow death of jQuery — should you migrate now
jQuery is still on 70%+ of the web. Removing it from a project is rarely worth a sprint, but new projects should never include it.
→
(146)
Tailwind CSS at scale — when it breaks
Tailwind ships fast for small projects. On a codebase with 50+ developers and 5 years of history, the cracks show.
→
(147)
shadcn/ui adoption — design systems shift
Copy-paste, not install. shadcn/ui changed how teams build UIs. Two years later — what stuck and what fell apart.
→