@aturon I adore this.

Trying out a small language change:

🙅 “what did I accomplish today”
💁 “what did I contribute today”

I don’t need to achieve, to belong.

omg they finally solved https://wiki.haskell.org/The_JavaScript_Problem

I kid I kid.

I've been trying to figure out how to characterize Starbeam. "Universal hooks" was an early, strong contender, but it feels a bit too React-centric.

That said, "React hooks" capture the lifecycle abstraction aspects of the design in a way that something like "universal reactivity" doesn't.

Thoughts?

Would people be interested in watching livestreams of me coding Starbeam? It's kind of embarrassing and boring, but maybe it's worth doing?

Starbeam 0.8 docs are out!

Next up:

- beefing up the React and Preact docs
- finishing up the API docs
- implementing modifiers
- Vue support
- making a plan for 1.0

#itshappening

@Decypher2 This is also how I feel about "legacy" admissions

Every time I talk to journalists about how ridiculous the effective altruism, longtermism, rationality cults are, I also make a point of letting them know how much I resent having to spend energy explaining why these cults are harmful. Wouldn't have had to do spend all this energy explaining their ridiculous ideologies if they didn't amass so much $$ and influence.

Over on Twitter it’s like the Penguin is in charge of Gotham.

In other news, I should deploy a version without the Vitepress title.

Anyone interested in Starbeam office hours? If so, what structure would work best?

https://www.starbeamjs.com

So we passed the 50k users at 7pm ET today.
Donations are going well so we'll keep growing. I still need to update the Hub page with latest numbers.
Since we are worldwide, I am looking for moderators than are bilingual English + German or Portuguese or Chinese or Spanish or Arabic. French is already covered. Please PM me.
Thank you all for choosing TechHub and let's build a great community.
#techhub #growing

@nicdex Hi! Glad to see @techhub.social doing so well :)

I'm enjoying it so far.

https://www.starbeamjs.com/

The basic idea comes from Ember, which has had services for the better part of a decade.

Any Starbeam renderer that can express a concept of "current app" (via context, for example), can use fully reactive universal services written in Starbeam.

In React, that means wrapping your app in a Starbeam context provider (normal reactivity, including resources, don't require a context provider in Starbeam, but services do).

In Preact, importing `@starbeam/preact` does all the work.

A resource is a reactive formula with cleanup (a universal hook, basically).

A service is a resource that is instantiated once for your entire app, and cleaned up when the app is unmounted.

Basically, your app state goes into services, instead of module state.

This design lets you instantiate an app multiple times (for testing or SSR, for example) without needing to mock modules or other weird stuff.

Also lets you sign users out by just resetting your app state.

Starbeam 0.8 is out:

- Updated Resource API
- Universal Services
- Improved React Renderer
- New Preact Renderer

Docs:

- Demos now use Sandpack
- Code snippets now use Twoslash

Next up:

- Add Preact docs
- Vue renderer
- Plan Starbeam 1.0

Hello world.