Emphatically, no. These are industrial experiments, in a similar vein to various Canola oils etc. We have things much worse than aspartame. A chemical byproduct of sucralose known as sucralose-6-acetate has been identified as highly genotoxic, meaning it breaks down DNA and may increase cancer risks. Found in common sucralose-based sweeteners, it causes a "leaky gut" by damaging intestinal walls and poses serious health risks, even at low, allowed consumption levels. https://www.medicalnewstoday.com/articles/a-chemical-found-in-common-artificial-sweetener-may-cause-dna-damage-cancer Heart Attacks (Erythritol): The sweetener erythritol, common in "keto-friendly" drinks, has been linked to increased blood clotting, potentially doubling the risk of heart attack or stroke. https://www.aarp.org/health/conditions-treatments/are-artificial-sweeteners-bad-for-you/ However, high levels of fructose have been engineered in many formerly natural foods, which is also dangerous (though far less so). https://www.reddit.com/r/todayilearned/comments/13ecikd/til_modern_fruit_is_becoming_too_sweet_for_zoo/ Sugar-free drinks are increasingly linked to serious health risks, with studies suggesting they are not harmless alternatives. Key concerns include a 20% higher risk of AFib (irregular heartbeat), increased stroke and cardiovascular disease risks, and potential links to type 2 diabetes. They may also trigger digestive issues, gut microbiome disruption, and tooth decay. Xylitol and Stevia may be exceptions, but they are also more naturally occurring.
↙ time adjusted for second-chance
Most people can't juggle one ball (lesswrong.com)
Hey all, Boris from the Claude Code team here. We've been investigating these reports, and a few of the top issues we've found are: 1. Prompt cache misses when using 1M token context window are expensive. Since Claude Code uses a 1 hour prompt cache window for the main agent, if you leave your computer for over an hour then continue a stale session, it's often a full cache miss. To improve this, we have shipped a few UX improvements (eg. to nudge you to /clear before continuing a long stale session), and are investigating defaulting to 400k context instead, with an option to configure your context window to up to 1M if preferred. To experiment with this now, try: CLAUDE_CODE_AUTO_COMPACT_WINDOW=400000 claude. 2. People pulling in a large number of skills, or running many agents or background automations, which sometimes happens when using a large number of plugins. This was the case for a surprisingly large number of users, and we are actively working on (a) improving the UX to make these cases more visible to users and (b) more intelligently truncating, pruning, and scheduling non-main tasks to avoid surprise token usage. In the process, we ruled out a large number of hypotheses: adaptive thinking, other kinds of harness regressions, model and inference regressions. We are continuing to investigate and prioritize this. The most actionable thing for people running into this is to run /feedback, and optionally post the feedback ids either here or in the Github issue. That makes it possible for us to debug specific reports.
Well, and worse, Windows was itself a hive of inconsistency. The most obvious example of UI consistency failing as an idea was that Microsoft's own teams didn't care about it at all. People my age always have rose tinted glasses about this. Even the screenshot of Word the author chose is telling because Office rolled its own widget toolkit. No other Windows apps had menus that looked like that, with the stripe down the left hand side, or that kind of redundant menu-duplicating sidebar. They made many other apps that ignored or duplicated core UI paradigms too. Visual Studio, Encarta, Windows Media Player... the list went on and on. The Windows I remember was in some ways actually less consistent than what we have now. It was common for apps to be themeable, to use weirdly shaped windows, to have very different icon themes or button colors, etc. Every app developer wanted to have a strong brand, which meant not using the default UI choices. And Microsoft's UI guidelines weren't strong enough to generate consistency - even basic things like where the settings window could be found weren't consistent. Sometimes it was Edit > Preferences. Sometimes File > Settings. Sometimes zooming was under View, sometimes under Window. The big problem with the web and the newer web-derived mobile paradigms is the conflation between theme and widget library, under the name "design system". The native desktop era was relatively good at keeping these concepts separated but the web isn't, the result is a morass of very low effort and crappy widgets that often fail at the subtle details MS/Apple got right. And browsers can't help because every other year designers decide that the basic behaviors of e.g. text fields needs to change in ways that wouldn't be supported by the browser's own widgets.
 Top