Re: libcrurl

2019-06-20 Thread Daniel Ferradal
It seems there may have been certain misunderstanding.

Daniel Stenberg published this tweet linking to googler apologizing
for the mess in his twitter account:
https://twitter.com/bagder/status/1141653215685087232
And the link of the apology: https://news.ycombinator.com/item?id=20228237

El mié., 19 jun. 2019 a las 22:37, Dennis Clarke
() escribió:
>
> On 6/19/19 10:13 AM, Stefan Eissing wrote:
> > I just want to mention that I have no plans to adapt the upcoming Chrome 
> > library libcrurl (see 
> > https://daniel.haxx.se/blog/2019/06/19/google-to-reimplement-curl-in-libcrurl/
> >  ).
> >
> > And, boy, do I hope they have no plans to do the same with our product 
> > names.
> >
>
> If one waits long enough we get to see the same behavior repeat itself
> over and over and over. Same as the '90s with Microsoft where they would
> adopt some defacto standard, extend it well out beyond what the original
> standard ever did and then kill the original.  However MS were unable to
> kill TCP/IP and failed in many ways with many of their little ideas. So
> this behavior by Google is just ... silly. At best. Stupid would be a
> better word.  It may be time to stop using Chrome everywhere and just be
> good open source humans and focus on the upstream FireFox which works
> just awesome everywhere.  My 0.02bt worth.
>
>
> --
> Dennis Clarke
> RISC-V/SPARC/PPC/ARM/CISC
> UNIX and Linux spoken
> GreyBeard and suspenders optional



-- 
Daniel Ferradal
HTTPD Project
#httpd help at Freenode


Re: libcrurl

2019-06-19 Thread Dennis Clarke

On 6/19/19 10:13 AM, Stefan Eissing wrote:

I just want to mention that I have no plans to adapt the upcoming Chrome 
library libcrurl (see 
https://daniel.haxx.se/blog/2019/06/19/google-to-reimplement-curl-in-libcrurl/ 
).

And, boy, do I hope they have no plans to do the same with our product names.



If one waits long enough we get to see the same behavior repeat itself
over and over and over. Same as the '90s with Microsoft where they would
adopt some defacto standard, extend it well out beyond what the original
standard ever did and then kill the original.  However MS were unable to
kill TCP/IP and failed in many ways with many of their little ideas. So
this behavior by Google is just ... silly. At best. Stupid would be a
better word.  It may be time to stop using Chrome everywhere and just be
good open source humans and focus on the upstream FireFox which works
just awesome everywhere.  My 0.02bt worth.


--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional


libcrurl

2019-06-19 Thread Stefan Eissing
I just want to mention that I have no plans to adapt the upcoming Chrome 
library libcrurl (see 
https://daniel.haxx.se/blog/2019/06/19/google-to-reimplement-curl-in-libcrurl/ 
).

And, boy, do I hope they have no plans to do the same with our product names.

Cheers, Stefan