It's a good thing you edited for politeness because you seemed to be basing your understanding of what I said based on stuff you read on Reddit.
A number of studies show that, in humans, the keto diet (the medical keto diet[1] and not the meat heavy Internet version) causes metabolic stress in breast cancer cells and in several other types of cancer, due to their significantly increased metabolic needs. It's like the difference between a normal human and Michael Phelps during Olympic competition. The cancer cells can process ketones, but not efficiently enough to fuel their activity so they starve.
In humans this eventually results in the death or deactivation of the cancerous cells (deactivation being the primary way that tumors "adapt" to a starvation diet). There have been few, if any, reported cases of metastasis in the types of cancers studied in humans. This outcome is statistically significant enough that multiple cancer treatment centers recommend the medical keto diet to human patients as part of a treatment regime.
As mentioned, the recent study from 2024 shows that this type of metabolic stress can, in mice cause the cancerous cells to metastasize in a last-ditch attempt to survive. However, very little of the cancer research conducted on mice has applications to human cancers. For example, chemotherapy has also been shown to cause metastasis in mice, and a number of earlier studies attempting to replicate the keto research in humans shows that the keto diet in mice increases tumor growth, which is the opposite effect it has in humans.
[1] The medical keto diet is basically just fat and vitamins. No carbs, and minimal to no protein because protein can get converted into glucose by gluconeogenesis. It is not a diet anyone would want to be on longer than strictly necessary. One of my friends had stage 4 metastatic lung cancer, which she discovered during a company-sponsored mud run. Surgery was not an option and chemotherapy was not working. With less than 4 months to live, she went on the medical keto diet and the two-punch combo of keto and chemo put the cancer into remission for almost three years. (Note: She only maintained the diet for a few months after ending chemo treatment. Unfortunately not all of the cancer cells had died, some had merely deactivated. Four years after remission the cancer cells reactivated with a vengeance and she died the day after she started showing symptoms.)
I like lit. I'm not primarily a web developer and I've found it intuitive and easy to read and write. What I find more confusing than frameworks is building, bundling, ES modules, the whole NPM ecosystem.
>building, bundling, ES modules, the whole NPM ecosystem.
That's evolved hand in hand with the React monoculture over the past 10-15 years, maybe by way of a project called Babel.
Babel set out to provide progressive enhancement for the original ES5 to ES6 migration, and then in classic POSIWID fashion began to thrive on a suite of a la carte incompatibilities.
That experience is as much a contributor to the current automatism to to reach for (non-configurable) Prettier and Eslint, or more, than any rogue devs imposing fell coding styles.
So yeah, plenty of things in JS infra that look like they've been designed to be a pain in the ass (a.k.a. "behavioral nudge", towards TS, what else) and very much seem like the result of more inept moat-building in the then-newly ballooning field of frontend dev.
Readers might look up whan an import map is sometime, as well as where it is and isn't supported. How TS handled ES modules at the time Node16 changed their ESM support. Does ESM `default` correspond to CJS `module` or `module.exports`? Room for vendors to fuck up in innovative ways all round, this whole rotten ecosystem.
Readers are also advised to try Deno if they haven't yet. On Node, try Vite instead of Webpack. Most importantly, try Lit with JS, import map, no builder/bundler, and test suite with coverage. Work out what is most comfortable for you, work out exactly how much toolchain makes you the most productive, and afterwards don't forget to ask yourself why the React cultists want to stick everyone in a hairshirt if not a straitjacket.
In any city the shortest distance in total time spent is by bike.
Even if it is widely dangerous to do so (most american cities i've ever visited)
You can hem and haw - but its pretty bang on
When you then add finding parking at the ends of your trip to it it is crazyly more efficient timewise.
Now even copenhagen denmark has rain causing many more to take a car or public transport (that works).
But it is very clear that the time argument is simply not true.
Now you can argue convenience at the start of the trip vs agony in the end (finding that parking space)
Or for "need to lug an ikea sofa across time"
Or even for "my kids and familiy needs to go as well"
That's super fine, and all true - but 70-80% of ALL trips in cars are by 1 person sitting in 1 car.
So moving just 10% of car users to alternate means free up a tremendous amount of space in the city.
I love my car, my bikes and my public transports and each does something nice for me - but seriously do you think cities like l.a. are even livable on a human scale - people don't even walk if the distance is over 1000meters.
I certainly agree with the idea of "uhm lets try to plan for otherthings than cars going forward"
I've done the same for a multinational with 1000 franchises-like subcompanies - trying to get them to conform to horizontal guidance.
It is an impossible task, noone takes it that serious and are focused on imminent kpi and okr's.
My only success has been internal reviews of wcag compliance and the threat of fines if found lacking.
But for non digital design its embarrassingly hard
React and the most commonly used pattern inherently promotes an way to complex html
Node structure and shitty css, especially if stuff like tailwind is used.
Now you CAN so it so that is not the case, but tbh i have never seen that in the wild -
Lol. If anything, Tailwind isn't shitty CSS (because it's a very limited number of classes) unlike the gazillion one-off classes that CSS-in-JS or even BEM encourages
Cancer metabolism isn’t a 2-bit meme. Tumors adapt. If they couldn’t, they wouldn’t metastasize.
reply