3 ms·

Awesome complimentary program to the `jq` tool. However... I do wish the name was `json` not `jo`. In my case more for personal reasons regarding painful memo

Awesome complimentary program to the `jq` tool. However... I do wish the name was `json` not `jo`. In my case more for personal reasons regarding painful memories attached to the name 'Jo', but I also think the tool creates JSON, so why not call it `json` or `jp` short for 'json print' ... but the matter appears settled. Oh well.

jvehent 11y ago
echo 'alias json="$(which jo)"' >> ~/.bashrc
- iokanuon 11y ago
  echo 'alias json=jo' >> ~/.bashrc Or even better sudo ln -s $(which jo) /usr/local/bin/json
- techdragon 11y ago
  Yes I can always do this sort of thing. But it would be nice to not 'maintain the illusion' when the future day comes that I've got `jo` installed on my various desktops and laptops, inside containers, on snowflake servers, on cattle servers, used by a growing collection of shell scripts written for various versions of sh and bash, etc...
  - fiatjaf 11y ago
    I feel the same. All these smart small tools are amazing, but they suppose the user has only one computer and does everything on it. so he can just install once and that's it. I normally use 4 different desktops and 2 VPSs weekly. Although I tend to do most of the work in one of the VPSs, the more I customize it with tools like this, the more all the other computers will miss things. What is the solution?
    - phunge 11y ago
      I found that learning ansible and storing my machine customization as a deployable playbook was totally worth the effort involved.
      - fiatjaf 11y ago
        Does that ansible thing support incremental deploys? Such that installing 'jo' here will idempotently install it on other machines?
        corobo 11y ago
        Late to the party but yes. The idea behind ansible seems to be (I'm new to using it) that you can run the command a million times over a million machines and it'll only install new things to the machines that don't already have it
  - ythl 11y ago
    Fork the repository, rename it, only clone from your fork.
kaoD 11y ago
`jo` is probably short for 'json output'.
- jpmens 11y ago
  It actually started out meaning `JSON Object'. (Arrays came later. :-)
  - r0muald 11y ago
    "JavaScript Object Notation Object"? ;-)
    - Saavedro 11y ago
      Yes. A JSON Object is not an ATM Machine.
  - techdragon 11y ago
    I did wonder a bit what the origin of the name was, thanks for the info.

jvehent 11y ago

echo 'alias json="$(which jo)"' >> ~/.bashrc

iokanuon 11y ago
echo 'alias json=jo' >> ~/.bashrc Or even better sudo ln -s $(which jo) /usr/local/bin/json
techdragon 11y ago
Yes I can always do this sort of thing. But it would be nice to not 'maintain the illusion' when the future day comes that I've got `jo` installed on my various desktops and laptops, inside containers, on snowflake servers, on cattle servers, used by a growing collection of shell scripts written for various versions of sh and bash, etc...
- fiatjaf 11y ago
  I feel the same. All these smart small tools are amazing, but they suppose the user has only one computer and does everything on it. so he can just install once and that's it. I normally use 4 different desktops and 2 VPSs weekly. Although I tend to do most of the work in one of the VPSs, the more I customize it with tools like this, the more all the other computers will miss things. What is the solution?
  - phunge 11y ago
    I found that learning ansible and storing my machine customization as a deployable playbook was totally worth the effort involved.
    - fiatjaf 11y ago
      Does that ansible thing support incremental deploys? Such that installing 'jo' here will idempotently install it on other machines?
      - corobo 11y ago
        Late to the party but yes. The idea behind ansible seems to be (I'm new to using it) that you can run the command a million times over a million machines and it'll only install new things to the machines that don't already have it
- ythl 11y ago
  Fork the repository, rename it, only clone from your fork.

kaoD 11y ago

`jo` is probably short for 'json output'.

jpmens 11y ago
It actually started out meaning `JSON Object'. (Arrays came later. :-)
- r0muald 11y ago
  "JavaScript Object Notation Object"? ;-)
  - Saavedro 11y ago
    Yes. A JSON Object is not an ATM Machine.
- techdragon 11y ago
  I did wonder a bit what the origin of the name was, thanks for the info.