htmx

So, one of the issues with PHP/CF was that to many developers it seemed to lack a means of encapsulation/reuse.

Not saying it was an accurate tagging... but it was the reason for dismissal.  Instead, they used factories of abstract visitors....

zend is making everything in their power to ruin it further

fuck OOP, wait, that should be a hashtag - #fuckOOP

So, cfront was great.  It was an absolute pleasure to have dynamic dispatch.

Templates (generic programming) was also great.

But, the entire C++ and then Java ecosystem that extended it to something more than a low-level technique....

https://www.youtube.com/watch?v=QM1iUe6IofM

and the Rational Rose people who sold CASE to fortune 500 people.

Then there's the whole decade of database technology lost to "object" databases in the 90s

(all while Oracle solidified their market advantagE)

Ok.  Anyway.  Thanks for the distraction.  I should ge to twork.

https://github.com/aidenybai/lucia#similar-projects Intercooler here in similar projects 😛

i think that poor kid got bullied into including it by HackerNews 😦

lesson here is - don't post your stuff on hackernews and/or don't read the comments there

and let's not forget it's just a dangling appedix of ycombinator

> <@!725789255590215732> Is the `hx-history-elt`  usable multiple times on the same page? I run into an issue where htmx errors trying to store the entire body in the history cache because it's too big, and when adding `hx-history-elt`  multiple times, it only seems to pickup the first one. I may end up implementing a different history cache solution, but first I want to make sure if I need to go this route. I would like to have "component" specific caching. Also currently it seems the cache stores the innerHTML regardless of default swap. I am not sure yet if this makes a difference, just something to point out.

history element is not intended to be used more than once

You can set the cache size (numerically) if you want to a lower number