3 ms·
I've been trending this way as well. Being asked to work on a needlessly complex React project turned me into a luddite. The more complex web development gets,
by al_borland 4y ago
I've been trending this way as well. Being asked to work on a needlessly complex React project turned me into a luddite. The more complex web development gets, the more I strip out of my own projects, until I'm left with the absolute basics (even opting for the short CSS and JS sections right in the HTML file).
I figure the more vanilla I make it, the longer it will last without needing a re-write. I often find HTML/JS a great way to mock up ideas or to create little utilities, that are also easy for others to use, without having to install anything or pass around executable files.
Although talking about the browser as the ubiquitous runtime makes me think of Windows XP. Wasn't Windows Explorer essentially running on IE? IE was also the default file viewer for a ton of formats. That all probably left a bad taste in people's mouth.
- prox 4y agoSame here. Usually something starts out a neat way of doing things (say React) and then the solution actually turns out worse than the original problem. Especially as frameworks grow and somehow need to have new versions and functions beyond its original use case.
- perilunar 4y agoSame. I always start web projects with a single html file with style and script blocks in the document head. Works a treat. If the project is a small demo then it's likely to stay a single file — I only move things to separate files when they get big, or if I start to reuse bits in other projects I might make a common file. I hate using npm, frameworks, build processes etc. for personal projects.