

I gotta admit I’m a bit confused because none of the articles posted here - articles made specifically to talk about if rice is safe - seem to be aware of fried rice syndrome? The thing that is such a thing that it got an own name?
The danger about fried rice syndrome is that it is unnoticeable. Meat goes bad, it stinks or gets white dots, etc. Fried rice syndrome, it doesn’t appear different at all and you can just straight up die from it. Restaurants only make rice fresh because of this danger.
But restaurants are extra careful, of course. At home, if you make sure to cool your rice quickly it’s ok. Which also means, don’t put one huge bowl of warm rice I to your fridge, because it will stay warm enough for the bacteria in the middle.
It’s also one if those things that doesn’t happen often, so there’s a chance you go through your whole life without this ever being a problem, but I don’t wanna die from bowl of rice.









I got the same feeling that it shouldn’t be rocket science. Then again, I’m most experienced with C#, which is just a very clean and professional ecosystem, and I often experience that other languages can feel rough around the edges in comparison. E.g. in npm JS, different package managers create entirely different folder structures, even though the build system is 100% the same!
So maybe a package manager for C# would be straightforward, while npm JS would require a bunch of research about what happens behind the scenes.
And if other languages are similar to npm JS, it’s easy to imagine that your want to keep languages separated for cleanliness - but then you kinda just get a bunch of one-language-package managers in a trenchcoat, so why even bother. OR you have the same code handling it all, becoming a bit of a mess.