4 ms·

> You could follow something like this: https://learn.svelte.dev/tutorial/welcome-to-svelte https://learn.svelte.dev/tutorial/welcome-to-svelte I think if you

by trog 3y ago

> You could follow something like this: https://learn.svelte.dev/tutorial/welcome-to-svelte https://learn.svelte.dev/tutorial/welcome-to-svelte I think if you are, like me, someone who for various reasons never followed the JavaScript ecosystem for various reasons over the last few years (in my case because I was working on exclusively backend APIs in C#), coming back into trying to do any frontend website is just ten thousand people saying "it's not that hard, just follow something like this: x", where 'x' is any one of forfty hundred humungous different frameworks. If you don't want to have to learn a whole new ecosystem but just want to bang out something that can take advantage of a bunch of modern-ish nice front end paradigms like being able to selectively update individual components without having to do a full page reload then htmx feels like it would hit the spot for a lot of different use cases. (I say this having only read the site several times, usually when it pops up here in some context, and I always think "oh damn yeh that thing exists, I have to give it a go at some point!" but never actually have yet)

benatkin 3y ago
I doubt it – I haven't seen any indication of HTMX being a silver bullet. Here's your list of examples: https://htmx.org/examples/ https://htmx.org/examples/ Here's validation: https://htmx.org/docs/#validation-example https://htmx.org/docs/#validation-example It looks kinda like ruby.
- user32456 3y ago
  I'd argue that neither is any particular JS framework a silver bullet. If HTMX works for their use cases without needing to write any JS then more power to them!
- renerick 3y ago
  It is explicitly NOT a silver bullet https://htmx.org/essays/when-to-use-hypermedia/#hypermedia-not-a-good-fit-if https://htmx.org/essays/when-to-use-hypermedia/#hypermedia-n...
  - benatkin 3y ago
    I'd like to point out that if you require offline functionality in one project that it likely isn't a good fit for your other project that doesn't require offline functionality. We all have finite time and it's great to learn something once and be able to use it multiple times.
    - renerick 3y ago
      Offline functionality naturally requires client-side code to handle storage, caching, synchronization etc, so client oriented frameworks are preferable in those scenarios. However, this comes at the cost of additional complexity, and I argue that this complexity may be unnecessary and htmx may help you achieve your goals easier You said it yourself: > We all have finite time and it's great to learn something once and be able to use it multiple times. We all have finite time and it's great to use tools that help us work efficiently, following the strengths of those tools, instead of having to maintain unnecessarily complex solutions
egeozcan 3y ago
htmx is yet another one of those forty hundred humongous different frameworks. It also uses a DSL that has no application outside of its specific corner. It also forces you to return HTML fragments via AJAX. By the way I did use intercooler.js (prev. iteration of htmx) intensively and while I liked it at first, it really added up to being an HTML/JS soup when other developers started extending.
- elchief 3y ago
  > humongous 14kb > It also forces you to return HTML fragments via AJAX. not true, you can return anything. support client-side templating for JSON etc

by trog 3y ago

benatkin 3y ago

I doubt it – I haven't seen any indication of HTMX being a silver bullet. Here's your list of examples: https://htmx.org/examples/ https://htmx.org/examples/ Here's validation: https://htmx.org/docs/#validation-example https://htmx.org/docs/#validation-example It looks kinda like ruby.

user32456 3y ago
I'd argue that neither is any particular JS framework a silver bullet. If HTMX works for their use cases without needing to write any JS then more power to them!
renerick 3y ago
It is explicitly NOT a silver bullet https://htmx.org/essays/when-to-use-hypermedia/#hypermedia-not-a-good-fit-if https://htmx.org/essays/when-to-use-hypermedia/#hypermedia-n...
- benatkin 3y ago
  I'd like to point out that if you require offline functionality in one project that it likely isn't a good fit for your other project that doesn't require offline functionality. We all have finite time and it's great to learn something once and be able to use it multiple times.
  - renerick 3y ago
    Offline functionality naturally requires client-side code to handle storage, caching, synchronization etc, so client oriented frameworks are preferable in those scenarios. However, this comes at the cost of additional complexity, and I argue that this complexity may be unnecessary and htmx may help you achieve your goals easier You said it yourself: > We all have finite time and it's great to learn something once and be able to use it multiple times. We all have finite time and it's great to use tools that help us work efficiently, following the strengths of those tools, instead of having to maintain unnecessarily complex solutions

egeozcan 3y ago

htmx is yet another one of those forty hundred humongous different frameworks. It also uses a DSL that has no application outside of its specific corner. It also forces you to return HTML fragments via AJAX. By the way I did use intercooler.js (prev. iteration of htmx) intensively and while I liked it at first, it really added up to being an HTML/JS soup when other developers started extending.

elchief 3y ago
> humongous 14kb > It also forces you to return HTML fragments via AJAX. not true, you can return anything. support client-side templating for JSON etc