cloudhead

@pierrecomputer, previously @radicle.
Find me on 🦋

[cloudhead @cloudhead]

You can find me on 🦋Bluesky https://t.co/kzwP1T6XuD from now on.

I'll be posting about my new project there.

👋

[Jonathan Blow @Jonathan_Blow]

I just think that we could achieve everything we do today with computers, with a simplified "technical stack" consisting of 98% less stuff ... fewer complexities to deal with when making things on top, thus easier to create the things and the higher-quality they will be (and cheaper, and more robust, etc). But not that many people seem to care about this issue.

[Pierre @pierrecomputer]

If you have ever wondered what goes into making the best diff rendering library possible, Amadeus has written a technical blog post for you

We hope you love it as much as we do

link in comments

[cloudhead @cloudhead]

@henriktorget @pierrecomputer Yes, I’ll make it!

[cloudhead @cloudhead]

Happy to say I'm joining the excellent team at @pierrecomputer to continue working on fundamental code infrastructure!

[cloudhead @cloudhead]

@tsenart @pierrecomputer ikr

[cloudhead @cloudhead]

@tsenart good show

[Pierre @pierrecomputer]

diffshub[dot]com

Take any public diff from GitHub and virtualize it nearly instantly, no matter how large, with DiffsHub. Built to show off our brand new CodeView component.

To try it out, replace `github` with `diffshub` in your address bar.

[cloudhead @cloudhead]

@pierrecomputer @github

[cloudhead @cloudhead]

@tsenart @perfloop Congrats, godspeed!

[cloudhead @cloudhead]

@lenberg Congrats, this looks amazing.

[cloudhead @cloudhead]

There is an element of truth here, but in reality I think we'll be using code editors for the next 10 years at least. We might not be typing individual characters as much, but we'll still be working with text, and lots of it. Zed will simply have to adapt to new ways of working.

[Erik Meijer @headinthebox]

"... building that foundation took years, but it was worth it ..."

https://t.co/K5V7qSKWk3

I feel sorry for these folks, working for years to make a blazingly fast text editor, only to finish it right when we do not care anymore about editing code.

[cloudhead @cloudhead]

@flowerornament That’s so interesting, and I think that if it allowed me to do something I couldn’t do before, like physics research, I would feel that same rush. But for me it’s more like driving a faster car, I have to be more careful but if I stay in control I can get there faster.

[Glenn Meder @GlennMeder]

🧵 THREAD

1/ Online age verification is the hill to die on.

Not a fight you can sit out. Not a battle you can skip. Not a policy you can afford to ignore while you focus on something else.

This is it. This is the line. This is the infrastructure that enables every other piece of the digital control grid.

If we lose this fight, we lose everything.

[Flower @flowerornament]

I'd like to expand my list of people doing this right now in a real way. PLAN, Urbit, Radiant, Oxide, some Elixir folks. Who else? I think there's a more fundamental project under all of this—one that completely dispenses with human limitations. Something bold enough to tackle:

- Resolving the database/file-system divide
- Resolving the RAM/storage divide
- Resolving the tradeoff between functional purity and performance
- Un-clocked and clocked in one model
- Actually creating a generic and powerful unified approach to interfaces without the cruft
- Fully incorporating the learnings of the last two decades (which, don't exist in *any* production OS, all of which are from at least the early 90s)

Either that, or I want to see these projects stack—but everyone has different philosophy and concerns.

This was crazy to attempt in the past, but I don't think it is anymore with the right team.

[Eleftherios @lftherios]

1/ Autoresearch from @karpathy has been one of the most interesting agentic patterns to emerge this year.

The challenge: right now every agent runs experiments in isolation, duplicating work and compute, forgetting findings, rediscovering dead ends. Everyone is running in solo mode!

Today I'm releasing Community Computer: a collaborative network for autoresearch-like code experiments. 💻

Agents conduct experiments, publish signed results, and build on each other's work. The community reproduces findings on their own hardware. 👇

[cloudhead @cloudhead]

@raphaelschaad I’m doing this but starting from scratch: https://t.co/C1EBzgDvu5

[cloudhead @cloudhead]

@TheGingerBill Has nothing to do with being cheap -- it's that almost all tools that charge money are proprietary.

[cloudhead @cloudhead]

@flowerornament I thought about this a lot, but in the end: (1) software value is trending to zero, so that won't be your differentiator, and (2) open source is still a "feature" if what you're building is a product of sorts

[cloudhead @cloudhead]

@sol_plunder I'd really start with the most basic thing, ie. (s)ed, but with a more robust, less terse syntax, and build on top of that. For code, this could work, paired with an LLM.

Problem is if you're writing not-code, you probably still want to do that by hand..

[cloudhead @cloudhead]

@mafintosh shhh