Issue #20077 has been updated by kjtsanaktsidis (KJ Tsanaktsidis). Status changed from Open to Feedback It would be good if you could outline in more detail: * What, exactly, about net/http you find hard to use? * Some use-cases where net/http causes problems which could be improved with a different client interface * Why this use-case can't be solved by using one of the many popular Rubygems for this, like Faraday, HTTParty, etc? * What you feel the relationship between stdlib & these gems should be? * Since you mentioned that it's "very very old", whether there is something specific about its age which is a problem? (e.g. are there design assumptions it makes which no longer stack up today?) Without a more specific use-case beyond "net/http is hard to use" it's hard to have a meaningful discussion. ---------------------------------------- Bug #20077: modern http client https://bugs.ruby-lang.org/issues/20077#change-105791 * Author: pynix (Pynix wang) * Status: Feedback * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- net/http is very very old and hard to use. we need a well designed http client in stdlib. -- https://bugs.ruby-lang.org/