dalkur

> There is a very good chance that someone is writing a reply with some suggestion as to how I should eat so that I'm not hungry. Thank you for the thoughts, but realize that you don't live in my body, you don't know how I feel, you don't know what I've tried.

I completely agree with this. I still do want to chime in a little. Don't feel obligated to try any of this, maybe you have already tried. I have a hunch you've tried it already. Perhaps someone else hasn't and will try upon reading it.

One rather simple change in diet is volume eating. As in, eat food that fills your stomach, but does not contain (many) calories. A prime example is lettuce, broccoli, or practically any vegetable.

When you're hungry try eating a large salad (a clean one that is, no sauces, or oil). When eating dinner add a large portion of broccoli, raw spinach, cauliflower. Try grilling or steaming vegetables.

In normal dishes try and replace as many ingredients with lower calorie alternatives, especially oils when cooking. These calories add up, quickly.

The above doesn't mean you cannot eat heavier sources of protein, fats, and carbs. Please just keep eating those, in balance. In balance meaning there's no need to have more grams of fats per day than a healthy weight in kg (e.g. 80kg -> 80 grams). Same story for proteins, but at a moderate ratio of 1-1.6 grams per kg body weight. Feel free to play with carbs.

> Hunger sounds like a problem to people. Hunger feels like a problem inside the body. People still tell me I shouldn't be hungry. Maybe part of the solution is realizing that eating to satisfaction is ... bad for some people. Maybe it's Ok to be a little hungry.

Strong agree with this. Funnily enough it's often thirst, which feels similar.

Depending on the research it is around 1.6 to 2.2 grams of protein per kg body weight. [1][2][3]

[1] https://www.ncbi.nlm.nih.gov/pubmed/29497353 [2] https://www.ncbi.nlm.nih.gov/pubmed/22150425 [3] https://www.ncbi.nlm.nih.gov/pubmed/19927027/

I wholeheartedly agree with you. That would be the ideal solution, because the browser is already doing the passes over the CSS rules.

I've done something similar nearly two years ago[1]. The problem is rather difficult, especially with all the JavaScript frameworks in existence right now. I've tried to build a state machine for handling those frameworks but never got around to finishing it. There's basically and endless amount of combinations one can do, thus you probably want to limit depth or something. You also have to be able to detect ::after and similar kind of selectors, which isn't always straightforward with querySelector and needs quite a bit of cleaning. I ran into a few other (edge) cases, which I cannot remember right now.

Nonetheless, it is a challenging and fun problem to solve.

[1]: https://github.com/Kevin-A/css-detector

Somewhat of shame that his decision is based on the applicant's grammar while he makes a few bad mistakes himself.