News for hackers. Stuff that matters.
Re:Google to Reimplement Curl in Libcrurl by carlsborg on Wednesday June 19, 2019 @06:55AM (#20222245)
Dear Google Chrome Folks,

Please rename your library.

Thanks

Re:Google to Reimplement Curl in Libcrurl by vkaku on Wednesday June 19, 2019 @07:08AM (#20222297)
How about libcruel - Chrome reimplementing usable external libraries
Re:Google to Reimplement Curl in Libcrurl by grosswait on Wednesday June 19, 2019 @08:46AM (#20222781)
Or libcrocurl and crocurl. Lots of better options.
Re:Google to Reimplement Curl in Libcrurl by ademarre on Wednesday June 19, 2019 @09:25AM (#20223094)
libchrurl

It's visually more distinct than libcrurl while retaining an appropriate resemblance to libcurl.

One could argue that some resemblance in name is a good thing for curl. But libcrurl is too close and likely to cause confusion.

Re:Google to Reimplement Curl in Libcrurl by EwanToo on Wednesday June 19, 2019 @07:03AM (#20222282)
libcrurl vs libcurl, I know naming things is hard but this just seems hostile against the Curl developer.
Re:Google to Reimplement Curl in Libcrurl by TheCycoONE on Wednesday June 19, 2019 @07:46AM (#20222438)
Could be worse - like when MS added curl as a powershell alias. https://github.com/PowerShell/PowerShell/pull/1901
Re:Google to Reimplement Curl in Libcrurl by Spivak on Wednesday June 19, 2019 @09:30AM (#20223132)
I really don't see what all the drama was over. Those aliases are incredibly valuable to me. I can never remember the PS equivalents of unix-y commands and those aliases let me use my current muscle memory.

Sure the options are different but it's really not all that different than switching between GNU/Linux, MacOS, and BSD and having to deal with differences.

    PS> cd C:\Users\
    PS> ls
    PS> wget https://example.com
And it makes discovery super easy when you can Get-Help just about every unix command and it will show you more-or-less the appropriate equivalent. The thread just looks like a bunch of people with a bone to pick against MS trying to take some moral high-ground with a change that was added to genuinely help users.
Re:Google to Reimplement Curl in Libcrurl by signal11 on Wednesday June 19, 2019 @09:23AM (#20223066)
Windows 10 builds have included a 'real' curl for about a year now (build 1803 onwards IIRC)[1]

[1] https://daniel.haxx.se/blog/2018/01/13/microsoft-curls-too/

Re:Google to Reimplement Curl in Libcrurl by smittywerben on Wednesday June 19, 2019 @02:48PM (#20226088)
Just to reiterate- in Windows 8/Server 2012 (PS ~3-5), writing "curl" would just alias to "Invoke-WebRequest". Prior discussion from 2016 on hn[0].

But since December 2017, Windows 10 build 1803 includes curl.exe (along with ssh!) These deprecated my use of chocolatey, and hopefully moves people away from Putty.

[0] https://news.ycombinator.com/item?id=12319670

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?
Re:Google to Reimplement Curl in Libcrurl by TheRealPomax on Wednesday June 19, 2019 @07:58AM (#20222488)
don't assume malice when "we suck at names and the first dumb name seems to stick without a marketing department overriding the naming choice" is also an option.
Re:Google to Reimplement Curl in Libcrurl by huffmsa on Wednesday June 19, 2019 @08:02AM (#20222511)
Marketing is busy branding the next 5 years worth of annual messaging applications.
Re:Google to Reimplement Curl in Libcrurl by TheRealPomax on Sunday June 23, 2019 @05:57PM (#20258933)
A company I once worked for spent $40,000 to find a good product name. It ended up being the same name people had already pitched for free internally.
Re:Google to Reimplement Curl in Libcrurl by captainbland on Wednesday June 19, 2019 @09:44AM (#20223257)
They missed a trick by not naming it libgurl.
Re:Google to Reimplement Curl in Libcrurl by rauhl on Wednesday June 19, 2019 @07:56AM (#20222481)
libcruller is available, is close enough to be clearly related and far enough away not to look like a typo. Also … mmm, tasty crullers.
Re:Google to Reimplement Curl in Libcrurl by avip on Wednesday June 19, 2019 @08:20AM (#20222599)
Propose LibTrurl

Pros: main class c'tor could be called TrurlTheConstructor

Cons: everything else

Re:Google to Reimplement Curl in Libcrurl by AlbertoGP on Wednesday June 19, 2019 @07:43AM (#20222431)
Is it too late for them to name it “Goorl”?
Re:Google to Reimplement Curl in Libcrurl by josteink on Wednesday June 19, 2019 @07:52AM (#20222462)
LibGurgurl
Re:Google to Reimplement Curl in Libcrurl by unethical_ban on Wednesday June 19, 2019 @08:44AM (#20222764)
It's doubly egregious given they work for a search engine that will immediately try to autocorrect that.
Re:Google to Reimplement Curl in Libcrurl by 0xFluegel on Wednesday June 19, 2019 @09:18AM (#20223025)
It'll be even worse when the search engine later magically ranks their's higher even when searching for the original.
Re:Google to Reimplement Curl in Libcrurl by dalf on Wednesday June 19, 2019 @09:02AM (#20222874)
The irony is when I've searched for "libcrurl" using Google, I got the result for "libcurl".
Re:Google to Reimplement Curl in Libcrurl by lifthrasiir on Wednesday June 19, 2019 @09:16AM (#20223006)
Of course it should be renamed to libdivergence. But joking aside, is "crurl" even a word after all?
Re:Google to Reimplement Curl in Libcrurl by willnorris on Wednesday June 19, 2019 @07:06PM (#20228238)
Re:Google to Reimplement Curl in Libcrurl by ben0x539 on Wednesday June 19, 2019 @10:15AM (#20223537)
and lets not be clever, if its a libcurl api for this cronet thing, call it cronet-libcurl or libcurl-cronet or something
Re:Google to Reimplement Curl in Libcrurl by wiggler00m on Wednesday June 19, 2019 @08:28AM (#20222651)
How about "gurl" or "gurgle"?