Me, looking at that 1-line file, wondering if 0-line files can exist

(Give me a break, haven't had my coffee yet today)

How do you feel about the Cascade Cup? And no, I don’t mean the Cascadia Cup. 🤓

Sorry, that prize cannot be given, it can only be bought.

Coffee, bourbon, flannel, soft pants, gripper slippers, WFH fireplace work sessions and lunch break baths, happy light, walk outside every day regardless of weather, 3 day weekend trips, Hawaii mid-winter break, and always looking for new coping mechanisms.

Awkward place for a … truncation

If it wasn’t clear, the above was meant humorously. Obviously there’s a false dichotomy here. We should fix our JS AND plant trees.

There’s also substantial benefits beyond net atmospheric CO2 to eliminating unnecessary JS — like websites and apps that are actually pleasant to use, save time, …

Unfortunately (fortunately?), at scale it costs about $1 to plant 1 tree, so clearly easier to plant trees than fix JS, at scale. But another way to look at it: fixing our JS would net eliminate jobs and planting trees is a job creator, so choosing JS over trees would be a 2x swing against jobs.

1. Become president
2. Commit acts of domestic terrorism
3. Not get penalized in the slightest
4. Realize you can do anything you want without consequences

I was going the guess The Cheesemonger’s Shop in Leavenworth. I was way off, but would recommend

WSL for sure: faster, more familiar terminal commends, fewer random windows-specific issues, and you can run multiple instances to keep environments for each project separated. VS Code also works great with WSL

Well deserved!

Someone should make some sort of Open AUTHentication system to link accounts across services

What app is this or do you have a codepen/sandbox? Experience is looking great!

- less storage space consumed on device
- can be accessed from borrowed/shared devices without installing anything

- always the latest version with the newest features and fixes
- bring your own browser, with your extensions
- no censorship, no app takedowns from political pressure
- no installation required, instant access via link
[continued…]

I agree the browser’s behavior is annoying, but I’m also glad ad banners can’t pop up share dialogs whenever they want.

Also, you can progressively-dehance here: try the API and only if it fails do you present UX that requires a second interaction.

Also: pre-fetch on idle (if responsible, depends on your UX and application) or on hover/focus. That may tighten up the delay enough to work most of the time.

Hard to tell what the UX looks like from the snippet, but with a fetch between the user interaction and the share feedback, it might benefit from a loading state with a cheerful “okay it’s ready now!” sort of dilly.