Buy commercial curl support from
WolfSSL. We help you work out your issues, debug your libcurl
applications, use the API, port to new platforms, add new features and more.
With a team lead by the curl founder himself.
Re: Sv: If you're using an official curl for Windows 32-bit build instead of 64-bit please tell us why
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-users <curl-users_at_lists.haxx.se>
Date: Thu, 14 Mar 2024 08:27:13 +0100 (CET)
On Wed, 13 Mar 2024, Art KnsZ via curl-users wrote:
>> You are most welcome to help us improve the documentation.
>
> And a snarky response like this is a poster child of why I, and many others,
> do not bother to contribute.
That snark was added in your head. It certainly was not in my mind when I
wrote that response.
I have spent a condiderable amount of time writing documentation for curl. It
is *hard* to write documentation that reaches all users correctly in their
various knowledge levels and different expectations etc.
The person that has a documentation problem right now is in the best possible
position to help out fixing that.
(Based on experience) I don't assume that everyone involved remembers and
properly considers the fact that curl is open source and is the product of
mostly volunteers chipping in their little efforts so that the combined
results become something useful. *Everyone* can help improve all aspects -
including the documentation.
I think newcomers with their fresh eyes on the project can provide valuable
feedback and help us improve, for other newcomers. For us who have been doing
internet transfers for multiple decades already, I figure it is easy to miss
out making newcomer friendly documentation simply because we've forgotten how
it was to be there.
Date: Thu, 14 Mar 2024 08:27:13 +0100 (CET)
On Wed, 13 Mar 2024, Art KnsZ via curl-users wrote:
>> You are most welcome to help us improve the documentation.
>
> And a snarky response like this is a poster child of why I, and many others,
> do not bother to contribute.
That snark was added in your head. It certainly was not in my mind when I
wrote that response.
I have spent a condiderable amount of time writing documentation for curl. It
is *hard* to write documentation that reaches all users correctly in their
various knowledge levels and different expectations etc.
The person that has a documentation problem right now is in the best possible
position to help out fixing that.
(Based on experience) I don't assume that everyone involved remembers and
properly considers the fact that curl is open source and is the product of
mostly volunteers chipping in their little efforts so that the combined
results become something useful. *Everyone* can help improve all aspects -
including the documentation.
I think newcomers with their fresh eyes on the project can provide valuable
feedback and help us improve, for other newcomers. For us who have been doing
internet transfers for multiple decades already, I figure it is easy to miss
out making newcomer friendly documentation simply because we've forgotten how
it was to be there.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2024-03-14