Right? Someone show this kid how we used to make web apps back in the day, using hardware 1/100th as powerful. Turns out you don't need to send megabytes of JS to the client to have it render a table
Location: Bay Area, California
Remote: Yes
Willing to relocate: For the right place in California
Technologies: PHP, Laravel, React, Vue, Next.js, Remix, Vue, Kubernetes, Docker, Golang, Rust, Node.js, Deno, Bun.
Résumé/CV: Available upon request.
Email: josh@joshmanders.com
Hello, I'm a full stack product engineer with over 25 years experience building apps on the web. I'm highly proficient in Node.js, JavaScript / TypeScript and PHP. I've contributed to a lot open source projects including but not limited to, Laravel, Vite, Tailwind, Alpine.js and Dokku. I know React, Vue and Angular like the back of my hand and can hit the ground running quickly in Next.js, Remix, Astro and Nuxt. Htmx CEO too, btw.
It includes older people because Mozilla had previous work before Firefox, so they heard that name first. I've never heard anyone my age (27) or younger call it that, including non-technical people who somehow still have a nostalgic and/or ideological affinity for Firefox.
When the Mozilla foundation took over the Netscape codebase, it was initially called Mozilla, or Mozilla Browser. There was also a Mozilla email client that came from Netscape Communicator.
Then they made a trimmed-down version of the browser with only essential features. That was initially called Phoenix, then Firebird, then Firefox. They did the same with the email client and called it Thunderbird. These existed alongside Mozilla Browser for a while until it was discontinued.
Yeah, again, probably because tech-literate (not tech-illiterate) people are more likely to know the history of the organization beyond when they started using the software. My point was pretty much that the know-nothing user learning about the software today/recently knows it's called Firefox and might never have heard of Mozilla. The branding is clear about Firefox and the Mozilla name is essentially background knowledge.
Htmx does work for simpler use cases like submitting a login form. Beyond that it gets messy very quickly as you start introducing more backend endpoints for every little interaction. In some stacks you have template fragments[1] which alleviate this problem somewhat but still, htmx doesn't scale for more sophisticated interactivity.
And most projects will still need client-side interactivity. So now your features are a mix of htmx stuff, something client-side (Alpine, Vue, whatever), and probably some HTTP endpoints to interact with the client-side stuff.
You also still need to take care of CSS which htmx completely ignores because it's really just a low level HTML exchange protocol if you will. With Vue, Astro, or Svelte you can encapsulate markup, behavior, and styles in a single file.
And on top of all that, the DX is quite frankly terrible compared to doing frontend with something like Vite with hot module reloading. Most backend servers need to restart and maybe even recompile the whole thing. PHP is the only exception I know of since every request "runs the whole application".
I feel that as software engineers, instead of talking about things like 'feels like magic', we are capable of reading the docs and understanding what something actually does, especially when it's pretty simple: https://htmx.org/attributes/hx-get/
They're talking about it but to actually see the thing they're talking about you have to pay before the part of the article that links to it is clickable
or you can just google it? it's not like the source code is exclusively held by 404media and you must pay them to view it, or something. would you have the same opinion if e.g. the article was the same but just didn't link to the repo?
Hello, I'm a full stack product engineer with over 25 years experience building apps on the web. I'm highly proficient in Node.js, JavaScript / TypeScript and PHP. I've contributed to a lot open source projects including but not limited to, Laravel, Vite, Tailwind, Alpine.js and Dokku. I know React, Vue and Angular like the back of my hand and can hit the ground running quickly in Next.js, Remix, Astro and Nuxt. Htmx CEO too, btw.
Hello, I'm a full stack product engineer with over 25 years experience building apps on the web. I'm highly proficient in Node.js, JavaScript / TypeScript and PHP. I've contributed to a lot open source projects including but not limited to, Laravel, Vite, Tailwind, Alpine.js and Dokku. I know React, Vue and Angular like the back of my hand and can hit the ground running quickly in Next.js, Remix, Astro and Nuxt. Htmx CEO too, btw.
