151–160 of 230 posts
Earlier quoted context omitted.
As in, htmx is better? I haven't used it but last I looked into it I was extremely confused as to whether it was a meme, an actual framework, or both.
HTMX is great when your web interface is just a representation of a server state. If web interface is an application backed by a remote state HTMX falls apart.
Earlier quoted context omitted.
Oh no! Issuing SSL certificates! The horror! I really doubt that people who can’t install an ssh key should be able to practice software engineering. Sometimes, I think that software engineering should be a protected profession like other types of engineering. At least it will filter out the people who can’t keep their OS up to date.
This is not about how easy or difficult it is to issue TLS certificates, to configure SSH keys or to update the OS. It's about having to actively maintain them yourself in every possible situation until eternity, like when TLS versions are deprecated, SSH key algorithms are quantum-hacked, backward-incompatible new OS LTS versions are released, and so on. You will always have new stuff come up that you need to take c…
I felt more comfortable maintaining a VPS back between 2005 and 2015, but at that point attackers were dramatically less sophisticated and numerous and I was a lot more overconfident/naive. At least for solo operations I'm now inclined to use a PaaS… the exception to that is if said operation is my full time job (giving me ample time to make sure all bases are covered for keeping the VPS secure) or it's grown enough that I can justify hiring somebody to tend to it.
Earlier quoted context omitted.
I think the unfortunate truth is the simplest. Web development has long been detached from rationality. People are drawn to complexity like moths to a flame.
> People are drawn to complexity like moths to a flame. Not to complexity, but to abstraction. The more something is abstracted away, the more fungible "developers" become, to the eventual tune of Claude Code. No one cares that trying to debug a modern application is as hellish as its performance, the KPI that executives go for is employment budget.
This is one of the most frustrating thing about working with NextJS. There seems to be no way to improve the speed of building the app.
Earlier quoted context omitted.
web dev is a sewer All my projects are server rendered with jinja/minijinja, bootstrap, jQuery, and htmx when I need a little bit of SPA behavior on forms. No builds, just static <script src= tags. Very fast and easy. I'll never recommend anything else.
Sounds more difficult then modern web frameworks. We've all done this for little projects, but anything with users or development teams, your method is DOA.
Less code is basically always better, so if you can skip the huge amounts of JS and orchestration required by modern web frameworks, then it will be easy. People are out here using React to render static pages. It's very overkill.
Earlier quoted context omitted.
With C#'s Blazor templating, you can ditch all JS logic, and use raw C# for all front-end logic, and have it all be transparently server rendered similar to how Phoenix has LiveView. I also have experimented with HTMX and Django, and that seems to be a nice combination. Everything is AJAX again.
I've a C# fanboy, but Blazor's DX just isn't very good compared to say Vite. There are many conditions under which the hot reload just straight up crashes out regularly.
Earlier quoted context omitted.
Oh no! Issuing SSL certificates! The horror! I really doubt that people who can’t install an ssh key should be able to practice software engineering. Sometimes, I think that software engineering should be a protected profession like other types of engineering. At least it will filter out the people who can’t keep their OS up to date.
Time is a precious (and really expensive for SWEs) resource, why should one spend it on updating certs and instances?
Earlier quoted context omitted.
Sounds more difficult then modern web frameworks. We've all done this for little projects, but anything with users or development teams, your method is DOA.
I disagree, most webapps, like 99.9% I would say, are just forms, links, and pages. Meaning, they can be done with 0 reactivity and that is the most simple and straightforward way to do it. Less code is basically always better, so if you can skip the huge amounts of JS and orchestration required by modern web frameworks, then it will be easy. People are out here using React to render static pages. It's very overkill.
> we sponsor both Vite and TanStack because we believe in where they're going
I'd like to see more of this attitude.