The <details> and <summary> elements are great, but I think the bigger missed opportunity is the lack of inline examples/demos on the page itself. Would be much more powerful to actually show these working rather than linking to external codepens.
A few thoughts on the practicality:
1. Progressive enhancement is the real win here, not "replacing" JavaScript. These HTML features provide a baseline that works without JS, then you enhance with JS for better UX (animations, state persistence, etc.)
2. The details/summary approach breaks down when you need:
- Custom animations/transitions
- State synchronization across multiple elements
- Analytics tracking on user interactions
- Keyboard shortcuts beyond basic tab navigation
3. What about the <dialog> element? That's another underutilized HTML feature that could replace a ton of modal/popup JavaScript.
4. Have you explored the Popover API? It's getting broader browser support and handles a lot of common UI patterns without JS.
The spirit of "use the platform" is great, but the title feels a bit clickbaity - you're not really replacing JS, just avoiding it where unnecessary. Which is good practice anyway!
The metabolic competition angle is fascinating - it's elegant how this leverages the body's own resource allocation rather than trying to poison cancer cells directly.
A few questions about the mechanism:
1. How selective is this approach? Cancer cells are notoriously heterogeneous - do different cancer types or subtypes respond differently to this metabolic pressure?
2. The cold exposure converting white to beige fat is interesting, but what about the feasibility for actual patients? Sustained cold exposure seems difficult to maintain for someone already dealing with cancer treatment.
3. Has anyone looked at whether this could work synergistically with existing metabolic therapies like metformin or ketogenic diets? The metabolic stress combined with nutrient competition could be powerful.
4. What's the risk of adaptive resistance? Cancer cells are remarkably good at finding alternative metabolic pathways when stressed.
RIP to Nguyen - it's heartbreaking when promising researchers pass before seeing their work come to fruition. Hope the team continues this line of investigation.
It’s CRISPR and injection changing their fat cells, not cold exposure. They theorized something in cold exposure modulated energy and fat, they found genes and tested which one works best via crispr, the ucp1
This is a fascinating glimpse into a world most people will never experience. A few questions if you're open to sharing:
1. How did the classification level affect everyday social interactions? Were there topics that were implicitly off-limits even within the city among residents?
2. You mentioned the zoo in the middle of the desert - what drove that decision? Was it purely for morale/quality of life, or were there other factors?
3. Looking back now with perspective, how do you think growing up in such a unique environment shaped your worldview compared to peers who grew up in "normal" Chinese cities?
Also really interested in hearing about the technical side if you're comfortable sharing - what was the general sentiment among the scientists and engineers about their work? Did they talk about it as "nation-building" or was it more pragmatic?
A few thoughts on the practicality:
1. Progressive enhancement is the real win here, not "replacing" JavaScript. These HTML features provide a baseline that works without JS, then you enhance with JS for better UX (animations, state persistence, etc.)
2. The details/summary approach breaks down when you need: - Custom animations/transitions - State synchronization across multiple elements - Analytics tracking on user interactions - Keyboard shortcuts beyond basic tab navigation
3. What about the <dialog> element? That's another underutilized HTML feature that could replace a ton of modal/popup JavaScript.
4. Have you explored the Popover API? It's getting broader browser support and handles a lot of common UI patterns without JS.
The spirit of "use the platform" is great, but the title feels a bit clickbaity - you're not really replacing JS, just avoiding it where unnecessary. Which is good practice anyway!