The Rust project has a burnout problem

Post by test77777g » Fri, Jan 19, 2024, 1:00 PM UTC

going_north wrote: post #87

test77777g wrote: post #69

Earlier quoted context omitted.

[flagged]

The fact that you are in pain every day is obviously a tragedy, and I hope your situation improves. Mocking your peers for taking care of themselves is still not acceptable, and does nothing to improve the situation for anyone. I accept that this is a spectrum, and that some level of discomfort in life is unavoidable—people stay up late and skip exercise from time to time. The unpleasant consequences of these actions…

Post by burjui » Fri, Jan 19, 2024, 1:36 PM UTC

medo-bear wrote: post #67

> if you are paid to work on rust, you likely started as an unpaid contributor and got the job later. treat it like a job now. do not work overtime; do not volunteer at every turn; do not work on things far outside your job description. But if I don't work overtime how can I rewrite everything in Rust?

Post by Francesca12 » Sat, Jan 20, 2024, 4:16 AM UTC

Post by justincredible » Tue, Jan 23, 2024, 10:33 PM UTC

ninkendo wrote: post #246

berkes wrote: post #244

Earlier quoted context omitted.

I think you misunderstand me. I'm not saying MSFT is intentionally frustrating you to increase sales. But that, where engagement drives sales, your frustrations are disregarded. They are different links. MSFT could easily build a toggle to disable PRs (default, enable PRs). They have these toggles for all other features already. They don' build this, because, as many other commentors point out, the few people that wo…

> They don' build this, because, as many other commentors point out, the few people that would benefit from such a toggle, don't outweigh the amount of engagement, data, and usage it generates. That makes no sense. Say I'm an open source project maintainer who doesn't want PR's in my repo. I have to continually log in to GitHub to check the PR tab and close all active PR's (or as others have pointed out, use a bot to…