damagednoob

>Andre has previously maintained that he owns a trademark on Bundler and he will enforce it against Ruby Central.

Well,

1. He's not fighting Ruby Central anymore, he'd be fighting the Ruby core team.

2. He's going to have a tough time asserting copyright on a name he didn't come up with on a project which shipped v1 before he joined.

3. If he believes the trademark belongs to the community, the right thing to do would be to transfer it to Ruby Core then, right?

Seems like a few old scores are being settled during this drama. It wouldn't surprise me if a lot of people on the side of RubyGems are avoiding commenting in case any legal disputes play out.

To be consistent, then the same goes for Shopify.

I think the thrust of the point is that it's not 'traditional'.

One might suggest that you may not be the only target demographic of Amazon.

When developing a small program for my Synology NAS in Go, I'm sure I had to target a specific version of glibc.

Should Automattic be compelled to subsidise their competitors?

> If nobody or barely anyone used Megaupload, he wouldn’t have been in as much trouble.

In a world where opportunity costs exist, as they do for law enforcement, this makes sense?

Did I miss the justification for the switch to Java? That decision seemed to come out of the blue.

Something I've observed as an English speaking immigrant is that in general, the US/UK is very forgiving when it comes to foreigners trying to speak English. Where certain types of phrasing and harsh words would not be tolerated with first language English speakers, the benefit of the doubt is given to 2nd/3rd language speakers because they

1. Might not have the vocabulary to express themselves correctly

2. Not understand the nuance and connotations that their word choices imply

I've seen my colleagues get frustrated in meetings while simulatenously having to assume good intent.

Choosing names like the bad actor(s) did gives them an advantage in this scenario.

I think the reason that JSON won was that at least on the client-side, it was much easier to turn the response data into a Javascript object to interact with then XML.