News for hackers. Stuff that matters.

burntcaramel

Re:Can the AI boom make enough money to sustain itself? on Thursday November 12, 2026 @05:11PM (#50475066)
Because it’s asking about something that can only be answered in the future, I think a question here is fine. It says the article will be about exploring that question.
Re:Anthropic IPO on Thursday November 12, 2026 @07:33AM (#50466249)
It is on the web too: https://qip.dev/chart-openai-anthropic-arr

It’s the exact same wasm as the cli command above.

I can take a screenshot if you need.

Re:Anthropic IPO on Thursday November 12, 2026 @07:15AM (#50466084)
I made a chart to compare Anthropic and OpenAI revenue that runs in the terminal:

npx qipgui qip.dev gui/openai-anthropic-arr.wasm

I made QIP Router where every part of rendering and making the HTTP response is customizable via WebAssembly. You often have a lot more control than a traditional static site generator that requires a particular plugin made — just make your own!

https://qip.dev/docs/router

Re:Bob Cringely Has Died on Sunday October 04, 2026 @12:26AM (#49950629)
I greatly enjoyed his book Accidental Empires https://en.wikipedia.org/wiki/Accidental_Empires
Re:Memory-Safe WebP Decoding on Saturday October 03, 2026 @10:35PM (#49950058)
I’ve compiled libwebp to WebAssembly and made a web page to use it: https://qip.dev/webp-to-png

You can also run the same wasm on the command line:

  npx @qip.dev/qipx qip.dev run \
    image/webp/webp-to-ktx2-r8g8b8a8-srgb.wasm \
    image/ktx2/ktx2-r8g8b8a8-or-b8g8r8a8-srgb-to-png.wasm \
    < input.webp > output.png
Re:Platform-Independent SIMD in Go on Friday September 25, 2026 @07:16PM (#49851286)
Now with Mojo and WebAssembly I notice 3 different approaches for platform-independent SIMD. For examples operating on an array of floats:

- WebAssembly: 4 float32s

- Mojo: N float32s where N is a compile-time parameter

- Go simd: vector of float32s

Re:27.5KB language-agnostic WebGPU syntax highlighter on Thursday September 10, 2026 @03:23AM (#49639674)
This prompted me to make a JavaScript syntax highlighter in WebAssembly that’s 99.9% in agreement with Shiki in 12.7 kb: https://qip.dev/syntax-highlight-comparison
Re:Static Allocation, Constant Work on Friday September 04, 2026 @02:14AM (#49561115)
I’ve been surprised how feasible static allocation has been. I thought it would be too restrictive and you’d be constantly hitting a wall. I’m writing WebAssembly in Zig/Odin/C and I’ve been able to have a linter reject the `memory.grow` wasm instruction and just use fixed-sized buffers in my code.

It me you think “ok, how big do I want the maximum image to be?” I’ve settled on 25 megapixels, which in the hundreds of megabytes. Since most images are much smaller, I believe on all mainstream hosts the memory isn’t paged in until it is first read/write so the memory footprint is much smaller.

Re:Mojo 1.0 on Tuesday August 11, 2026 @11:14PM (#49267444)
From listening to Chris Lattner in interviews my guess it’s learning from when Swift became open source. The beta versions of Swift had massive language changes in how value types worked like with Array. Mojo is trying to get this language design locked down first, which is easier to do behind closed doors.

A compiler promising source stability is a different commitment than the compiler’s code being ready for outside contributors. Which is also different to having ABI stability, which took until 5.0 for Swift to achieve (I think Mojo does not have ABI stability as a goal as it doesn’t have to link to OS frameworks).

Re:Cool URIs Don't Change (1998) on Sunday August 09, 2026 @09:20PM (#49238167)
They didn’t follow their own advice for their accessibility practices page https://www.w3.org/TR/wai-aria-practices/
Re:The Difference Between a Button and a Link on Wednesday July 29, 2026 @03:34AM (#49094456)
If you have a cancel button inside a form, you can point that button to another form dedicated to deleting with the form attribute: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...

I agree with some of this post but the argument feels muddled. "Clicking a logout button navigates the current page to a logged-out one" is wrong — it changes the state of the session, which is more than just a navigation. "Relative links can jump around the current page" — this _is_ a navigation.

I too weighed up the differences between a button and link and referenced the now sadly defunct WAI-ARIA Practices document which I found pretty clear: https://components.guide/accessibility-first/navigation

Re:The Tower Keeps Rising on Wednesday July 15, 2026 @09:13AM (#48920369)
I love the line “This friction synchronizes people.”

Part of the understanding that is missed being learned by the team are the failure modes: how can this system fail and how catastrophic is it?

Now I fear only the users will learn via data loss, leaks, and hacks.

Re:Just Let Me Write Digits on Tuesday July 14, 2026 @09:07AM (#48906265)
Yet another example where using <form method="post"> and <input> with zero JavaScript would be a better user experience. If you are going to write custom code you have to clear the minimum bar of what the browser provides.
Re:Death by a Thousand Comments on Tuesday June 23, 2026 @04:32AM (#48642040)
Thanks for your honest thoughts. It bothers me because there’s many places to check all the time. It seems every tool has an inbox and wants to send me notifications about it. I have to read them all to keep up to date, and my job becomes piecing them all together into a cohesive story just to make sense of what’s going on at work.

It can feel super useful as an engineer to find a line of code in PR or a sentence in a Notion document, and then add your feedback directly there. But then I find the conversation half happens on Slack, and then continues in a Zoom meeting, and then the comment on the Notion doc is out of date. So I have to keep track of all of this in my head with which piece of feedback is stale and which one is still relevant, and then reconcile that with feedback from others.

It’s assumed that we need another tool, something that can do the job of retrieving all of these comments and reconciling them into a total order. My article asks whether reconciling decisions into a total order is actually part of the job of leadership. If we defer to AI to make sense of what we’re saying and deciding then we risk the people and the org becoming weaker from lack of clarity.

Re:Elixir v1.20 released: now a gradually typed language on Thursday June 04, 2026 @01:34PM (#48401903)
> if you can use AI to achieve full test coverage, are there actual benefits in static typing for coding agents?

Full test coverage doesn’t tell you if the tests behave correctly. So you could prompt an AI agent to write 100% test coverage where those tests could be exercising all code paths yet contribute 0% to the story of what the code does. You need human understanding of what the desired contract is that the tests check.

Imagine a contract lawyer who blindly signs any contract that they are given: they aren’t doing their job. They ought to have an idea in mind of what their client’s goals and limits are so they can determine if a given contract fulfils those needs.

Types are a declarative contract, so they can be a lighter yet more limited way to enforce a contract. The compiler can verify if all the declared types across the program agree with each other. This is especially helpful with refactoring, such as ensuring the adding a field has been rolled out everywhere.

Types aren’t to be just checked by the compiler, but checked by the human authors too. That’s why explicit type signatures are valuable, especially if they are kept intelligible. They encode the different variations in state and possible branching on that state. So you can whittle your types down as a way of whittling the solution down to be more focused. The problem in your head is reflected in the types, and any simplifications in the types then simplify the problem in your head, and any tests derived from that understanding.

Re:Saying Goodbye to Asm.js on Thursday May 21, 2026 @01:46PM (#48226479)
It definitely wasn’t “working great”, I’ve now fixed a bug in the event system that was causing loops. The performance should be improved now.

Yes, accessibility is a key concern of mine, I’m keen to explore html-in-canvas as a way to have an accessibility tree combined with a rendered interaction.

I’m personally at a stage where React and CSS have pushed to DOM to extremes of complexity and difficultly in optimization that I desire simpler ARIA-based HTML combined with custom rendering. I’m hopeful that it will be easier to test, lighter for users, and faster for everyone.

Older »