Hacker News: ameliaquining

New comment by ameliaquining in "GitHub Stacked PRs"

ameliaquining — Mon, 13 Apr 2026 21:10:09 +0000

It's in private preview. Probably they'll put it in the main docs and such once it's open to everyone.

New comment by ameliaquining in "GitHub Stacked PRs"

ameliaquining — Mon, 13 Apr 2026 21:08:52 +0000

The tooling for that already exists, since a PR can consist of multiple Git commits and you can look at them separately in the UI. I don't know whether agents are any good at navigating that, but if not, they won't do any better with stacked PRs. Stacked PRs do create some new affordances for the review process, but that seems different from what you're looking for.

New comment by ameliaquining in "GitHub Stacked PRs"

ameliaquining — Mon, 13 Apr 2026 21:01:05 +0000

How would that work? Commits in different repos aren't ordered relative to one another. I suppose you could have a "don't let me merge this PR until after this other PR is merged" feature, but you could do that with a GitHub Action; it doesn't really need dedicated backend or UI support.

New comment by ameliaquining in "GitHub Stacked PRs"

ameliaquining — Mon, 13 Apr 2026 20:54:14 +0000

You can in fact do this from the web UI: https://github.github.com/gh-stack/guides/ui/#creating-a-sta...

New comment by ameliaquining in "Jennifer Aniston and Friends Cost Us 377GB and Broke Ext4 Hardlinks"

ameliaquining — Fri, 10 Apr 2026 19:03:57 +0000

They do also offer it as multi-tenant hosted SaaS, and the post is about their experience running backups on that. But whatever solution they use has to also work with the self-hosted version, which imposes some constraints.

New comment by ameliaquining in "Jennifer Aniston and Friends Cost Us 377GB and Broke Ext4 Hardlinks"

ameliaquining — Fri, 10 Apr 2026 14:28:40 +0000

Discourse is self-hostable; they can't require their users to use a filesystem that supports deduplication. (Or, well, they could, but it would greatly complicate installation and maintenance and whatnot, and also there would need to be some kind of story for existing installations.)

New comment by ameliaquining in "A cryptography engineer's perspective on quantum computing timelines"

ameliaquining — Mon, 06 Apr 2026 22:23:00 +0000

The timeline here is for when major governments have access to CRQCs. It will be much longer than that (barring an AI singularity or something) before you have access to one.

New comment by ameliaquining in "Bombadil: Property-based testing for web UIs"

ameliaquining — Tue, 24 Mar 2026 15:47:21 +0000

The latter. For example, the concept here seems like it ought to work with the Playwright test runner for Node.js (and then you'd have compatibility with the Playwright ecosystem).

New comment by ameliaquining in "Bombadil: Property-based testing for web UIs"

ameliaquining — Tue, 24 Mar 2026 03:57:37 +0000

Is there any particular reason why this is its own bespoke test runner, instead of a library that plugs into existing ones?

New comment by ameliaquining in "404 Deno CEO not found"

ameliaquining — Sat, 21 Mar 2026 17:34:45 +0000

Would something else that wasn't a VC-funded startup really work better? The technical problem seems fundamental.

New comment by ameliaquining in "2% of ICML papers desk rejected because the authors used LLM in their reviews"

ameliaquining — Thu, 19 Mar 2026 19:59:36 +0000

I believe that's the joke, yes.

New comment by ameliaquining in "2% of ICML papers desk rejected because the authors used LLM in their reviews"

ameliaquining — Thu, 19 Mar 2026 19:59:14 +0000

It was. More details here: https://icml.cc/Conferences/2026/LLM-Policy

In particular: "Any reviewer who is an author on a paper that requires Policy A must also be willing to follow Policy A."

New comment by ameliaquining in "Switzerland Built an Alternative to BGP"

ameliaquining — Wed, 18 Mar 2026 13:20:33 +0000

No, the publication date on this is yesterday.

New comment by ameliaquining in "C++26: The Oxford Variadic Comma"

ameliaquining — Mon, 16 Mar 2026 13:38:50 +0000

Editions never remove APIs.

New comment by ameliaquining in "C++26: The Oxford Variadic Comma"

ameliaquining — Sun, 15 Mar 2026 23:35:05 +0000

If you're talking about editions, this isn't how they work at all; every edition continues to be supported forever. (The part about automated migration tooling is true, and nice.)

There've been a few cases where code was unsound and should never have compiled, but did due to compiler bugs, and then they fixed the bugs and the code stopped compiling. These were handled through deprecation warnings with timelines at least several months long (Rust releases a new version every six weeks), but usually didn't have automated migration tooling, and didn't fracture the language mostly because they were rare edge cases that most programmers didn't encounter.

New comment by ameliaquining in "Vite+ Alpha: Unified Toolchain for the Web (MIT License)"

ameliaquining — Fri, 13 Mar 2026 13:37:56 +0000

No. There's an open issue: https://github.com/voidzero-dev/vite-plus/issues/557

New comment by ameliaquining in "Vite 8.0 Is Out"

ameliaquining — Fri, 13 Mar 2026 06:13:32 +0000

Yes, those work fine: https://playground.oxc.rs/?options=%7B%22run%22%3A%7B%22lint...

For that matter, TypeScript's version of decorators ("experimental decorators") also works: https://playground.oxc.rs/?options=%7B%22run%22%3A%7B%22lint...

What's not supported is the current draft proposal for standardized ECMAScript decorators; if you uncheck experimentalDecorators, the decorator syntax is simply passed through as-is, even when lowering to ES2015.

New comment by ameliaquining in "Malus – Clean Room as a Service"

ameliaquining — Thu, 12 Mar 2026 14:37:58 +0000

Note for people who just briefly skimmed the site: This is satire.

New comment by ameliaquining in "Warn about PyPy being unmaintained"

ameliaquining — Sun, 08 Mar 2026 14:58:54 +0000

It's not irrelevant, because if SPEC 0 says that a particular Python version is no longer supported, then libraries that follow it won't avoid language or standard library features that that version doesn't have. And then those libraries won't work in the corresponding PyPy version. If there isn't a newer PyPy version to upgrade to, then they won't work in PyPy at all.

New comment by ameliaquining in "Package managers need to cool down"

ameliaquining — Sat, 07 Mar 2026 23:24:07 +0000

Can you explain how this works? Is it different from what's described in the "Language vs. system package managers" section of the post?