Hacker News: qbane

New comment by qbane in "The Last Quiet Thing"

qbane — Mon, 06 Apr 2026 19:13:49 +0000

The watch is interactive! Nice detail

New comment by qbane in "GitHub is once again down"

qbane — Tue, 24 Mar 2026 21:43:37 +0000

Productivity is finite. If you pivot entirely to the AI stack, you're going to lose bandwidth for everything else. It's an opportunity cost problem.

New comment by qbane in "Ask ChatGPT to pick a number from 1-10000, it generally selects from 7200-7500"

qbane — Sun, 22 Mar 2026 07:06:26 +0000

A better example would be to use LLMs to generate passwords or secret keys. Then even if it looks random to human, the inherent bias would make it a security disaster.

New comment by qbane in "Making WebAssembly a first-class language on the Web"

qbane — Thu, 12 Mar 2026 05:00:58 +0000

You can still obfuscate JS heavily and make a VM that executes also obfuscated code calling arbitrary browser APIs. At least In WASM everything is sandboxed so the attack surface is smaller.

New comment by qbane in "Hacker News.love – 22 projects Hacker News didn't love"

qbane — Mon, 23 Feb 2026 16:06:49 +0000

cf. Kagi is a good take

Technical Breakdown: How AI Agents Ignore 40 Years of Security Progress [video]

qbane — Mon, 23 Feb 2026 10:26:11 +0000

Article URL: https://www.youtube.com/watch?v=_3okhTwa7w4

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

Points: 1

# Comments: 0

New comment by qbane in "Anthropic's original take home assignment open sourced"

qbane — Wed, 21 Jan 2026 09:46:48 +0000

Remember: It is a company that keep saying how much production code can be written by AI in xx years, but at the same time recruiting new engineers.

New comment by qbane in "Show HN: Pdfwithlove – PDF tools that run 100% locally (no uploads, no back end)"

qbane — Mon, 19 Jan 2026 08:33:17 +0000

The "source" link at the footer seems to point to the author's GitHub profile, not source repository. The repo under it contains no code either.

New comment by qbane in "C++ std::move doesn't move anything: A deep dive into Value Categories"

qbane — Sun, 11 Jan 2026 20:58:32 +0000

I read Effective Modern C++ years ago and was confused exactly like what you describe.

New comment by qbane in "A production bug that made me care about undefined behavior"

qbane — Mon, 29 Dec 2025 21:47:58 +0000

icc's result is interesting too

New comment by qbane in "Show HN: Minimalist editor that lives in browser, stores everything in the URL"

qbane — Wed, 24 Dec 2025 20:03:35 +0000

Just started making my own recently with CodeMirror 6 during holidays. No saving function for now: https://qbane.github.io/cgm

New comment by qbane in "Fabrice Bellard Releases MicroQuickJS"

qbane — Tue, 23 Dec 2025 20:00:29 +0000

Not likely:

> It only supports a subset of Javascript close to ES5 [...]

I have not read the code of the solver, but solving YouTube's JS challenge is so demanding that the team behind yt-dlp ditched their JS emulator written in Python.

New comment by qbane in "Making Google Sans Flex"

qbane — Fri, 19 Dec 2025 10:32:33 +0000

To declare "open source", you have to provide a way for the public to get access to the source code. But there seems to be none at least for the time being.

New comment by qbane in "Put a ring on it: a lock-free MPMC ring buffer"

qbane — Wed, 17 Dec 2025 19:22:39 +0000

That is a fair assessment. Maintaining read/write pos and peek them at every operation is a big performance hit. The impact is amplified if each invocation needs a syscall. That is exactly what futexes address: Allowing spin locks to remain in user space and avoid entering the kernel as long as contention is low.

In JavaScript, atomic operations are relatively lightweight, so their overhead is likely acceptable. Given that, I am open to adjusting my code to your suggested approach and seeing how it performs in practice.

New comment by qbane in "Put a ring on it: a lock-free MPMC ring buffer"

qbane — Tue, 16 Dec 2025 17:47:17 +0000

By a quick glance, yes, this is what I want: a channel to communicate between processes via a piece of shared memory, protected by a pair of futexes.

In JS ecosystem, buffers that allow data loss is more common (aka ring buffers), but ringbuf.js [1] is the only complete implementation to my knowledge. In my use case on I/O between WASM modules where data must be transferred as-is, the process must block on buffer overrun/underrun in a synchronous manner. Therefore a circular buffer is required. I could not find such a niche library written in JS, so I decided to bite the bullet and reinvent the wheel [2].

[1]: https://github.com/padenot/ringbuf.js

[2]: https://github.com/andy0130tw/spsc

New comment by qbane in "Put a ring on it: a lock-free MPMC ring buffer"

qbane — Tue, 16 Dec 2025 14:30:15 +0000

I wrote my first SPSC circular buffer implementation in TS upon reading the previous post on futex [0] from the same author. It was more intricate than it had seemed, until I finally sat down and wrote my own code.

[0]: https://h4x0r.org/futex/ discussion: https://news.ycombinator.com/item?id=44951563

New comment by qbane in "Shai-Hulud Returns: Over 300 NPM Packages Infected"

qbane — Mon, 24 Nov 2025 12:49:44 +0000

`--ignore-scripts` should be the default behavior.

New comment by qbane in "Boa: A standard-conforming embeddable JavaScript engine written in Rust"

qbane — Sun, 16 Nov 2025 04:06:47 +0000

I really appreciate the clear and detailed project description, the only concern is the title on HN. Failing on tests is fine, especially when it demands huge efforts to triage and reiterate on the project structure for them.

New comment by qbane in "Boa: A standard-conforming embeddable JavaScript engine written in Rust"

qbane — Sun, 16 Nov 2025 03:42:01 +0000

If you mean "latest" ECMAScript then that is true. Even latest gcc or clang does not support all features from C++23: https://en.cppreference.com/w/cpp/compiler_support.html.

New comment by qbane in "Boa: A standard-conforming embeddable JavaScript engine written in Rust"

qbane — Sat, 15 Nov 2025 19:37:31 +0000

I am not meant to be harsh, but note that it fails on a small number of test cases, on v0.21 that is ~900 out of ~50k. Strictly speaking it cannot be described as standard-comforming unless there is some reason behind every failed test. A better way to strive on standard conformance, like QuickJS takes, is to pin down the ecma262 revision and make it 100% compliant.