4 ms·
Experimenting with no-build Web Applications
- martin_a 1y agoNice to see Pico CSS in use here. I'm using it for internal tools and private side projects for some time, too. I like it.
- sirjaz 1y agoIt would be great if you created this as a single executable desktop or cross platform app.
- mock-possum 1y agoThe only reason I work on apps with build steps is because I’m paid to. When I play with stuff on my own, I keep my toolchains real simple. Whenever possible, my rule is “I drag the html file into the browser and it just works.” As it was in the old days Also, FTA - is ‘nerdsnipped’ distinct from ‘nerdsniped’?
- hu3 1y agoWhenever I have the chance, no-build is how I have been architecturing web applications for the last decade or more. That plus no-compile/near-instant-compile tooling (PHP, Bun, Go) enables instant feedback during development. It's liberating and force multiplier. I also implement custom unit testing libraries that are simpler than industry standard but MUCH faster. It hits different when unit tests finish running 1s after saving a file versus 10s. I also make unit test runner play sound for success and failures. So you don't even have to look at tests to know if they passed or failed. It's dopaminergic. And reduces cognitive load because you can offload unit tests feedback to auditive system, aliviating the already heavily overloaded developer visual system. To this day I receive e-mails and direct messages of developers thanking me for their joy working in these projects. On average once every 2 months or so. Makes my day. Everything in the name of reducing cognitive load. This is our bottleneck.
- halpow 1y agoTime to open source your solutions?
- dhruvrajvanshi 1y ago> I also make unit test runner play sound for success and failures. This is brilliant! Such simple change but a massive qol improvement. > Test runner Node has one built-in these days. Haven't tried it yet but would be nice to get rid of the vitest dependency. Mostly because it makes my dependabot noisy for no apparent benefit.
- christophilus 1y ago> So instead of writing the book I want to write, I decided to rewrite Little Webby Press in a stack that is more suitable to my own enjoyment. This guy stole my patented side-project management technique.
- christophilus 1y agoTo post a more serious comment, I’d forgotten about Mithril. It is indeed nice. I think I’d miss Typescript and JSX too much, though. I may have to play with this stack soon, and see if it can change my mind.
- velomash 1y agoThis is why many developers are upset with AI. A lot of us love the craft of writing code. The last version worked. There was no need to rewrite other than enjoyment. “Delivering value” without the craft of coding a project grates against many. I too enjoy that process, but I’m also learning when and how the ultra boost of AI assistance can fit into a quality first / crafting mentality. I suspect the author would shudder at the thought though
- rcarmo 1y agoThis is the way. Everything of consequence I’ve built with JS and still maintain today has at _most_ a bundler/minifier. If I see I need to npm install a web library, I instantly skip it and look for something I can get as a plain js file (even if I need to pick it off a CDN).
- deleted 1y ago[deleted]
- wackget 1y agoNot trying to sound like an asshole but articles like this always confuse me. "Experimenting" with no-build web apps makes it sound like web apps require build steps by default. The opposite is true. The idea of building/compiling in web development is (and has always been) totally alien. HTML, CSS, JavaScript. None of these require a build step. It also further confuses me when authors talk about simplifying their web tooling but instead of using the actual web languages mentioned above, they resort to using some weird framework which just introduces another learning curve and more cognitive load. As a web developer of 20 years, you know what I build web apps with? HTML, CSS, and JavaScript.
- rambambram 1y agoThis. Add in some PHP and MySQL, and I still don't have to 'build' anything. Well, I have to build it of course. As in, me as the developer has to make it.
- weird-eye-issue 1y agoThe website in your profile isn't even loading for me
- rambambram 1y agoOkay. For me it is. Never had complains like this, even with thousands of HN visitors an hour.
- weird-eye-issue 1y agoIt's loading now
- rambambram 1y agoCool, thanks for letting me know! ;) I see some traffic from HN now. For some of my websites I block traffic from certain timezones and/or browser languages, I just double-checked but Hey Homepage doesn't block anything. May I ask from what country you're visiting? I myself experience long loading times for websites from Japan for example (I am visiting from western Europe).
- WorldMaker 1y ago> Both the ebook and the website generation functions are massive waterfalls async/await syntax works in all current browsers [1], you can clean up your massive waterfalls without a build process today. [1] https://caniuse.com/mdn-javascript_operators_await https://caniuse.com/mdn-javascript_operators_await
- moralestapia 1y agoEven back then there were polyfills, which most of the time all that was involved was an extra <script src="..."> tag. Modern web development (tooling) is trash, lmao.
- bob1029 1y agoI think targeting no JS at all is much more impactful to the overall experience of web development. Reaching for it only when HTML+CSS have failed you is the original intent. Server-side rendering can take you really far if you are patient and creative. NPM/Node is at the heart of my displeasure with JS. I don't mind JS in the browser when done tastefully. But I don't think it makes much sense outside of the DOM. As another comment noted, you often have to go dig through CDNs and hack at URLs to get the actual JS files for non-insane hosting models (i.e., statically from the same machine that hosts everything else). The notion that I need a CDN to serve a few kilobytes of source for anything short of netflix.com is absolutely insane. I would advocate starting your next web project using 0 lines of JS, even if you intend to use the full USS Enterprise to build it out for prod. See how far you can get with just HTML & CSS. Consider that anything proximal to layout/style/art/etc. is entirely within this box. Javascript is not going to save you from an art problem. It can only make it worse.
- mozanunal 1y agoIf you are looking for web app stack, that does not require build step: TLDR: I was looking for a web app stack that I can work easily in year 2030, it is for side project, small tools I am developing and that is what I came up with. I've been spending some time thinking about (and getting frustrated by!) the complexity and churn in modern frontend development. It often feels like we need a heavy build pipeline and a Node.js server just for relatively simple interactive applications. So, I put together some thoughts and examples on an approach I'm calling "No-Build Client Islands". The goal is to build SPAs that are: Framework-Free (in the heavy sense): Using tiny, stable libraries. No Build Tools Required: Leveraging native ES modules. Long-Lasting: Reducing reliance on rapidly changing ecosystems. Backend Agnostic: Connect to any backend you prefer. https://mozanunal.com/2025/05/client-islands/ https://mozanunal.com/2025/05/client-islands/
- jslakro 1y agoRecently instead of writing the book I want to write, I decided to search a good tool to create eBooks, I found Writebook https://books.37signals.com/2/the-writebook-manual https://books.37signals.com/2/the-writebook-manual But considering that LWP doesn't require an account I will go for it
- seanw265 1y agoA word of caution on import maps. My app, Easel, previously relied on import maps for running user and AI-authored code in an iframe and it caused many many issues for us. Import maps combined with ESM CDNs (like jsDelivr, jspm, or ESM.sh) can work in ideal conditions. But in practice, a lot can go wrong. Many packages don’t compile cleanly to ESM, ad blockers can interfere with individual scripts (the innocuous Lucide "fingerprint" icon [1] is a common casualty), and a package might work on one CDN but not another (intercompatibility is shaky at best). Worse, any failures happen at runtime, and a single missing or broken script can snowball into a full app breakdown. If it’s working for you, great. Just make sure your versions are pinned. But if you’re building anything dynamic, it’s worth knowing that the ecosystem is still quite brittle. I'll probably author a blog post about this one day. [1]: https://lucide.dev/icons/fingerprint https://lucide.dev/icons/fingerprint