News for hackers. Stuff that matters.
Re:The time might come when we add some JSON specific comman... by jedberg on Thursday January 20, 2022 @01:36PM (#30012759)
It's a lot easier for a distro to update a default utility than to add a new one though. I suspect having updated curl would happen faster than adding httpie to the list of default utilities.
Re:The time might come when we add some JSON specific comman... by derefr on Thursday January 20, 2022 @02:01PM (#30013086)
Especially singe HTTPie is a python package. curl exists even in plenty of embedded systems, in many Docker base-images, etc.; but scripting runtimes like Python generally don't.
Re:The time might come when we add some JSON specific comman... by sneak on Thursday January 20, 2022 @04:38PM (#30015451)
I wish this were the case. Unfortunately for us grownups that run stable/LTS distros, non-security updates like these don't usually make it to us for like 5 years or something.

There's a happy medium, and we're not in it.

Re:The time might come when we add some JSON specific comman... by fragmede on Friday January 21, 2022 @05:31AM (#30021676)
It depends. How long did to take for bash4-isms to get adopted? Sometimes the update time for more basic utilities, for all systems can take a long time. (Apple switching to zsh doesn't help here.)
Re:The time might come when we add some JSON specific comman... by bonkabonka on Thursday January 20, 2022 @02:23PM (#30013452)
Except if it's an enterprisey distro, it won't get updated. Specifically RHEL 7 ships 7.29.0 and cherry-picks features (TLS handshakes) to backport to their nine-year-old version.
Re:The time might come when we add some JSON specific comman... by thwarted on Thursday January 20, 2022 @01:55PM (#30013011)
The exact opposite is more likely true, depending on the nature of the change. A new utility has no current usage so there are no in-the-wild backwards compatibility concerns. The system python on redhat based distros was stuck at 2 for a long time because some of the sysadmin utilities relied on it and all those deps needs to be vetted or converted to either a newer python version or their own shipped version of the runtime that didn't use the general purpose python install.
Re:The time might come when we add some JSON specific comman... by jedberg on Thursday January 20, 2022 @02:09PM (#30013193)
Python is a huge outlier in this case. Very rarely do you have a default tool that can't be upgraded, and this case was only because Python is an interpreted language.

Curl is a command line tool. As long as they only add new functionality, there is very little that prevents an upgrade.

Re:The time might come when we add some JSON specific comman... by jsight on Thursday January 20, 2022 @02:01PM (#30013082)
There's a big difference between a bump to the latest curl version and a jump between two major versions of a language runtime. The Python 2->3 transition took years and many distros kept both versions.

Most dependencies get updated much more quickly. It wouldn't even shock me if this change got picked up mid-cycle.

Re:The time might come when we add some JSON specific comman... by bonkabonka on Thursday January 20, 2022 @02:19PM (#30013365)
Unhappily RedHat won't. Heck, RedHat has gone well out of their way to backport updated TLS handshakes (1.2 at least) to their 2013 version (7.29.0) of curl.
Re:The time might come when we add some JSON specific comman... by jsight on Monday January 24, 2022 @11:27AM (#30059789)
I'm assuming that you mean for RHEL? That's a little bit of a special case.
Re:The time might come when we add some JSON specific comman... by ericbarrett on Thursday January 20, 2022 @02:09PM (#30013194)
This is only a valid comparison if curl deprecates or moves options, as Python 3 did with language features and standard library functions.