I'm not a copyright expert and if you told me that Harry Potter was common domain then I'd probably be a bit surprised but wouldn't think it's crazy. The first book came out 30 years ago after all. On further research the copyright laws are way more aggressive than that (a bit too much if you ask me) but 30 years doesn't seem quick. Patents expire after 20 years.
The Berne Convention (author's life + 50 years) is the baseline for the copyright laws in most countries. Many countries have a longer copyright period than Berne.
I find this fascinating, as I keep observing that there are pretty widespread differences between what people believe copyright does and what the law actually says.
For me lack of thunderbolt is a showstopper, when it’s supported a lot of needed peripherals will be supported automatically. They have apparently been working on tb support since the m1 was released 4 years ago.
To be frank, TB support on Linux in general is kinda crap. I'm not surprised this might take them a while, and I'm sure it's lower priority compared to other things on the road map
Unfortunately even if you pick nominally-equal-width glyphs, on the web you can still get screwed over by font substitution/fallback done by the browser.
First off, let me say it is awesome you're doing something like this.
But... I'm encountering a similar issue on both Chrome and Firefox on Leenucks. I guess it's possible you don't see the problem on your Mac because both these browsers use the OS to do font rendering.
It'd be a bit weird to have the Sonnet numbering ahead of the Opus numbering. The Opus 4.5->4.6 change was a little more incremental (from my perspective at least, I haven't been paying attention to benchmark numbers), so I think the Opus numbering makes sense.
I wonder if some kind of voluntary tagging system could help?
e.g. [20h/2d/$10] could indicate "I spent 20 human-hours over 2 days and burned $10 worth of tokens" (it's hard to put a single-dimensional number on LLM usage and not everyone keeps track, but dollars seem like a reasonable approximation)
I've thought about this. Even in the pre-LLM era, projects were rarely judged by the quality of their source code. READMEs and slick demos were the focus. So in some sense nothing has changed.
The difference now is that there is even less correlation between "good readme" and "thoughtful project".
I think that if your goal is to signal credentials/effort in 2026 (which is not everyone's goal), a better approach is to write about your motivations and process rather than the artefact itself - tell a story.
Yeah, but that's not the same, as most readers will just skip over that. What I said is more similar to HN's monthly "who's hiring" threads or "what are you working on" threads. Like https://news.ycombinator.com/item?id=46937696. I find those much more interesting.
What does my blog post have to do with anything? (But since you mention it - a large part of reverse engineering falls under the "boring" category I define in that article)
Why wouldn't that apply?
reply