129 karma · joined April 12, 2024
Perhaps is the better link. It talks about the perks.
The take the money one has been done (Beeminder, and others probably), but sure different flavours are welcome.
The split with friends I haven't seen. That would be pretty cool, especially if you can do it without needing to pay banks a txn fee, or perhaps a tiny one (maybe you take a 5% of profits fee from participents, or similar). Crypto is the other option (!).
The split with friends is great becuase
* People less likely to lie to friends than a SaaS. Which is good for both parties.
* Social motivation and financial motivation.
* If you lose it's like losing a game of poker with mates, not a big deal (as long as you kept the stakes reasonable).
https://www.health.harvard.edu/staying-healthy/can-mouth-tap....
I remember the first meme like presentations back in 2002 at work and I hated it. It's like stop learning, now you have to find this picture funny (maybe it was some star wars reference, and I haven't watched them), and we will get back to it. It was cringe!
On the other side of the scale, React has overheads like a virtual dom.
It is a complicated question as to what is most performant, who bares that cost, and so on.
However a a developer or team, if you say "this page only includes the HTMX library and no other scripts" (something that is easy to verify) then you know a lot about what can and can't happen.
In a sense HTMX is a framework that provides a non-turing complete DSL with limited interactions.
Whereas React alone provides... well nothing, because it isn't a framework. You need JS to initiate it, and do anything with it at all! So a React app by extension must have a lot (or maybe a little, rarely) custom Turing-complete code with access to the entire operating system that is the Web API!
(I appreciate that people's definition of Framework vs. Library will differ, but the main point stands that React requires a decent chunk of turing complete code to do anything useful, whereas HTMX requires no turing complete code on the client but just markup.)
Where the application is doing lots of micro-level stuff, like maybe you are drawing on a canvas and occasionally sending a payload of updates to a server, I think then HTMX would be much slower and clunkier, and that is when you dust off your React.