90 karma · joined February 20, 2023
I would be really curious to know what tools you've tried and are using where gemini feels better to use
Could this be in the opposite direction, where the richer you are, the less you need to work?
The documentation itself is so full of implementation details that, as someone who is interested in the concept of this, I'm scared off even trying to setup and use this
The project would be much more approachable if there was a simple native installer. My parents could also benefit from this but there's no way they would ever even understand how to install this, much less troubleshoot docker things.
However I do know that it moved the needle significantly in _my_ life by changing my relationship with food so it's valuable to me. Losing the extra ~10 to 20 lbs of weight people gain in adulthood is something that people do struggle with even if it's not as dramatic as someone fighting obesity.
- When at a dinner with family or friends, I never _have_ to finish something. Most of the time the host will be happy to package my leftovers to take back home when asked. That last part makes it clear that I like and appreciate the food even through I didn't finish it in the moment.
- If I buy food at a restaurant, I don't have an obligation to finish it to get my moneys worth. And again, I can just save it for another meal if I want.
- I don't have to eat snacks just because the host put them on a table at a party.
For some reason our brains think that just because food is _there_ we need to eat it, but that's generally not true.
const fn get_outer_height() -> Result<SomeErrorType, WeakReference<Number>>
- `const` makes it clear this doesn't mutate
- the function name says exactly what it does
- The return type makes it clear it can return an error
- The return value is typed in a way that makes it clear what the ownership is
Throw in a language like Rust that gives guarantees about thread safety and now the only thing left is if the API is stable or not. Which I would argue doesn't matter much at all since people will still end up depending on it regardless of the comment saying "This API might not be stable"
And the best part? My definition will never get outdated. If the assumptions change, the definition will also need to change (well, except for maybe the name)
I'll keep using it for a bit to give it a fair shot however since I can imagine the split pane being super useful in certain cases.
I get people don't like classes / templates / .. but there isn't any reason one has to use those.