Sharing a great read today:
Some of the takes are on the extreme end, but like most IT decisions, you can dial the pain to exactly what you want.
^C
Any conversation
I like this guy I drew
ibb.co/vxRtMxQC
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.
Having spent the last 12 months using HTMX in $day_job, after 5 years with react, I have come to the opinion that whilst large amounts of JS and CSS are not necessarily wrong, they should be reserved for progressively extending the platform with a composable set of generic UI primitives that build out a cohesive design language โ encoding business logic (including routing) there is generally a mistake



