惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

人人都是产品经理
人人都是产品经理
有赞技术团队
有赞技术团队
WordPress大学
WordPress大学
月光博客
月光博客
T
Tailwind CSS Blog
阮一峰的网络日志
阮一峰的网络日志
小众软件
小众软件
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Last Week in AI
Last Week in AI
大猫的无限游戏
大猫的无限游戏
S
SegmentFault 最新的问题
罗磊的独立博客
Jina AI
Jina AI
酷 壳 – CoolShell
酷 壳 – CoolShell
宝玉的分享
宝玉的分享
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园 - 三生石上(FineUI控件)
量子位
雷峰网
雷峰网
Apple Machine Learning Research
Apple Machine Learning Research
美团技术团队
博客园 - 聂微东
V
V2EX

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I stopped using React for simple tools… and started shipp...
DarkenAmber · 2026-06-18 · via DEV Community

DarkenAmber

I didn’t quit React because it’s bad.

I quit it because I noticed a pattern.

Every time I wanted to build something small and useful, I ended up building something way too complex.

It always started the same way: “this will be a quick project”.

But then I would open a React setup, add a bundler, think about folder structure, install dependencies, and suddenly the actual tool was no longer the focus.

I was building infrastructure instead of building the thing.

So I tried a constraint

One rule:

No frameworks. No backend. No build tools. No npm.

Just a single HTML file.

Vanilla JavaScript, inline CSS, and localStorage when needed.

Nothing else.

At first it felt limiting. Like I was going backwards.

But something unexpected happened.

I started finishing things again.

The shift was immediate

Ideas stopped getting stuck in setup.

I would open a file and just build.

No architecture decisions.

No dependency rabbit holes.

No configuration fatigue.

Just:

idea → code → done

What I built with this approach

A few real examples:

invoice generators
markdown editors
budget trackers
simple calculators
internal tools for quick work tasks

Each one is just a single HTML file.

It opens instantly in a browser. No install. No setup. No friction.

The real change wasn’t technical

It was mental.

I stopped asking:

“What’s the correct stack for this?”

And started asking:

“What is the simplest thing that actually solves the problem?”

Most of the time, the answer was much simpler than expected.

Not everything should be a framework project

This is not a “React is bad” story.

React is great when you actually need it.

But most small tools don’t.

They just need to exist.

Where this approach breaks

Single-file apps are not meant for everything.

They break when you need:

real-time collaboration
multi-user systems
complex authentication
large-scale applications

But most personal tools and internal utilities never reach that level.

My current rule

Start as a single file.

Add complexity only when it becomes necessary.

Not when the ecosystem expects it.

If you want to try it

Pick one small idea today.

Build it as a single HTML file.

No setup. No frameworks. No excuses.

Just ship it.

If you want to see how I formalized this approach, here’s the project:

https://github.com/DarkenAmber/single-file-app

It’s a small “skill” that pushes AI-assisted coding toward building complete web tools as a single HTML file — fast, minimal, and dependency-free.