Boards of Canada

Mr. Robot Original Soundtrack

They used to have a “Dr. Paul's Raw Animal-Based Smoothie” that I looooved, but unfortunately they stopped making it. Still sad about that one :(

Yabai supports this perfectly (especially combined with instant, animation-free space switching) but it requires disabling system integrity protection--which is a non-starter on a work computer.

Aerospace solves it with their own spaces implementation.

I was able to put together a hammerspoon script that does the job decently enough for my purposes: https://gist.github.com/kcrwfrd/6f3dcaec0e08e0e77b2884588a34...

It looks like a nice display, but that’s a deal killer for me.

I like that I can have some vaults that sync to both my personal and work laptops and other vaults that only sync to one or the other.

It’s awfully convenient without any vendor lock in since I can just take my plain markdown files and leave anytime.

The Navigation API has landed in the newest versions of all the modern browsers, and supersedes the older History API with some much-needed improvements for developing single-page applications. I've been chomping at the bit to use it in prod, and I created this polyfill so I could do so.

As it stands, I feel really good about its support for currentEntry, entries(), canGoBack/canGoForward, and the currententrychange event.

Where the Navigation API gets really interesting is in its navigation transition lifecycle management with the navigate event, navigation interceptors, and so on--which I plan on tackling next.

It has zero runtime dependencies, and bundlejs.com reports it weighing in at 2.95 kB after bundling and gzip.

I'm hoping to get any feedback and gauge interest as I think about how to approach polyfilling the rest of the API. Thank you for taking a look!

Comments URL: https://news.ycombinator.com/item?id=47062360

Points: 3

# Comments: 0

Along with syntax highlighting.

Now I’m entirely invested, what was the problem causing the crashes? How did they solve it?

I believe you can see it working on TikTok web as well.

You just can’t have the first video unmuted on initial load, although I wonder if this can be relaxed when user installs a PWA.

I am somewhat fearful of having created a monster, but at the same time I think it’s good to knock down barriers to knowledge and learning. All else equal, I think a designer or PM with some exposure to code is better than one without.

What I’m fearful of are 10k line PRs and pressure from product to “just ship it.” Past a certain threshold a PR will be really tough to review, to the point that it would be preferable for an engineer to have handled it from the start.

I think we will need deeper integration between figma and the codebase/storybook. Shared color palette definitions, integration of storybook components with figma components, stuff like that.

The Figma MCP that you can use to handover to your agent and simply say “implement this” is already pretty impressive.

Dead middle is decent too.

5120x3200 in 30” would be awesome.

I've been super hyped about it. My main goal at first was supporting `navigation.canGoBack` and the `currententrychange` event simply so that I could implement perfect back buttons with (almost) zero edge cases. This is surprisingly very tricky with the older History API.

Today I just opened a PR with support for `entries()` and `currentEntry`: https://github.com/kcrwfrd/navigation-ponyfill/pull/33

Once that lands I'll be able to start thinking about implementing full-blown navigations with it, with cool stuff like navigation interceptors and whatnot. That would actually enable framework router implementations wholly based off the Navigation API, rather than simply patching some enhanced capabilities for use with a router based on history.pushState / history.replaceState.