3 ms·
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 pri
by Mizza 1y ago
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.
- Alifatisk 1y agoI can't use Phoenix with Rails now, can I?
- nchmy 1y agoWhat here has been reinvented? There's nothing out there like datastar. Htmx + alpine is similar, but much heavier and less functional. 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.
- hasanhaja 1y agoSimple features? Making those imperative APIs declarative is not very simple for me, but you're welcome to not use those features and write them yourself. A couple of things on the Phoenix point: - Requires the adoption of Elixir and Datastar is backend agnostic - Adopting Phoenix feels more suited to greenfield projects, but Datastar is suited for that and brownfield ones. - Websockets vs Server Sent Events has been really interesting and nuanced
- TeddyDD 1y agoIn what specific areas Phoenix Live View is so far ahead? Do you mind elaborating? The unfortunate disadvantage of Live View is that you need to write Elixir. A lovely language, but it would be hard to sell in company that use only <SOME_LANGUAGE>. The hypermedia libraries like d* and htmx can be used with any backend.