pi, oh-my-pi, opencode - none of them have subsidized Claude though

Opencode can't lazy load skills, mcps, or agents and has limitations on context. It's a total nonstarter from my experience using it at work.

Fixed header isn't always a good thing, it can also be a mistake. Since content is the product, let the content take up all available space and use your browser navigation capabilities to navigate if necessary

Please look at the example that is literally on the front page of the lefthook website: https://lefthook.dev/

Ah ok the home page actually reminded me what the actual issue was. It can pass the list of staged files to the command but since it doesn't actually stash anything, it's not compatible with commands that don't accept a list of files. golangci-lint for example doesn't accept a list of files like this and will run on every single file in the repo. I don't know if this behaviour has changed in lefthook or golangci-lint now.

I recommend Amusing Ourselves to Death by Neil Postman

Not to have him cancelled in the first place. No need to pretend that doing something under the mob pressure is the same as doing something entirely willingly

Far, far more people have protested the positions of power held by (for example) Joe Rogan and Dave Chappelle. They ignored the cancellation attempts, and they're richer and more influential today than they were a few years ago.

"Cancellation" is a state of being famous enough that your controversial beliefs upset a large, loud number of people. In Eich's case, it threatened to have no effect on his career. He chose to change his career because of it.

Eich expressed his First Amendment rights, and other people expressed theirs in return. Why should either of them give up those rights for fear of offending the other?

Michael Hobbes, host of IBCK is guilty of those inaccuracies too. Here's him being fact checked regarding claims in the Maintenance Phase podcast: https://spurioussemicolon.substack.com/

I enjoy If Books Could Kill and I used to like You're Wrong About when Michael was on it. However, I have found on If Books Could Kill that they sometimes take the least charitable interpretation of something to ridicule it when a more charitable interpretation might find that there is more nuance than they are presenting.

I haven't listened to Maintenance Phase because it isn't really a topic that I'm all that interested in.

Yeah, I’ve seen those criticisms before and been convinced-enough that it’s contributed to my not bothering with that podcast. IBCK has been accurate enough when they’ve covered books I’m familiar with that I’m less worried about that being a problem with that show (though I’m sure they do sometimes get things wrong)

> The lead Ladybird dev endorses white replacement theory

Lying used to be something that people are ashamed of

If I scavenge any machine today, how likely would I be to find a 6502 vs something more modern? I’d argue that some people might have a NES at home and one could get a 2A03 from it, but in a hypothetical scenario where I need to scavenge some computational power, I’d find an Android phone

You're much more likely to stumble one something more modern, but that modern something is also much less repairable. It's great if it works and if it can run Linux or Dusk OS, but when it can't, you're out of luck.

With a 6502 or other such CPU, the machines you scavenge them from are much more repairable and adaptable. You can use those components like lego blocks. It breaks? either repair it or strip the working parts to use in another frankenstein computer.

I get the idea of making a frankenstein computer, I just disagree that 6502 is THE platform to do it on. Practically, there's no way for me to find it. Other comment mentions ARM, which is a much more interesting proposal to me

ARM is an interesting proposal if you want to order a SBC online and run software on it. Soldering an ARM CPU with low tech tools? That's something else.

Time of a strategic reserve of J-Links?

DuskOS apparently runs on ARM, so one of these vape boards running FORTH would likely feel very roomy indeed.

I have ported zForth to an even weaker chip, the famous 10c risc-v micro ch32v003 (16k flash, 2k ram) so no issue running on this: https://github.com/BogdanTheGeek/zForth

Allow me to brag about romforth (https://github.com/romforth/romforth) which I ported to the "3c" Padauk and can run on really small rom/ram microcontrollers. Caveats: - tested only on an emulator SDCC/ucsim_pdk, not on real hardware - given how small the ram is, there is no user dictionary but new words can be defined and tested using what the Forth folks refer to as "umbilical hosting".

Even for a Forth, 3KB of RAM is rather tight. Dusk OS intentionally de-prioritize compactness and it couldn't run on that amount of RAM. It can get a C compiler loaded in about 100KB of RAM, but 3? not enough to boot.

OK, so we'd play with zForth then, as BogdanTheGeek notes here. That reminds me, I have a Scamp board sitting here on my desk that I really should play with more. https://udamonic.com/what-is-a-scamp.html

"we'd", you mean in a collapse scenario? Forths are, by nature, "collapse-friendly", but one particularity with Collapse OS and Dusk OS is that they are fully self-hosted. This includes the tools necessary to improve upon themselves.

From a quick glance, it looks like BogdanTheGeek's Forth is written in C, which means that it's not self-hosted. If all you have is that disposable vape with this Forth in it, you lack the tools to deploy it on another machine or to improve it in place.

One could also port Collapse OS to ARM. I guess it wouldn't be a very big effort.

Good points! Really, I should start with learning Forth on the devices I have first, before getting to concerned about others. ARM does seem like a useful target though, given that they're basically everywhere these days.

Except when they ship v8 and you'll be forced to restructure your app to the whims of the library creators in case you need to update.