2 ms·
I had thought of this after my original comment. Windows provides a slightly different set of assumptions that a traditional UNIX-like platform. Mainly, that
by kbenson 9y ago
I had thought of this after my original comment. Windows provides a slightly different set of assumptions that a traditional UNIX-like platform. Mainly, that piping is not as common and the chances that the operating system the tool is deployed on will be used as a server at much reduced. There are a couple middle-ground solutions which might be worth exploring:
- Only build that functionality on windows. Optionally, provide two packages for windows, one with URL fetching and one without it.
- Provide a flag that enables/disables the feature. Either default toit off and allow it to be enabled with a flag (and a helpful error message if oyu attempt to use it without a flag) or vice-versa.
- Do nothing. In the end, it's an entirely valid decision to leave it as it is unchanged. I thought it was something worth discussing, both for this tool and for the larger trend in general, but that doesn't mean the problem is so large that it makes the tool unusable until addressed.
In any case, thanks for making this. The simplicity and obvious usefulness of this tool means that as someone who deals with JSON quite often, generally in an archived form where I care about one or two entries in lists of hundreds, I imagine I'll be finding lots of use for it in the future.