6 ms·

PrimateJS: Svelte and Htmx Quick Start

51 points by phaleth 4y ago

yoyohello13 4y ago
This seems like a product created by ChatGPT...
- Finnucane 4y ago
  That sounds like something Bard would say.
deleted 4y ago
[deleted]
DrKerryKing 4y ago
[flagged]
deleted 4y ago
[deleted]
sosodev 4y ago
What is this supposed to be? I familiar with Svelte and HTMX but I don't understand from any of the documentation here what PrimateJS is.
- ActionHank 4y ago
  yes
- jmull 4y ago
  I don't think it's coherent. It doesn't really make sense to use htmx and svelte together. (This QuickStart just shows svelte. htmx imported but not really used.) I think I remember this was posted a few weeks ago too, but maybe then it really was htmx? But it's really unclear why you'd use this over, say, sveltekit (the "native" app framework for svelte the reactive UI library) or, if you don't want to use that style of framework, any of the many other routers, server, etc. Good name, though. Maybe that's why it keeps catching my eye.
unsupp0rted 4y ago
A "Why PrimateJS?" section at very the top would be helpful.
toinbis 4y ago
Indeed it's hard to grasp what mission the framework is up to. I'll just say though that am very happy to see htmx getting more traction. I'm a technical marketer and I was really saddened to see trend of bussiness logic being expresses in TS and spitted out into small bundles for marketers to have no clue on what's going on. Now I just say this magic combo to frontend team: htmx+alpine+xstate-fsm. And suddenly I have gained the control back! JS-in-markup is a dream comming true for those who actually keep working on optimizing the websites after developers create them.
- Xeoncross 4y ago
  I would like to see HTMX cut down to a tiny size. It's already larger than several network packets for many network configurations (15.05 kB gzip / 42.58 kB size). Now we need an htmx-lite that focuses on not growing into it's own JS framework (that's kind of the whole point after all)
kjksf 4y ago
I did a couple of project in Svelte (proof: all the tools on https://onlinetool.io/ https://onlinetool.io/ are in Svelte). I understand (I think) what htmx does. I don't get at all the need to add htmx to Svelte. It looks like cargo culting because Svelte does what htmx does and more. htmx has a use case where you mostly generate html e.g. on the backend and then want to sprinkle bits of interactivity by making it easy to replace parts of your HTML with another HTML generated by the server. Svelte has it's own, superior, way of doing interactivity. The whole point is to make it easy to generate HTML client side. Anything you would want to do with htmx you can do just in Svelte. You've already paid the price (setting up Svelte transpilation toolchain) you might just as well get all the benefits of Svelte.
- CameronNemo 4y ago
  Thanks for your input. I have experience with Svelte, but not so much with htmx. I always wondered if I would benefit from using htmx for a project, but kind of doubted it.
  - SCUSKU 4y ago
    I am a fan of htmx, but the only time I've found it useful was when I wanted a radio option in a form to send a POST request or something like that (which was probably an anti-pattern anyway) using django templates. I do think it's a welcome addition to the web dev space, but for me personally, it was more of a stepping stone from learning jQuery, then htmx, and then going to SPAs.
- listenallyall 4y ago
  > Svelte has it's own, superior, way of doing interactivity. The whole point is to make it easy to generate HTML client side. I'm not a Svelte user, I am an HTMX fan. It would seem, in my experience, that if the data intended to be presented to the user lives on a server (i.e. in a database, retrieved via API, etc.) then it's not going to be so easy to generate that HTML client-side. Obviously, you have to call the server... why not simply allow it to send you back an HTML segment that's ready to be plugged in as-is, rather than requiring any client-side transformation?
earthboundkid 4y ago
The kaleidoscope theory of framework design: shake it up first, see if the jumble makes any sense afterwards.
- billllll 4y ago
  My theory is that there is so much money on the table, that every single possible permutation of software is being tried no matter how nonsensical. It's like everybody is simultaneously brute-forcing a combination lock. To me, I would think there is negative synergy with combining a UI framework like Svelte, with htmx's replacement abilities. One of the value props of htmx is that you don't need to use a framework like Svelte, I don't quite see the point in combining them.
yewenjie 4y ago
I would really appreciate if there is a Why <New hot framework> section in the homepage of such new hot frameworks.
yawnxyz 4y ago
Is this supposed to be a smaller Sveltekit alternative? I'm confused as to what it adds to the ecosystem
3535546hhh73 4y ago
Nmkik B

51 points by phaleth 4y ago

yoyohello13 4y ago

This seems like a product created by ChatGPT...

Finnucane 4y ago
That sounds like something Bard would say.

deleted 4y ago

[deleted]

DrKerryKing 4y ago

[flagged]

deleted 4y ago

[deleted]

sosodev 4y ago

What is this supposed to be? I familiar with Svelte and HTMX but I don't understand from any of the documentation here what PrimateJS is.

ActionHank 4y ago
yes
jmull 4y ago
I don't think it's coherent. It doesn't really make sense to use htmx and svelte together. (This QuickStart just shows svelte. htmx imported but not really used.) I think I remember this was posted a few weeks ago too, but maybe then it really was htmx? But it's really unclear why you'd use this over, say, sveltekit (the "native" app framework for svelte the reactive UI library) or, if you don't want to use that style of framework, any of the many other routers, server, etc. Good name, though. Maybe that's why it keeps catching my eye.

unsupp0rted 4y ago

A "Why PrimateJS?" section at very the top would be helpful.

toinbis 4y ago

Indeed it's hard to grasp what mission the framework is up to. I'll just say though that am very happy to see htmx getting more traction. I'm a technical marketer and I was really saddened to see trend of bussiness logic being expresses in TS and spitted out into small bundles for marketers to have no clue on what's going on. Now I just say this magic combo to frontend team: htmx+alpine+xstate-fsm. And suddenly I have gained the control back! JS-in-markup is a dream comming true for those who actually keep working on optimizing the websites after developers create them.

Xeoncross 4y ago
I would like to see HTMX cut down to a tiny size. It's already larger than several network packets for many network configurations (15.05 kB gzip / 42.58 kB size). Now we need an htmx-lite that focuses on not growing into it's own JS framework (that's kind of the whole point after all)

kjksf 4y ago

I did a couple of project in Svelte (proof: all the tools on https://onlinetool.io/ https://onlinetool.io/ are in Svelte). I understand (I think) what htmx does. I don't get at all the need to add htmx to Svelte. It looks like cargo culting because Svelte does what htmx does and more. htmx has a use case where you mostly generate html e.g. on the backend and then want to sprinkle bits of interactivity by making it easy to replace parts of your HTML with another HTML generated by the server. Svelte has it's own, superior, way of doing interactivity. The whole point is to make it easy to generate HTML client side. Anything you would want to do with htmx you can do just in Svelte. You've already paid the price (setting up Svelte transpilation toolchain) you might just as well get all the benefits of Svelte.

CameronNemo 4y ago
Thanks for your input. I have experience with Svelte, but not so much with htmx. I always wondered if I would benefit from using htmx for a project, but kind of doubted it.
- SCUSKU 4y ago
  I am a fan of htmx, but the only time I've found it useful was when I wanted a radio option in a form to send a POST request or something like that (which was probably an anti-pattern anyway) using django templates. I do think it's a welcome addition to the web dev space, but for me personally, it was more of a stepping stone from learning jQuery, then htmx, and then going to SPAs.
listenallyall 4y ago
> Svelte has it's own, superior, way of doing interactivity. The whole point is to make it easy to generate HTML client side. I'm not a Svelte user, I am an HTMX fan. It would seem, in my experience, that if the data intended to be presented to the user lives on a server (i.e. in a database, retrieved via API, etc.) then it's not going to be so easy to generate that HTML client-side. Obviously, you have to call the server... why not simply allow it to send you back an HTML segment that's ready to be plugged in as-is, rather than requiring any client-side transformation?

earthboundkid 4y ago

The kaleidoscope theory of framework design: shake it up first, see if the jumble makes any sense afterwards.

billllll 4y ago
My theory is that there is so much money on the table, that every single possible permutation of software is being tried no matter how nonsensical. It's like everybody is simultaneously brute-forcing a combination lock. To me, I would think there is negative synergy with combining a UI framework like Svelte, with htmx's replacement abilities. One of the value props of htmx is that you don't need to use a framework like Svelte, I don't quite see the point in combining them.

yewenjie 4y ago

I would really appreciate if there is a Why <New hot framework> section in the homepage of such new hot frameworks.

yawnxyz 4y ago

Is this supposed to be a smaller Sveltekit alternative? I'm confused as to what it adds to the ecosystem

3535546hhh73 4y ago

Nmkik B