3 ms·

You don't have to "get" anything. If Java works for you, great!! Go just works better for some of us, and that's all the justification we need.

by bmurphy1976 11y ago

Myrmornis 11y ago
This type of comment is common, but specious. It sounds nice: "what works for you; great! this works for me" but it undermines a large category of important discussions: e.g. analyzing which, out of several competing discussions, is a better fit for large classes of people, or on average. In other words, I think this sort of comment strays too far in the direction of niceness, and tends to undermine simple, and desirable, notions of better vs. worse, etc. TL;DR being nice and polite is over-rated. Some things are wrong and it is helpful to say so.
- bmurphy1976 11y ago
  > TL;DR being nice and polite is over-rated. Some things are wrong and it is helpful to say so. And thus continues the never ending cycle of "You're wrong! No you're wrong!"
  - krylon 11y ago
    The problem, I think, or at least part of the problem, is that it is hard to discuss the relative merits and problems of languages (frameworks, operating systems, ...) without feeling like somebody is trying to push his/her favorite piece of tech on somebody else. If we discuss what e.g. Java does better than Go and vice versa for purely technical interest, there is little emotional pressure. But if I feel that somebody is trying to make me use Java (or Rust, or C++, or Visual Basic) over whatever I prefer and feel comfortable with, I get defensive. When people get defensive, they become unwilling to admit shortcoming in their preferred language/framework/OS/..., and so the debate devolves into "You're wrong! - No, you're wrong!" and namecalling.
    - bmurphy1976 11y ago
      I agree 100%. Also, a lot of good devs have poured their heart and soul into golang. They are a part of this community, like it or not. They find go news interesting, but I totally feel for them that every conversation feels like somebody kicking their sandcastle down because "theirs is better.". Same goes for nodejs. Same goes for PHP. Same goes for every language actually. A person may have the best of intentions, but they need to realize that their words can have unintended consequences. There are places times and ways to properly discuss go's shortcomings, but there are also times when it is wildly inappropriate. This is a good event for a very hardworking and capable part of oyr community. They deserve a little respect.
- autoreleasepool 11y ago
  I didn't even interpret that as politie. That's the kind of "polite" comment I would make if I thought you were being an an aggressive idiot and I didn't care to help you. i.e. You think Andoid apps have the same revenue potential as iOS apps? That swell! Good for you buddy, whatever works for you is fine with me :) (Now go back to your cubicle and stop bothering me me.)
  - bmurphy1976 11y ago
    Well that's certainly not what I intended. Only further proves my point that our words can have unintended consequences.

You don't have to "get" anything. If Java works for you, great!! Go just works better for some of us, and that's all the justification we need.

Myrmornis 11y ago

This type of comment is common, but specious. It sounds nice: "what works for you; great! this works for me" but it undermines a large category of important discussions: e.g. analyzing which, out of several competing discussions, is a better fit for large classes of people, or on average. In other words, I think this sort of comment strays too far in the direction of niceness, and tends to undermine simple, and desirable, notions of better vs. worse, etc. TL;DR being nice and polite is over-rated. Some things are wrong and it is helpful to say so.

bmurphy1976 11y ago
> TL;DR being nice and polite is over-rated. Some things are wrong and it is helpful to say so. And thus continues the never ending cycle of "You're wrong! No you're wrong!"
- krylon 11y ago
  The problem, I think, or at least part of the problem, is that it is hard to discuss the relative merits and problems of languages (frameworks, operating systems, ...) without feeling like somebody is trying to push his/her favorite piece of tech on somebody else. If we discuss what e.g. Java does better than Go and vice versa for purely technical interest, there is little emotional pressure. But if I feel that somebody is trying to make me use Java (or Rust, or C++, or Visual Basic) over whatever I prefer and feel comfortable with, I get defensive. When people get defensive, they become unwilling to admit shortcoming in their preferred language/framework/OS/..., and so the debate devolves into "You're wrong! - No, you're wrong!" and namecalling.
  - bmurphy1976 11y ago
    I agree 100%. Also, a lot of good devs have poured their heart and soul into golang. They are a part of this community, like it or not. They find go news interesting, but I totally feel for them that every conversation feels like somebody kicking their sandcastle down because "theirs is better.". Same goes for nodejs. Same goes for PHP. Same goes for every language actually. A person may have the best of intentions, but they need to realize that their words can have unintended consequences. There are places times and ways to properly discuss go's shortcomings, but there are also times when it is wildly inappropriate. This is a good event for a very hardworking and capable part of oyr community. They deserve a little respect.
autoreleasepool 11y ago
I didn't even interpret that as politie. That's the kind of "polite" comment I would make if I thought you were being an an aggressive idiot and I didn't care to help you. i.e. You think Andoid apps have the same revenue potential as iOS apps? That swell! Good for you buddy, whatever works for you is fine with me :) (Now go back to your cubicle and stop bothering me me.)
- bmurphy1976 11y ago
  Well that's certainly not what I intended. Only further proves my point that our words can have unintended consequences.