Earlier quoted context omitted.
> This is a good description of what life is like working on almost any significant open source project. Open contributions project. An open source project does not necessarily have to accept random contributions, issues or hatemail from the general public. [1] They just need to make the source available with a permissive licence, period. I believe that Linux with its idiosyncrasies in its communication model (mailin…
I strongly believe GitHub has the same dynamics as most "big tech social media". Where anything that drives "engagement" gets prioritized. From algorithms that make alt-right/neo-nazi's more visible because the controversy drives "eyeballs" to features that are removed or never implemented because they would lower engagement. I'm confident that GitHub has a good prediction on what will happen if they roll out feature…
The Rust project has a burnout problem
111–120 of 258 posts
Re: The Rust project has a burnout problem
#112This is why I think that C++ will be around in the next 50 years but Rust? I can't tell.
Re: The Rust project has a burnout problem
#113Earlier quoted context omitted.
It comes across as saying "fuck you" to your readers.
FWIW, not to me. Variety is the spice of life. It’s their blog, they should use whatever style they feel like using. Besides, is lowercase poetry a fuck you to the reader as well?
Re: The Rust project has a burnout problem
#114Do other people react as strongly as I did to the lack of capitalisation at the start of sentences? The post is generally "well" written with good grammar and punctuation so I find it strange - it feels like a style choice. But the style choice just instinctively makes part of my brain feel like it's written by a child.
Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.
Re: The Rust project has a burnout problem
#115Do other people react as strongly as I did to the lack of capitalisation at the start of sentences? The post is generally "well" written with good grammar and punctuation so I find it strange - it feels like a style choice. But the style choice just instinctively makes part of my brain feel like it's written by a child.
Re: The Rust project has a burnout problem
#116This is a good description of what life is like working on almost any significant open source project. The only thing not included was the comments from overly entitled users that saps whatever morale and energy you have left. Probably best he did not include that though as that is what all discussion would be about. I am not sure what to do about the burnout problem. The way he described it is very on point though.…
>I am not sure what to do about the burnout problem. Get paid for it, and don't do anything more than you are paid to do. I've done volunteer work, per se. My biggest takeaway has been that humanity overall is not worth giving away my free time to. When I volunteer my time now, I do so only for individuals who I know will sincerely appreciate it.
Re: The Rust project has a burnout problem
#117Earlier quoted context omitted.
Oh, hey! Thanks for chiming in. It's rare to see rejection of grammar rules on longer forms of writing, so it looked interesting. Any special reasons? Just because I like to know people through their choices and views. Didn't want to sound rude in the previous comment, so if I did, genuinely sorry (non-native speaker woes).
two reasons: 1. writing in lowercase is freeing. it reminds me that grammatical rules are arbitrary, and by extension other rules. "you can just do things." 2. people who are pedantic about this when it's clearly intentional are probably not people i want to interact with anyway, so it's a good anti-asshole filter ( https://siderea.dreamwidth.org/1209794.html )
I guess it's like user interface design, where a cardinal rule is to be conservative, and not break user expectations unduly.
Of course UI patterns and language evolves, but the evolution of changes should probably be gradual, and done for a justifiable purpose. In this case, I'm not sure the stylistic choice actually adds anything to the clarity or beauty of the writing.
Re: The Rust project has a burnout problem
#118Earlier quoted context omitted.
my shift key is there i just have conscientiously objected to it
If we could beam our thoughts directly into each other's head, we would. It would be the easiest way to convey information. Alas, we don't have that ability, so we resort to the written word. If your goal is to spread something interesting don't make it more difficult for your readers by hiding your point behind a style choice that directly contradicts the readers' expectations. Capitalization goes hand-in-hand with…
Re: The Rust project has a burnout problem
#119Earlier quoted context omitted.
I strongly believe GitHub has the same dynamics as most "big tech social media". Where anything that drives "engagement" gets prioritized. From algorithms that make alt-right/neo-nazi's more visible because the controversy drives "eyeballs" to features that are removed or never implemented because they would lower engagement. I'm confident that GitHub has a good prediction on what will happen if they roll out feature…
It would be a baffling decision for GitHub to make any product decisions based on engagement. They don’t even serve ads, what benefit do they have to an engaged user?
Re: The Rust project has a burnout problem
#120Earlier quoted context omitted.
I strongly believe GitHub has the same dynamics as most "big tech social media". Where anything that drives "engagement" gets prioritized. From algorithms that make alt-right/neo-nazi's more visible because the controversy drives "eyeballs" to features that are removed or never implemented because they would lower engagement. I'm confident that GitHub has a good prediction on what will happen if they roll out feature…
It would be a baffling decision for GitHub to make any product decisions based on engagement. They don’t even serve ads, what benefit do they have to an engaged user?
https://github.com/orgs/community/discussions/13130
https://github.com/orgs/community/discussions/65343
The feedback is overwhelmingly negative, and has severely disrupted many people's workflow, but GitHub doesn't even acknowledge the problem.