Reading the latest extended incident report from Honeycomb makes me want to never run Kafka in production.
Which is an approach that's served me fine up to this point in my career, why not in the future as well? 🤞
Ghostty is written in Zig and it really shows, unfortunately
The Steering Council has formally accepted the TypeForm PEP. This is big news for cattrs but I'll hold off on implementing it until Mypy enables support for it without a flag.
yeah reflinking is probably the way to go here
Apparently on Linux uv defaults to hardlinking files from its cache when installing stuff into a virtualenv. That kind of sucks for people who sometimes edit third-party libraries to stick prints or breakpoints in there, like me.
Touche
Yes from a practical perspective (sure, it needs to import the code) but also from a logical perspective.
If you have pytest unit tests, pytest is a (dev) dependency of your project. If you format your files, Black or ruff is a dependency of your project. Same for Mypy. They should all be listed.
It has been [0] days since some monkeypatching has caused me to waste over an hour of debugging.
Since upgrading my OnePlus Open to Android 16, my home screen reset itself to blank twice.
Super #firstworldproblems, but it feels like someone rearranged the furniture in my house. Trying to reconstruct app position by muscle memory right now (again).
They wanted to simplify by not having exceptions and just returning errors from functions but got bored before they added sum types
So instead functions return tuples with errors and exceptions still exist but they're called panics
Doing chess lessons on Duolingo.
"Pin my queen with your bishop" sounds way more fun out of context
In your particular case, the type system doesn't model hashability. Lists are mutable and so not hashable.
Tuples are immutable, but only hashable if their contents are hashable. So if you try hashing something like `([],)`, you'll again get an error.
You don't have to go that far to get an exception to be raised in properly typed code:
```py
x = [1]
x[2]
```
The point of type checking isn't to ensure no exceptions, but to apply an additional, stricter model of execution to your code. This model sometimes includes exceptions.
Ya
The law
This might get really thorny, yeah. Let's say Claude knows a ton of Textual (which is true in my experience) having ingested a ton of Textual, is Claude a derived work of Textual? If Claude spits out a tool written in Textual for me, is that tool a derived work of Textual?
🤷🤷🤷
You find a project you like, but you can't use it due to the license (maybe it's GPL or AGPL). What's stopping you feeding it to an agent and having it port it to another language, and then potentially back again?
Bam, no more copyright.
This is what AI companies are doing in the first place, yes?
Serious question: what happens to copyright when this is done? I'm guessing you lose any claims to the new code?
a guy wearing a “i ❤️ ny” cap reading the qur’an in one hand and the communist manifesto in the other
day one in mamdani’s new york
Yeah wtf? War is war, get him
Dipshit Derek king of season 5
This is no longer the case since AI can do all of this for you, zero effort required. In fact it's much worse since the sycophantism inherent to the process will actually push this further in the wrong direction.
Back in the olden days™️ it used to be the case that if a person went to the trouble of publishing an open source project - setting up the repo, tests, CI, documentation) - you could at least assume said person spent a modicum of time validating their idea first, by doing a little research.
Turns out J. Michael Straczynski (of Babylon 5 fame) worked on both the original He-man cartoon and the Captain Power and the Soldiers of the Future show.
I haven't seen Babylon 5 but this dude had a large influence on my childhood. Maybe I should just watch it 😅
Kudos to @hynek.me for writing hynek.me/articles/mac..., which just solved my problem.
Why?
A more consistent story for positional, kw-only and combined arguments.
Type checking. Linting. Auto formatting.
Sophisticated argument validation.
If I could clone myself, this would be pretty awesome. I'd base it on the Astral stuff (ruff, ty) and Cyclops.
I like `just` a lot. I switched all my open source stuff to it (from make) and we're in the process of adopting it as standard at $DAYJOB. Would not go back to make for my needs.
But I have this niggling suspicion a task runner based on Python would be better.
I'm saying it's bad, Senko
Hot take: saying we need EU big tech is like saying we need EU asbestos
What do you mean by "platform code"?
