News for hackers. Stuff that matters.
Re:Google to Reimplement Curl in Libcrurl by jsty on Wednesday June 19, 2019 @07:23AM (#20222356)
Admittedly they're a little hard to differentiate at first glance, but is 'hostile' not pushing things a little too far? There's a long history of derivatives of open source tools having similar-ish names, often differing by a single letter - just look at all the 'make' derivatives: pmake, bmake, fmake, gmake, rmake, nmake, ... to name but a few that Wikipedia mentions [0].

[0] https://en.wikipedia.org/wiki/Make_(software)#Derivatives

Re:Google to Reimplement Curl in Libcrurl by EwanToo on Wednesday June 19, 2019 @07:33AM (#20222392)
If you launched an alternative search engine called Gooogle, I don't think Google would consider it a friendly move :)
Re:Google to Reimplement Curl in Libcrurl by eesmith on Wednesday June 19, 2019 @08:44AM (#20222763)
Case in point from 2006 - https://www.chemistryworld.com/news/google-chmoogle/3001845.... :

> A new chemistry search engine has been forced to change its name from ’Chmoogle’ to ’eMolecules’ following pressure from the search engine Google.

Re:Google to Reimplement Curl in Libcrurl by Spivak on Wednesday June 19, 2019 @09:34AM (#20223173)
We're talking about two categories of people. The software developers would have no problem with stuff like this. Go ahead and create a UX toolkit called Fluttershy.

But if you mess with someone's actual products that make them money you'd probably hear from their legal team.

Re:Google to Reimplement Curl in Libcrurl by jsty on Wednesday June 19, 2019 @07:48AM (#20222451)
Very true. I probably should've caveated that I don't actually think it's a good name choice, just that I doubt it was chosen to mislead / as an attack on (lib)curl. Given my own uselessness with naming things sometimes, I tend to be forgiving!
Re:Google to Reimplement Curl in Libcrurl by Spivak on Wednesday June 19, 2019 @09:39AM (#20223212)
Like we're talking about software developers here. I think it's funny that when a Google engineer does it there's some shadowy motivation to usurp a FOSS downloader library -- like they aren't like the rest of us picking silly names for things.

"Hey, curl is a super useful tool, it would be nice if it used our new fancy network protocol"

"Yeah, what should we name it?"

"Uhh -- wait, I got it. crurl and the library could be libcrurl"

"Hilarious! It's perfect!"

Re:Google to Reimplement Curl in Libcrurl by rlue on Wednesday June 19, 2019 @07:39AM (#20222415)
Prefixing a word with another letter is perceptually different from slipping one in the middle, especially when the new letter is one of the four letters already in the name. What Google has done here would be more comparable to releasing a new utility called 'mkake'.

As the author of curl points out, it just looks like a typo. When it's this egregious, your only choices are to assume either incompetence or bad faith.

Re:Google to Reimplement Curl in Libcrurl by Spivak on Wednesday June 19, 2019 @09:41AM (#20223227)
I mean don't think for a second that mcake couldn't be the name of a build utility that uses baking terms.

    mcake knead && mcake bake
Re:Google to Reimplement Curl in Libcrurl by huffmsa on Wednesday June 19, 2019 @07:34AM (#20222396)
If not for Google's recent spate of scraping people's stuff and publishing it verbatim with zero attribution, they'd get the benefit of the doubt regarding maliciousness. See genius.com's recent accusations

The smell like some "developer's developer" who thinks he can do a better job of libcurl and is so cocksure that he's going with the name libcrurl. Perhaps he'll put his name on it. Unlikely, as that would require skin in the game.

Re:Google to Reimplement Curl in Libcrurl by laumars on Wednesday June 19, 2019 @07:54AM (#20222472)
crurl and libcrurl look almost visually identical to curl and libcurl - to the point that many on HN genuinely misread Google's names to be their original counterparts.

Whereas your make examples are much easier to visually differentiate.

If curl was trademarked then they would have a strong case here.

Re:Google to Reimplement Curl in Libcrurl by zapzupnz on Wednesday June 19, 2019 @07:28AM (#20222372)
At least those all have the decency to be prefixes. Those are much easier to parse.
Re:Google to Reimplement Curl in Libcrurl by huffmsa on Wednesday June 19, 2019 @07:44AM (#20222433)
Then Google should follow that pattern and call it glibcurl

Which clearly reads as "the g(oogle) implementation of libcurl"

Re:Google to Reimplement Curl in Libcrurl by josteink on Wednesday June 19, 2019 @07:53AM (#20222466)
It could easily be mistaken as a GNU implementation (ref glib, gmake, etc).
Re:Google to Reimplement Curl in Libcrurl by huffmsa on Wednesday June 19, 2019 @07:57AM (#20222483)
Fair. But crurl is something my auto-correct extensions would assume I fat fingered.
Re:Google to Reimplement Curl in Libcrurl by smittywerben on Wednesday June 19, 2019 @10:42AM (#20223798)
Chrome and curl seem like competing products. But I agree. I don't see this as that bad relative to the other things they're doing at the moment (i.e. breaking uBlock, user agent blocking).

In any case I admire curl has a binary size of ~1MB, which is 1/5 the size of my filter list for Chrome.

Re:Google to Reimplement Curl in Libcrurl by simion314 on Wednesday June 19, 2019 @07:51AM (#20222459)
In your examples the first letter is different, the names do not suffer of the confusion issue, me and other people read the name wrong(our eyes or brain tricked us)
Re:Google to Reimplement Curl in Libcrurl by pritambaral on Wednesday June 19, 2019 @07:35AM (#20222402)
Neither of those make derivatives has a likelihood of being readably confused with the original similar to the libcurl/libcrurl comparison.
Re:Google to Reimplement Curl in Libcrurl by maccard on Wednesday June 19, 2019 @08:33AM (#20222686)
Slightly different in that case that they're introducing a new different letter at the start. What if I called my tool mmake, or mkake?