The question is how to get a good and efficient dev experience while also preserving that level of speed.
AI has now made that question mostly irrelevant, since it can generate and rapidly edit vanilla webpages without a framework to make the DX better.
[–] NohatCoder 4 days ago
[–] smt88 4 days ago
What? This is absolutely untrue for anything that isn't a trivial v1 prototype. Complex applications have a lot of boilerplate, which is unavoidable with the baggage of HTML and CSS.
There's a reason people are obsessed with web frameworks. Writing vanilla HTML/CSS/JS for large or complex apps is an enormous pain.
[–] preg_match 3 days ago
React et al. won’t just be 10x slower, it will also use 5x the amount of code with 5x the complexity.
People are obsessed with web frameworks because it’s more fun to engineer frameworks than make products or ship applications. Applications are boooooring. But, most of the time, you’re just wasting your time with the framework.
[–] jasomill 3 days ago
Not consistently over time it can't — at least not the usual LLM-as-a-service suspects, which don't even guarantee the model you use today will function identically tomorrow — unless you use it to create your own static site generator, which may or may not make sense depending on whether existing, battle-tested tools don't already fit the bill.
[–] smt88 3 days ago
Claude seems better at frontend dev work than at any other category of task. It’s far better than the last senior frontend dev I worked with.
There is no secret ingredient, writing a website, or anything really, without a framework is not wildly more difficult than using a framework.
Save for a few cases where all you really want to do is covered by the default configuration, you generally don't end up writing a lot less code with a framework. Worst case, you end up spending most of your time working around the framework.