Recent searches
Search options
@schizanon@mas.toIn the beginning #websites were static files.
Then websites were generated dynamically on a server with a language like #PHP or #Ruby.
But when we wanted to do complex #frontend behaviors we would need to generate #html in the same way as those #backend languages, which was awkward.
So, we used #reactJS #fullstack to render "Single Page Apps" (#SPA) in the browser and on the server using "Server-Side Rendering" (#SSR).
Now there are some that suggest we oughtn't be shipping #DOM declaring JS to the browser at all:
#HTMX recommends returning HTML from APIs and simply rendering that according to the rules of its attributes. In other words; the only DOM manipulations that a frontend app can make are those that are handed to it by the server. The server is the only place where HTML is generated. HTMX simply hydrates it.
#HTMX is for #JS what #TailwindCSS is for #CSS
the return of php 5 but with better marketing
@troglodyt it's got a lot in common with #angularJS I think.
@schizanon i’ve been actively ripping out alpinejs (i think similar to htmx) as phoenix liveview matures
that said, i keep tailwind around cuz i am bad at css
@kenichi sorry to tell you; if you've learned all the TailwindCSS classes, then you've been learning CSS all this time, just with messed up capitalization 
@schizanon don't know if i'd go so far as to say i've "learned" tailwind 
@kenichi as if anyone ever stops googling CSS properties 