foxygen

> the most compelling reasons to use HTMX instead (for building dynamic/interactive web applications) are to reduce the amount of JavaScript sent to the client and make pages become interactive faster

Next.js and TanStack Start don't send any JavaScript to the client if you decide to server-render everything. The upside is that you can opt-in into client-side components, and have all the interactivity benefits of React. I understand using HTMX if you are building a backend in Go/Python/..., but if you are already using Node, I see no reason not to use TanStack Start instead.

I don't see how HTMX has anything to do with UX. Could you clarify what you mean?

What is the point of using HTMX if your backend is JavaScript(Hono)?

Can you show me some examples that are hard to implement in Tailwind? I've been using Tailwind for an app with a somewhat complex UI for the past ~2 years, and it works great most of the time. Sometimes it doesn't, but then I write some CSS. Tailwind doesn't stop me from doing so.

I don’t know about Shadcn, but how does Tailaind hampers your ability to do anything?

It could, right? But let me tell you a secret: Apple doesn't want PWAs/web apps and actively limits Safari to force developers to build apps.

Because they are not the same as Go-style green threads/coroutines?

Because you are have an existing app in Python. Because you need some library that is not available in Go. Because you prefer Python. All are valid reasons.

The US did not create a neutral global free market. It created and maintains a US-centered international order that is relatively open for trade when openness aligns with American strategic interests and becomes coercive when it does not.

> Providing a stable currency is legit

The US does not "provide" a stable currency, it outright forces everyone to use it.

> how enforcing your ideals often comes into conflict with the values of your ideals themselves

The US/NATO couldn't care less about enforcing their "ideals". This is all about economic gain. It is very odd how liberal ideals must be enforced upon Iran, but not upon Saudi Arabia, which is a US ally, no?

> but that is another conversation, not for this thread

So discussing the use of force in the global economy is not fit for a thread about free-trade?

Are we pretending the US/NATO hasn't been interfering with the world's economy for the past decades? Or free trade here means the US being the sheriff of the world, forcing everyone else to use their currency, and bringing "freedom and democracy" to whoever thinks of challenging that?

Your first comment assumed I was "speed-running to a conclusion and squinting too hard", and this was "similar to the weird childish name-calling". I think that is in the same area(or worse) than saying "Amazing how X didn't even cross your mind". And sorry, but invoking that you have experience with X, Y, Z and thus your opinion is informed after criticizing some technology IS an appeal to authority.

> If you don't intend to discuss out of position of curiosity

I'm not the one making sweeping statements on the superiority of one piece of technology. Reading your other response, I think you are the one who have little to no curiosity in understanding how you might be wrong.

> That being said, has Akka started making full use of JVM's new green threads? Has Java itself started introducing immutability and STM / share-nothing as first-class citizens?

Amazing how it doesn't even cross your mind that there are trade-offs to those choices. Green threads are awesome, but guess what, they come at a cost. Same for share-nothing semantics.

> Has anybody rolled up their sleeves and said "Alright, BEAM VM's reign is over, I am making the same or better runtime as them in Java / Clojure!"?

You are again presupposing the BEAM has an absolute superiority over the JVM. "Better runtime" makes no sense on its own. Better is always relative to something. Better for whom? For what?

I'd bet that you work on a traditional CRUD enterprise software, and that IO(the database) is the real bottleneck of your app. In that case, sure, the BEAM is a solid choice(so is Python, Ruby and PHP nowadays). But let's please not pretend that is all there is to software engineering.