"Working on a project" doesn't only mean pushing commits. It also means deciding what to do, syncing with committees, running a team structure, thinking about how and where to get funding, and handling the mental pressure of "I'm responsible for this". https://twitter.com/sebmck/status/1392025650014326789

@sebmck you ran a crowdfunding campaign and you know how draining it is. If Henry didn't take over Babel when you left, the project could be dead by now.

Henry didn't have to do this. Maintaining Babel has inflicted huge stress on him. He could've easily looked for a *much* higher paying full time job but he decided to stay and try because he felt it was the right thing to do.

It's disheartening to see someone who practically threw his maintenance responsibility to Henry now openly criticizing Henry for "not doing enough". No, you shouldn't be doing this.

Is 130k a lot for someone living in NYC? Henry probably was making more than that even before he quit to work full-time on Babel.

Is 130k a lot for someone who keeps Babel, which is used by millions of devs, which effectively served as the testing ground for ES next proposals, afloat? Heck I'd say that's even too little.

The fact that Henry is willing to take a pay cut is *not* because he felt he's not doing enough, but because given current funding situation, that's the only way to keep the project going. It's like a founder taking a paycut. Do they do that because they are "not doing enough"?