[dingle_thunk]

With H/3, modern frameworks have become unnecessary deviations from web standards that result in high costs and lower app lifetimes. Do standard server side work, don’t use node as a server, sprinkle a bit of typescript where needed, and keep things lean.

As a recovering front end developer of 20 years, someone who has played with every damn framework and used most of them professionally; just stick to web standards and ignore the frameworks unless you specifically need them.

For example: we are using HN. It is simple. It works. It does not need to change. It does not need to be reddit or twitter or whatever, to be engaging. It’s good because it’s focused simple and well maintained. Almost every app I enjoy that has been over complicated or lost touch with its user base has done so while implementing these frameworks. They are business death. See; Facebook (react destroyed fb), Google (angular destroyed AdWords and G Suite), and so on. You lose analytics, accessibility, performance for the end user, less server side bugs is bad when clients are running the bugs, and most importantly you lose track of your customers needs.

If you want your shit to work, keep it close to the metal, conform to standards, scale only where necessary, and listen to your customers.

[waboremo]

Your example does not align with your closing statement. Using Arc is certainly not "sticking to web standards" in the way you're proposing.

HN is simple and works, from a user perspective. I don't have my hands on the codebase, but I imagine it's kind of fun to work on precisely because it isn't "close to the metal". DX is just as important as UX is, you have to strike a balance.

Not sure there's much correlation between frameworks and apps becoming complicated or losing touch with their userbase. Using AdWords as an example, I'm like ~75% sure they went from one framework (Google Web Toolkit) to another (AngularJS).

[dingle_thunk]

GWT and Facebook’s PHP stack were both effectively server side technologies. GWT was pretty awful, but angular is probably the worst of the bunch when it comes to front end frameworks too. What I’m saying is you should run your app on the server and use HTML as a presentation layer. This is standard, it gives you visibility into bugs, it simplifies the end user payload, and it works quickly and reliably without needing huge refactoring projects and complex abstractions that your business does not need.

You probably don’t need a front end stack. You should just use the web standards as designed first, and then add improvements that customers like.

Developers wasting time on unnecessary fripperies is not a new thing: https://youtu.be/wHdHCoeUbU4

[amadeuspagel]

> For example: we are using HN. It is simple. It works. It does not need to change.

There are lots of basic issues with HN. For example, if you vote on a comment while writing a reply, the page reloads and you lose your comment. A web component for voting would do wonders here.

[paulddraper]

Imagine using HN as the model for web software projects.

[dingle_thunk]

You've been here since 2014. How much value have you derived from this code? How long would it take you to write it? https://news.ycombinator.com/hn.js

[jakelazaroff]

What is H/3?

[SahAssar]

HTTP3. The protocol name used in a lot of places is H3 (for example the alt-svc header)