reject modernity embrace htmx

Listen. I just don't like that they replaced glass with TV screens that show what's behind

They fucking what now?
- They replaced glass with screens that show what they think the product is.
  In stores run by the particularly stupid.

You're probably joking but just to save people some time, it does not actually recommend HTMX. (I remembered seeing this website a while back but didn't recall anything about HTMX so had to check.)

Svelte my man, I barely have to read the docs, just guess how things should be done because that's how it would work in vanilla JS, and most often it just works.

Svelte is very good. If I had to use a frontend framework I would either pick svelte or soldijs both are great.
- svelte or soldijs both are great
  What would you say is the most important difference between the two? I feel like I should dip my toes into Svelte, but I haven't had a reason yet
Been a react dev for about 4 years now, I’ve heard good things about Svelte. But like from a career perspective would it be worth the switch now?
- It's good to play around with different frameworks from time to time, even if it's just to form an initial opinion on. I've been programming for 15+ years and the only constant is learning new things.
- From a career perspective using it enough to know whether you'd like to or be willing to work with it in the future is probably enough. Then when you're looking you know whether you want to apply for jobs focused on it.
  On that topic I've been on the market and haven't seen Svelte mentioned a single time when searching, granted I've probably only looked at a couple hundred listings (most being WFH).
- From a career perspective, think of languages and frameworks as tools. Knowing how to work with more tools broadens your horizon about what you can achieve and how efficiently. Sure, you can specialize on certain tools, but these come and go.
Svelte is the way to go

I thought HTMX was a joke, but they're serious.

I am serious
- and don't call me Shirley.
C'mon, what's not to like about bonding every UI action against a remote server? What's a few milliseconds anyway? I'm sure it works fine over cellular networks. I mean, it works great on my dev machine! /s
- What kind of you UI action are you talking about? Most of the time you need data from the server and if you want have some animations with css it will be client side anyway also it's not like you cannot write JS. I mean downloading thousands of lines of js for some web framework over cellular does not sound better tbh.

I personally don't like the htmx style of coding. It often feels like having to explain what I want to do to someone else using only a limited set of custom words, instead of just doing it myself.

I understand you but for me it's the opposite I am not bound to using js for everything and can just return html from the server like I want. Also everything else still works I can write js if I want to. Htmx gives me more words I can use in html not less. Also I can manage the state via the url and the server. In other frameworks I often had the problem that I was writing the same logic twice in backend and frontend.
- Exactly. Not everything needs to be a goddamn SPA!
I just peeked at the docs and right off the bat I don't like how they have conflicting attributes like hx-get and hx-post. What happens if both are set at the same time? Why not just have hx-method?

Reject Web technologies - embrace native mobile app development

Compose feels like React but without the bad JavaScript parts, really pleasant experience!

Ah, yes, let's have thousands of specialized apps, each with uniquely expiring dependencies and vulnerabilities, instead of one browser that can work with apps that are standardized for OSS, UI, accessibility, performance, inspection by humans and machines, and security.
- Funnily enough, I've found JavaScript to be by far the worst offender for expiring dependencies and vulnerabilities.
I love Compose, creating UI is actually fun. The whole ViewModel thing though I don't love
- I love Compose, creating UI is actually fun.
  It's a good time, for sure. That being said, I've stopped working with UI, and I don't really miss it. I still do some side projects in Compose though, and it's always way better than XML.
  The whole ViewModel thing though I don't love
  When it clicks, it's actually not that bad imo. I think the main problem is that Google aren't really explicit enough about how to leverage them effectively, and as such they can be pretty hard to get right.
How are you supposed to develop web applications then?
- That's the neat part - you don't.

I'm good with my Vue, thanks. I hate React though. I can see htmx simplifying some things and being adopted by front-end frameworks. The same way improvements in HTML and CSS have been adopted.

Fellow Vue enjoyer! I love Vue, it's so friendly. Maintaining a complex React app feels like getting dragged behind a truck down a one way road.
(Did you like my two way data binding joke there?)
- Hello sane friend! You used your joke to great effect!
  Did you like my useEffect joke haha
Vue and AlpineJS for me.
- When you say "and", do you mean together?
  I love Vue, first time I've heard of AlpineJS. From my quick searching, they seem pretty similar. What advantages does one have over the other? Thanks :)

Any svelte enjoyers

I love HTMX ❤️

Gross.

If you know HTML and Python already I would recommend going for something like jinja2 + flask or fastapi and try some htmx stuff no need to use everything you can just refresh the site at the beginning. This should be pretty beginner friendly. It really depends on what you want to do. I don't know much about Hugo or Publii. If you want to make an interactive website and not just a blog or static website I would advise you against using either of the two. If you want to get a job in frontend webdev I would advise you to learn javascript (https://javascript.info/) and some framwork like react also learn tailwind or css.