Per the FDA, caffeine in amounts under 400mg/day is not generally associated with harmful effects for healthy adults. The largest option for this drink (30oz) has 390mg. It’s not remotely high enough to kill unless you have a heart problem or other severe abnormal caffeine sensitivity. It is clearly labeled as having as much caffeine as coffee. Similarly to how products with peanuts are labelled as “contains nuts,” not “contains enough peanuts to kill you.”
The 30oz size has 390mg caffeine. The FDA says 400mg a day is not generally associated with harmful effects for adults without heart conditions etc. If the FDA says up to 400mg is fine, I don’t think it’s fair to call that the “danger threshold.” That’s like calling the speed limit the “danger threshold.” It’s set there for a reason, but you don’t go from “no adverse effects” to “danger” as soon as you cross the line.
It’s advertised as having the same amount of caffeine as their coffee. 30oz of coffee is a pretty significant amount. Not typically dangerous, but hardly something you can drink by accident.
I’m surprised, I would love to work in Java 20. Do you have any particular pain points with it? Or is it just that you’d rather be using something else?
I still can’t use WSL 2.0 because of the abysmal filesystem performance compared to 1.0. As far as I can tell this is a fundamental flaw with the design, not a bug that can/will be fixed.
If you install config files to the new location and prefer the new config file location over the old, you risk accidental misconfiguration when a system has both config files (e.g. in a build pipeline that installs the software and then copies the config to the old location). It is not impossible to solve, but there are questions that require some care if you have a large userbase and solidified codebase. More care than it takes to do it right the first time.