New comment by bikeshaving in "Ask HN: What are you working on? (August 2026)"

bikeshaving — Sun, 09 Aug 2026 20:20:06 +0000

TermDOM: A terminal renderer which used real DOM nodes, so you can write TUIs like web apps with HTML, CSS, and whatever framework you want. I didn’t really write this, more like spent intense weeks of effort where I product manage (yell at) Claude and did visual testing.

https://github.com/bikeshaving/termdom

Show HN: IPAbet – A fast, memorable keyboard for International Phonetic Alphabet

bikeshaving — Sat, 25 Jul 2026 14:41:59 +0000

Article URL: https://ipabet.org

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

Points: 2

# Comments: 0

New comment by bikeshaving in "l: A new runtime for k and q"

bikeshaving — Tue, 07 Jul 2026 18:53:42 +0000

As someone who does not know what k4, qSQL, or q are, reading through the landing page of this website was giving me mild schizophrenia. And then I tried to search for these things in the old way, and received incredibly dry technical sites that still don’t tell me what it is, and all these names are wildly SEO unfriendly. So I had Claude give me context and it’s apparently the database Wall Street uses for tick data. Sounds cool but, jeez.

New comment by bikeshaving in "How liminalism became the defining aesthetic"

bikeshaving — Sun, 07 Jun 2026 14:41:56 +0000

My favorite example of liminalism is Everything Empty Always Alone, a man on YouTube in his 40s who claims to be a time traveler and films himself walking and driving around empty metropolitan areas. He claims he’s recording from some sort of alternate universe, but it’s likely he’s just at these locations at odd hours. In any case, it’s fun outsider art. Or maybe it’s all true you never know.

https://www.youtube.com/@EverythingEmptyAlwaysAlone/videos

New comment by bikeshaving in "Collaborative Editing in CodeMirror (2020)"

bikeshaving — Tue, 05 May 2026 21:56:56 +0000

I’ve tried to create the minimalist version of this with Revise.js. The main surface area is a custom element called a ``. The OverType library you linked to uses a time-old technique where you essentially put a duplicate copy of the content over a `` to highlight it but this doesn’t really work in mobile and it messes with the selection. I’ve tried to grapple with `contenteditable` directly with my solution, but it does try to use less JavaScript and it does try to be more minimal.<p><a href="https://github.com/bikeshaving/revise" rel="nofollow">https://github.com/bikeshaving/revise</a> <a href="https://revise.js.org" rel="nofollow">https://revise.js.org</a> <a href="https://revise.js.org/blog/introducing-revise/" rel="nofollow">https://revise.js.org/blog/introducing-revise/</a></p> </article> <article> <h1>New comment by bikeshaving in "Qite.js – Frontend framework for people who hate React and love HTML"</h1> <p>bikeshaving — Fri, 27 Mar 2026 15:47:50 +0000</p> <p>Manual refresh(). This is something Crank does, and other frameworks like the new Remix one is picking it up as well. Being explicit has its advantages.</p> </article> <article> <h1>New comment by bikeshaving in "Qite.js – Frontend framework for people who hate React and love HTML"</h1> <p>bikeshaving — Tue, 24 Mar 2026 20:05:28 +0000</p> <p>I’ve written about how Svelte, Vue, and Solid are all reactive and share common pitfalls due to their reactive solutions. My theory is that they all cause worse bugs than they prevent.<p><a href="https://crank.js.org/blog/why-be-reactive/" rel="nofollow">https://crank.js.org/blog/why-be-reactive/</a></p> </article> <article> <h1>New comment by bikeshaving in "Meta's Omnilingual MT for 1,600 Languages"</h1> <p>bikeshaving — Sat, 21 Mar 2026 15:41:58 +0000</p> <p>I don’t own a car :)</p> </article> <article> <h1>New comment by bikeshaving in "Meta's Omnilingual MT for 1,600 Languages"</h1> <p>bikeshaving — Sat, 21 Mar 2026 15:35:27 +0000</p> <p>I’m very wary of celebrating Meta’s language work when the company was credibly found to have contributed to the genocide against the Rohingya in Myanmar, and separately, to human rights abuses against Tigrayans during the conflict in northern Ethiopia. Be careful whose sins you’re laundering.<p><a href="https://www.amnesty.org/en/latest/news/2025/02/meta-new-policy-changes/" rel="nofollow">https://www.amnesty.org/en/latest/news/2025/02/meta-new-poli...</a> <a href="https://www.amnesty.org/en/latest/news/2023/10/meta-failure-contributed-to-abuses-against-tigray-ethiopia/" rel="nofollow">https://www.amnesty.org/en/latest/news/2023/10/meta-failure-...</a></p> </article> <article> <h1>Show HN: Revise.js – Building blocks for contenteditable-based text editors</h1> <p>bikeshaving — Tue, 17 Mar 2026 16:02:36 +0000</p> <p>Hi HN. I've been working on this since 2018. Revise.js is a set of building blocks for contenteditable: a <content-area> web component that gives you a textarea-like .value for any contenteditable element, an Edit data structure with compose/transform/invert for OT inspired by the Xi editor, and a Crank.js integration for declarative editable components. At 32.8 KB gzipped (including the rendering framework), it's 2–4x smaller than ProseMirror, Slate, or CodeMirror. The trade-off is that those ship complete editors; Revise is foundations you build on. All the demos on the homepage are live and editable: <a href="https://revise.js.org" rel="nofollow">https://revise.js.org</a></p> <hr> <p>Comments URL: <a href="https://news.ycombinator.com/item?id=47414537">https://news.ycombinator.com/item?id=47414537</a></p> <p>Points: 5</p> <p># Comments: 0</p> </article> <article> <h1>Dulce et Decorum Est (1921)</h1> <p>bikeshaving — Wed, 04 Mar 2026 21:41:40 +0000</p> <p>Article URL: <a href="https://www.poetryfoundation.org/poems/46560/dulce-et-decorum-est">https://www.poetryfoundation.org/poems/46560/dulce-et-decorum-est</a></p> <p>Comments URL: <a href="https://news.ycombinator.com/item?id=47254322">https://news.ycombinator.com/item?id=47254322</a></p> <p>Points: 220</p> <p># Comments: 107</p> </article> <article> <h1>New comment by bikeshaving in "Microsoft Creative Writer (1993)"</h1> <p>bikeshaving — Tue, 03 Mar 2026 00:41:34 +0000</p> <p>I must tell you, it is an incredible relief to learn that McZee was not a figment of my imagination.</p> </article> <article> <h1>New comment by bikeshaving in "Microsoft Creative Writer (1993)"</h1> <p>bikeshaving — Mon, 02 Mar 2026 23:05:59 +0000</p> <p>Just found the text editor from my childhood</p> </article> <article> <h1>Microsoft Creative Writer (1993)</h1> <p>bikeshaving — Mon, 02 Mar 2026 23:05:59 +0000</p> <p>Article URL: <a href="https://classicreload.com/play/win3x-creative-writer.html">https://classicreload.com/play/win3x-creative-writer.html</a></p> <p>Comments URL: <a href="https://news.ycombinator.com/item?id=47225536">https://news.ycombinator.com/item?id=47225536</a></p> <p>Points: 18</p> <p># Comments: 5</p> </article> <article> <h1>New comment by bikeshaving in "When does MCP make sense vs CLI?"</h1> <p>bikeshaving — Sun, 01 Mar 2026 20:40:39 +0000</p> <p>I’ve found that humans are pretty good at reading through the output of bash commands. And Claude Code keeps insisting on truncating the output for some reason.</p> </article> <article> <h1>New comment by bikeshaving in "When does MCP make sense vs CLI?"</h1> <p>bikeshaving — Sun, 01 Mar 2026 18:10:47 +0000</p> <p>I keep asking why the default Claude tools like Read(), Write(), Edit(), MultiEdit(), Replace() tools aren’t just Bash() with some combination of cat, sed, grep, find. Isn’t it just easier to pipe everything through the shell? We just need to figure out the permissions for it.</p> </article> <article> <h1>New comment by bikeshaving in "A better streams API is possible for JavaScript"</h1> <p>bikeshaving — Fri, 27 Feb 2026 21:39:28 +0000</p> <p>Yes, the callable promise abstraction is just a bit of effort:<p><pre><code> let resolveRef; const promise = new Promise((res) => { resolveRef = res; }); const callback = (data) => { // Do work... resolveRef(data); // This "triggers" the await }; Object.assign(callback, promise); </code></pre> There’s a real performance cost to awaiting a fake Promise though, like `await regularPromise` bypasses the actual thenable stuff.</p> </article> <article> <h1>New comment by bikeshaving in "A better streams API is possible for JavaScript"</h1> <p>bikeshaving — Fri, 27 Feb 2026 20:11:05 +0000</p> <p>Not accepting PRs for this. I think the logic is sound (Easter Eggs should be difficult to trigger).</p> </article> <article> <h1>New comment by bikeshaving in "A better streams API is possible for JavaScript"</h1> <p>bikeshaving — Fri, 27 Feb 2026 15:53:08 +0000</p> <p>A long time ago, I wrote an abstraction called a Repeater. Essentially, the idea behind it is, what would the Promise constructor look like if it was translated to async iterables.<p><pre><code> import { Repeater } from "@repeaterjs/repeater"; const keys = new Repeater(async (push, stop) => { const listener = (ev) => { if (ev.key === "Escape") { stop(); } else { push(ev.key); } }; window.addEventListener("keyup", listener); await stop; window.removeEventListener("keyup", listener); }); const konami = ["ArrowUp", "ArrowUp", "ArrowDown", "ArrowDown", "ArrowLeft", "ArrowRight", "ArrowLeft", "ArrowRight", "b", "a"]; (async function() { let i = 0; for await (const key of keys) { if (key === konami[i]) { i++; } else { i = 0; } if (i >= konami.length) { console.log("KONAMI!!!"); break; // removes the keyup listener } } })(); </code></pre> <a href="https://github.com/repeaterjs/repeater" rel="nofollow">https://github.com/repeaterjs/repeater</a><p>It’s one of those abstractions that’s feature complete and stable, and looking at NPM it’s apparently getting 6.5mil+ downloads a week for some reason.<p>Lately I’ve just taken the opposite view of the author, which is that we should just use streams, especially with how embedded they are in the `fetch` proposals and whatever. But the tee critique is devastating, so maybe the author is right. It’s exciting to see people are still thinking about this. I do think async iterables as the default abstraction is the way to go.</p> </article> <article> <h1>New comment by bikeshaving in "Making a font with ligatures to display thirteenth-century monk numerals"</h1> <p>bikeshaving — Thu, 19 Feb 2026 07:47:12 +0000</p> <p>I was thinking using ZWJ because the staff is always implied by the usage of Cistercian numerals. I was also wondering if we could reuse CISTERCIAN 1-9 for each significant digit rather than having to encode all 4 separately, though at the end of the day it’s only 36 separate code points.<p>Adding the staff is 37 codepoints versus 36, but I think using ZWJ would at least have each numeral independently renderable so it degrades gracefully. I’m not too sure about how combining characters degrade.<p>Essentially it boils down to whether you think the staff and the digit flag part of the numeral are independent or not.</p> </article> </main></body></html>

Hacker News: bikeshaving

New comment by bikeshaving in "Ask HN: What are you working on? (August 2026)"

Show HN: IPAbet – A fast, memorable keyboard for International Phonetic Alphabet

New comment by bikeshaving in "l: A new runtime for k and q"

New comment by bikeshaving in "How liminalism became the defining aesthetic"

New comment by bikeshaving in "Collaborative Editing in CodeMirror (2020)"