I spent a weekend debugging a bundling issue that happened with 30% probability . It was an issue that only expressed itself on our CI VMs - docker node-buster: 20, it happened because a dependency 4 times removed included babel and run commands that didn't jive with my apps vite and yarn.
It's nice to hear someone who doesn't cling to a framework and treats it as an oracle for writing a program. I like this new wave of programming returning to simplicity: less is more
I prefer to just use custom elements to determine when a page is loaded or not. It works perfectly for this situation where you can initialize libraries, do any garbage collection, etc.
I heard some devs say they really like DaisyUI which makes a bridge between Tailwind and Bootstrap-style. I'm not sure if it goes the full PicoCSS where it will style everything for you.
ohhhh man, i can't explain how excited i am working on it!! i need more hours in the day. Let me know if you want to get a sneak peak and give feedback sometime!
For your HTMX examples website: IMHO, submission of code that is pre-approved before display to avoid spam code...such code components need to work in order to build trust in the library and website...
yeah, hopefully these conversations will show the stuff it is very good at and the stuff it doesn't have an easy path for. would be curious to hear your experience if you get into it!
I think the secret that I tried to get across is that htmx (or anything on the front end) is already solving the wrong problems. The secret to great developer experience is a strong backend stack and then getting a bunch of value out of light weight htmx as a front end helper. The magic happens on the server, not on the client.
I spent a weekend debugging a bundling issue that happened with 30% probability . It was an issue that only expressed itself on our CI VMs - docker node-buster: 20, it happened because a dependency 4 times removed included babel and run commands that didn't jive with my apps vite and yarn.
I spent a weekend debugging a bundling issue that happened with 30% probability . It was an issue that only expressed itself on our CI VMs - docker node-buster: 20, it happened because a dependency 4 times removed included babel and run commands that didn't jive with my apps vite and yarn.
It's nice to hear someone who doesn't cling to a framework and treats it as an oracle for writing a program.
I like this new wave of programming returning to simplicity: less is more
simplicity has such long tail benefits!!
Rally great talk! thank you!
thank you!! i had a lot of fun
I prefer to just use custom elements to determine when a page is loaded or not. It works perfectly for this situation where you can initialize libraries, do any garbage collection, etc.
That sounds interesting. Can you describe your process a bit? Have you written it up anywhere?
I heard some devs say they really like DaisyUI which makes a bridge between Tailwind and Bootstrap-style. I'm not sure if it goes the full PicoCSS where it will style everything for you.
Great Interview, this was very helpful.
thank you!! i thought his story was fascinating
I remember in '95 building a .shtml wrap around center content that would change based upon the surrounding hyperlinks...cool stuff...
This about phone and serving UI from backend is brilliant idea.
ohhhh man, i can't explain how excited i am working on it!! i need more hours in the day. Let me know if you want to get a sneak peak and give feedback sometime!
@@hypermedia-tv I would love to check it
For your HTMX examples website: IMHO, submission of code that is pre-approved before display to avoid spam code...such code components need to work in order to build trust in the library and website...
yup, submission with personal approvals, i like it!
I need to rename my ship in Helldivers to Locality of Behavior.
?
its currently called Separation of Concerns
This conversation doesn't really convince me to use HTMX - sure if I am creating a simple website, but nothing more than that.
yeah, hopefully these conversations will show the stuff it is very good at and the stuff it doesn't have an easy path for. would be curious to hear your experience if you get into it!
I think the secret that I tried to get across is that htmx (or anything on the front end) is already solving the wrong problems.
The secret to great developer experience is a strong backend stack and then getting a bunch of value out of light weight htmx as a front end helper.
The magic happens on the server, not on the client.
I spent a weekend debugging a bundling issue that happened with 30% probability . It was an issue that only expressed itself on our CI VMs - docker node-buster: 20, it happened because a dependency 4 times removed included babel and run commands that didn't jive with my apps vite and yarn.
good god man!
this is a hypermedia villain origin story