Live data from Hacker News

Linus and Pull Requests (2012)

github.com

51–60 of 77 posts

Re: Linus and Pull Requests (2012)

#51
post #31

Earlier quoted context omitted.

> Reminder that Linus is part of the reason you and I have a job in the first place. yikes, operating systems existed before linus.

Imagine reducing the impact of linux/git/etc to merely an operating system.

Don't you think we'd largely have palette-swapped jobs doing basically the same thing on some BSD derivative instead?

Re: Linus and Pull Requests (2012)

#53

This is a prime example of the white supremacy that runs rampant in the American technology culture. A white man is allowed to emotionally abuse people because of his privilege's. This type of behavior perpetuates a toxic white masculine culture that makes it impossible to create safe spaces for BIPOC in technology.

I mean, this is not even a particularly good troll.

Re: Linus and Pull Requests (2012)

#54
post #50

Earlier quoted context omitted.

> it drives me up a wall when people use it in things like email or Markdown documents Are there many editors that can rewrap long lines in a Markdown-aware way when displaying long lines? I mean if you create an outline with significant nesting depth (like 3+ levels) and all the items are more than one screenwidth worth of text, the editor linewrapping is going to make it impossible to see the structure. Otherwise y…

With your example of a nested list, VSCode will correctly display line-wrapped inner items at the same indentation level.

Do you use VSCode to read your emails and edit Wikipedia?

Will it do this for Markdown inside of comments in C/C++/Rust code?

How does it even know you're using Markdown in comments as opposed to something else?

(I'll have to trust your answers since I don't have a Windows machine, let alone a Visual Studio license)

Re: Linus and Pull Requests (2012)

#55

Earlier quoted context omitted.

No, this is like going to Quentin Tarantino and saying "hey Quentin, here's that work you need for your film, which I did for free," and him screaming at you for not doing your free work exactly how he wanted. Linus has often been a dick. Being offended at being abused for asking a question or doing a relatively normal thing is reasonable. (He's gotten better, recently, because even he acknowledges it's harmed the pr…

People still work with him and he is successful. From what I can see (I've never dealt with Linux community), people that work with him know what to ignore and what to listen to. Moreover, I guess I have a different way to deal with offensive people even if they were serious - to ignore and scoff it off. I would never feel "offended" ever . Offense is taken and it is a choice. That's how I operate but your mileage ma…

> People still work with him

That's part of the problem. A bunch of people effectively didn't have a choice but to put up with this sort of communication style because their job required them to interact with the Linux community.

> Offense is taken and it is a choice.

This is a meaningless platitude. Whether you take offense or not, sometimes the most productive response is to tell someone their behavior is counterproductive, instead of stoically shrugging it off.

Re: Linus and Pull Requests (2012)

#56
post #50

Earlier quoted context omitted.

With your example of a nested list, VSCode will correctly display line-wrapped inner items at the same indentation level.

Do you use VSCode to read your emails and edit Wikipedia? Will it do this for Markdown inside of comments in C/C++/Rust code? How does it even know you're using Markdown in comments as opposed to something else? (I'll have to trust your answers since I don't have a Windows machine, let alone a Visual Studio license)

I mean, there are definitely places where hard wrapping makes sense or is the only option. I’m not saying it’s never the right thing to do, just that with emails or full-Markdown docs specifically it tends to restrict the ability to render in an optimal manner more than it helps.

Re: Linus and Pull Requests (2012)

#57

Earlier quoted context omitted.

People still work with him and he is successful. From what I can see (I've never dealt with Linux community), people that work with him know what to ignore and what to listen to. Moreover, I guess I have a different way to deal with offensive people even if they were serious - to ignore and scoff it off. I would never feel "offended" ever . Offense is taken and it is a choice. That's how I operate but your mileage ma…

> People still work with him That's part of the problem. A bunch of people effectively didn't have a choice but to put up with this sort of communication style because their job required them to interact with the Linux community. > Offense is taken and it is a choice. This is a meaningless platitude. Whether you take offense or not, sometimes the most productive response is to tell someone their behavior is counterpr…

This is the surefire way to create conflict where there could have been a peaceful resolution. Learning to tolerate and ignore is a blessing IMO. If it gets excessive and affect's people's lives, jobs, personal threats, yes - that's not excusable.

It turns out when you ignore people, they get the point. You don't need to bark back at dogs. Keep your head up, mind your own business and move on.

Re: Linus and Pull Requests (2012)

#58
post #23

Earlier quoted context omitted.

Was he level-headed? Talking like that at work might get me fired. It would be better if he just ignored the PR instead of making a scene. Maybe I’m just sensitive

> Was he level-headed? Talking like that at work might get me fired. In my experience, this is very much a cultural thing. The way Linus talks is the usual way that people talk at most of the workplaces I've been at over the years in Australia. However, we're not exactly known as a sensitive people. If something is crap, we call it crap. It isn't generally taken personally. It isn't seen as overly aggressive. If some…

> The number of times I get a 'yes' answer from Asia that absolutely does not mean 'yes' is probably in the high double figures per day.

This has cost me time, money, and caused unnecessary risks.

How do you get around it?

Re: Linus and Pull Requests (2012)

#59
post #23

Earlier quoted context omitted.

> Was he level-headed? Talking like that at work might get me fired. In my experience, this is very much a cultural thing. The way Linus talks is the usual way that people talk at most of the workplaces I've been at over the years in Australia. However, we're not exactly known as a sensitive people. If something is crap, we call it crap. It isn't generally taken personally. It isn't seen as overly aggressive. If some…

I will respectfully disagree with you. I am Australian, and have worked in many workplaces across white and blue collar jobs. What you are describing is an attitude that is fast falling out of favour, and in my mind has died in the last ten years. We do not have a culture of brutal honetsy, and I think that this is a good thing. That honesty may be refreshing to you, but there are many people in the workplace who do…

Honesty is truth and we're working hard to discover it, fix it and engineer things well. If we don't confront truth in favor of hurting people, oh boy... the world is regressing faster than ever.

This is how you get a snowflake organization that has way too many people complaining, not learning to tolerate and generally bickering around about this or that.

FAANG and silicon valley culture unfortunately is moving in that direction, if not leading it. I detest it with a passion.

Re: Linus and Pull Requests (2012)

#60

Earlier quoted context omitted.

> People still work with him That's part of the problem. A bunch of people effectively didn't have a choice but to put up with this sort of communication style because their job required them to interact with the Linux community. > Offense is taken and it is a choice. This is a meaningless platitude. Whether you take offense or not, sometimes the most productive response is to tell someone their behavior is counterpr…

This is the surefire way to create conflict where there could have been a peaceful resolution. Learning to tolerate and ignore is a blessing IMO. If it gets excessive and affect's people's lives, jobs, personal threats, yes - that's not excusable. It turns out when you ignore people, they get the point. You don't need to bark back at dogs. Keep your head up, mind your own business and move on.

Not acknowledging it when someone's causing problems under the banner of "taking offense is a choice" is definitely a surefire way to make problems worse, too.
Post reply on HN