41–50 of 298 posts
This post and other posts about datastar on the hn frontpage seem unnatural to me. It's like a marketing effort to astroturf this, especially with newly created accounts interacting with this...
Reinventing the wheel and then charging for simple features? If this paradigm excites you, just use Phoenix, dawg. It's so far ahead, everything else feels primitive.
Earlier quoted context omitted.
What more do you need than writing something like `data-on-input__debounce.200ms="@get('/examples/active_search/search')"` in the DOM as being crazy and wrong?
So your answers is no, you cannot provide any arguments.
For those of you who don't think Datastar is good enough for realtime/collaborative/multiplayer and/or think you need any of the PRO features. These three demos each run on a 5$ VPS and don't use any of the PRO features. They have all survived the front page of HN. Datastar is a fantastic piece of engineering. - https://checkboxes.andersmurphy.com/ - https://cells.andersmurphy.com/ - https://example.andersmurphy.com/…
Right but this says “bring your own backend” in big letters on the splash page. So surviving HN isn’t really something Datastar is doing here.
This post and other posts about datastar on the hn frontpage seem unnatural to me. It's like a marketing effort to astroturf this, especially with newly created accounts interacting with this...
It isn't mentioned on the homepage, but Datastar does charge for the following features: data-animate - Animates element attributes over time. data-custom-validity - Adds custom validity to an element. data-on-raf - Runs an expression on every animation frame. data-on-resize - Runs an expression on element resize. data-persist - Persists signals in local storage. data-query-string - Syncs query string params with sig…
not sure i think this is a good way to fund their work BUT exploring models to make open-source sustainable for the developers does seem like a good thing, no?
In the case of a web framework, that choice is a bit difficult. But if the software is fully functional for the large majority of users, then charging for niche features, or those that are actively discouraged, sounds like a fair approach to me.
Earlier quoted context omitted.
Isn't that the whole point of hypermedia frameworks like Datastar and HTMX? It's to extend the declarativeness of HTML. If you don't like the syntax, that's your preference. But I'm curious to hear why this is "wrong". Since that's a more objective thing, we can discuss it
Because it's a mish-mash of different ad-hoc DSLs. You have a DSL based on data-* attributes But then some attributes get this weird syntax-ish extension Then some of those attributes accept a Datastar expressions DSL: https://data-star.dev/guide/datastar_expressions So you can have data-on-click__debounce.200ms="$landingGearRetracted && @post('/launch')" Which is just bad design
Earlier quoted context omitted.
Could provide actual arguments for why these aspects of Datastar are "crazy", "even more crazy" and "wrong"?
What more do you need than writing something like `data-on-input__debounce.200ms="@get('/examples/active_search/search')"` in the DOM as being crazy and wrong?
This post and other posts about datastar on the hn frontpage seem unnatural to me. It's like a marketing effort to astroturf this, especially with newly created accounts interacting with this...
Reinventing the wheel and then charging for simple features? If this paradigm excites you, just use Phoenix, dawg. It's so far ahead, everything else feels primitive.
And God forbid someone try to make open source sustainable by charging for largely-unnecessary functionality and actively dissuading you from buying it - as the devs do regularly in their discord.
And phoenix doesn't work with ANY backend language or framework.