I haven't had bandwidth to explore the implementation deeply yet, but this seems almost too relevant:
"Working in Elevators: Offline-Enabled Realtime Apps with LiveView, Svelte, & Y.js"
Your course has been fantastic to work through, please keep up the great work (also saw you just launched a companion deep-dive on Phoenix forms, congrats!)
- not affiliated, just a humble enjoyer of Arrowsmith Labs materials
That doesn't really say anything about alcohol's effect on (non-dementia related) mental clarity and sleep.
Also if you continue to read that meta-analysis beyond the sentence you linked to it seems that much larger studies did not find a correlation between reduced dementia risk and moderate alcohol consumption. In fact they found that high alcohol consumption was associated with significantly higher risk of dementia. The overall conclusion of the analysis was "Available epidemiological studies are not sufficient to verify a protective effect of alcohol on dementia development."
Dementia seems highly related, if not inversely synonymous, with mental clarity? I think your comment is a bit misleading - while it does seem clearer that _high_ alcohol consumption and alcohol "use-disorders" are correlated with elevated risk of dementia, results pertaining to light-to-moderate consumption are "heterogeneous" - I read 4 studies or meta-studies with results showing _decreased_ risk of dementia (Rotterdam, Whitehall-II, Anstey, Xhu), 2 showing no correlation (California, HUNT), and zero showing increased risk when it comes to light-to-moderate consumption. Anyone interested should of course read the linked text in full and draw their own conclusions.
Just wanted to say thank you for this comment, fascinating and perfect example of the beauty of HN. Relatively fresh off The Making of the Atomic Bomb and while fusion was not at all a focus, this (incomplete) impression is exactly what I came away with.
Is there any chance you'd recommend any books related to these topics? The walk through decades of revelations in physics was the most enjoyable aspect of that book, I'd love to continue building on that story.
Well if you liked "The Making of the Atomic Bomb" I can strongly recommend the follow up "Dark Sun" that covers both the Soviet atomic bomb program and the development of the H-bomb by the US.
Not sure how I missed that Rhodes wrote a continuation! The clarity of writing about physics for a layperson has been wonderful, glad to find there's more. Much appreciated.
One of the points I took away from that book being that "H-bomb" weapon design is as much about fission as fusion - most designs being fission-fusion-fission with most energy coming from the latter fission stage.
That book is absolutely great. As the sibling comment mentions, the Dark Sun is also great.
Here are some more books I read on this topic. One was written by someone who was very close to the Ulam and Teller inner circle: "Building the H Bomb" by Kenn Ford. Another one is "Sun in a Bottle: The Strange History of Fusion and the Science of Wishful Thinking" by Charles Seife. And finally, you can't go wrong with any book written by James Mahaffey.
Seconded, love the ability to take it camping (car, the thing weighs a ton) along with a c40, and use standard-size baskets. Current favorite is a big bang[1] which leads to a very different resulting espresso than the stock basket - both great!
Couldn't agree more. We've been having good luck working with TSX-templated Vue components (using "render functions"[1]) after getting fed up with gaps in VTI back in the day – most of https://radiopaper.com is built in this way and we're closing in on it all being so. We haven't run into any issues with Vue's (alleged) lack of ability to optimize TSX templates in certain ways as opposed to traditional Vue templates – maybe comes down to the nature of our use cases – but our view is that this trades off against many other benefits:
- File extensions are all .tsx, and thus work with bog-standard editor tooling and syntax highlighting
- We're more confident about typechecking in templates, because template code is 1 minor transformation away from raw typescript, and basic `tsc` has understood TSX well for years now. Up and down the component stack, it feels like we understand typings better without "gaps" at each template layer.
- Scoping of values in templates is easier to understand. Everything you write is what it says it is, it's just whatever's in the same scope as the template. There are no transformations, no omissions of various words, no magic.
- It's easier to compose templates from small easy-to-understand parts in the same file, without fragmenting code across many small components. Not everything needs to live in a `<template>` tag separate from your `<script>` tag.
- When React folks have joined the team they've had no problem ramping up.
- By the way, in Vue TSX you just say "class" not "className" which is refreshing.
Feel free to email me at evan at radiopaper dot com if any of this interests you – we're currently working on expanding the team and looking for like-minded people interested in contributing.
Hi Evan! That sounds really interesting! Would you have a short code example for me, demonstrating what your typical Vue component looks like? Is it similar to the examples at the end of https://vuejs.org/guide/extras/render-function.html ?
I'd also be interested in how you write (S)CSS for your components – do you use some form of CSS-in-JS?
CSS-in-JS has been a challenge – we're currently using https://github.com/astroturfcss/astroturf which seemed the simplest zero-runtime-cost option back when we were looking, but the library is starting to feel a bit under-maintained (if the author of Astroturf reads this, we love your work and will do whatever we can to support you in it!). But it's worked well for us over the last 2 years.
Happy to share a component example. We also use a small library for managing CSS classes in a typed fashion, which can also be used by our UI test code to target various elements. So that does add a bit of cryptic boilerplate, but the repo README has an example component with syntax highlighting:
https://github.com/evnp/namespace.style#usage
MIT licensed work still requires attribution, which (as far as I know) current AI models / training practices are unable to handle properly. From the MIT license text:
> The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
> In PowerShell, structured output is the default and it seems to work very well. This is probably too far for Unix/Linux, but a standard "--json" flag would go a long way to getting the same benefits.
OP has a blog post[0] which describes exactly this. `jc` is described as a tool to fill this role "in the meantime" -- my reading is that it's intended to serve as a stepping stone towards widespread `-j`/`--json` support across unix tools.
If there is to be a push to add structured data to all the unix tools, I wish they would use a format that allows embedding binary data. Yes base64 is an option, but it suffers from the issue that base64(base64(base64(data))) leads to exponential overhead.
https://liveview-svelte-pwa.fly.dev/
reply