You are reading content from Scuttlebutt
@Christian Bundy %Eu0pMsUHaoEmkKMBiXn10XHYi9QxlSeCpowdigVgkjk=.sha256
Re: %9NXKauuXC

Hi all.

  • I'd be happy to move that money toward people doing work in the ecosystem.
  • I'm kinda burnt out on Oasis, and lots of the SSB stack in general.
  • I think I'd be most excited about paying maintainers for their continued attention (SSB-JS?) or paying people to fix underlying problems deep in the stack. I'm worried about the amount of time + energy it takes to keep adding layers and features without fixing the underlying stuff.
  • I'm happy to be a resource for some of this, but I'm unlikely to pour lots of time or energy into new features for Oasis. ❤
User has not chosen to be hosted publicly
@~daan 📟 %+3ql+n5wm7gdJoSs1VOCF51kbtd1N3hmaCUfFxxsiJU=.sha256

Thanks to manyverse's somewhat ineffable ways, I just stumbled over this one again .
Thank you for sharing, @Christian.
This pattern is quite real throughout the ssb stack. And I think this can't stay this way. A sustainable effort can't be built on finding a new torch bearer every other month, just to see them burn out.

After spending the better part of a year living in JS land I don't consider myself experienced in the ways of the scriptures but I think I've seen a bunch of the pains one gets to see when entering this ecosystem. I feel like this tendency of being exhausting is maybe not directly causally related to the language, but maybe to the dev culture/ecosystem around it.
The way that JS libraries/apps (and patchwork is no exception here, oasis is better though) keep stacking leaky abstractions on top of each other seems... it seems to be encouraged by the tooling and generally by the JS community.

I'm happy that the feature-based funding worked I this instance. Maintenance will have to look differently.

I hope you're not burnt out on ssb in general. I think the best is yet to come :)

Join Scuttlebutt now