jkbr
Joined 15 years ago
Karma
1,606
Submissions
164
Member since
Feb 4
Recent submissions
Comment · 2 years ago
Please see my reply here: https://news.ycombinator.com/item?id=41337485
Comment · 2 years ago
What is it that makes the web documentation atrocious in your view?
As for man pages, HTTPie has been shipping them since v3.2 [1].
Try `man http` or `http --manual`.
Comment · 2 years ago
HTTPie creator here. Just a clarification: HTTPie is still under the same management, and the CLI doesn’t have any telemetry. Little Snitch is probably warning you about requests to packages.httpie.io/latest.json [0]. That is done to let you know when a new version becomes available. It’s a static file hosted through GitHub pages [1] without any tracking. However, there’s currently a bug [2] that prevents the response from getting cached so that the request fires frequently for some users. It’s already fixed in a PR [3] and will be part of the upcoming release.
[0] https://github.com/httpie/cli/blob/master/httpie/internal/up...
[1] https://github.com/httpie/packages.httpie.io/blob/master/lat...
Comment · 3 years ago
Thanks!
Comment · 3 years ago
Gotcha. Would you mind checking if you happen to have PyOpenSSL installed inside the Python environment HTTPie runs from?
Comment · 3 years ago
I don’t know when you last tested the start-up time, but we significantly improved it in HTTPie CLI 3.0 [0]. Now it’s still slower by ~0.1s.
$ time http --version
3.2.2
real 0m0.113s
user 0m0.087s
sys 0m0.020s
$ time xh --version
xh 0.18.0
-native-tls +rustls
real 0m0.007s
user 0m0.002s
sys 0m0.002s
Comment · 3 years ago
Whoever posted it thought otherwise.
Comment · 3 years ago
Are you the @prmoustache on GitHub with zero public repos?
Comment · 3 years ago
> Why is the license for this GUI tool so different than the license for their command line tool? The source isn’t even in this repository.
The desktop app is not ready to be open-sourced yet.
> There is 0% chance that this will avoid the route that POSTman and Insomnia have paved.
HTTPie has been around for 10+ years, and the new desktop product is built around the idea that we can do much better than the incumbents (from a much simpler interface and more pleasant UX to a more aligned set of incentives supporting incognito, free, as well as paying users/companies).
> WTF is it about these tools that the creators think will make us tolerate the sudden switch from free to paid? I am dead tired of watching this play out over and over.
What Postman and Insomnia did is not cool. But that does not mean it’s unavoidable. Even though it complicates development, we’re local-first from the very start. Accounts and sync are optional layers on top of it.
Comment · 3 years ago
As the first paragraph in the README says, we use the GitHub repo to host releases and issues.
Comment · 3 years ago
We have a PoC where the runtime is implemented in Python and the Electron and web apps use it through https://pyodide.org/. Still exploring but looks surprisingly viable.
Comment · 3 years ago
We started httpie/desktop as a separate codebase but are working on unifying it with httpie/cli and our cloud to avoid multiple implementations by extracting a shared runtime that will be used everywhere. One of the interesting challenges here is that HTTPie Desktop is written in TypeScript while the rest is in Python.
Comment · 3 years ago
> I think the issue is the posturing as open source, having a github repo with no code just to attract devs and look open source-y
As the first paragraph in the README says, we use the GitHub repo to host releases and issues.
Having it on GitHub under the same organization as our other projects that already are open-source is convenient for both us and our users — https://github.com/httpie.
> and even sharing it on HackerNews right after the issues with closed source by Postman too. Feels like an "open source alternative", but not really, hence the sketchy accusation.
The person who shared it is not related to HTTPie.
Given the quality of the discourse here, I almost wish they did not! ;-)
Comment · 3 years ago
Yes, an Electron app is worse than a native app. An Electron app is also infinitely better then no app.
It's a trade-off.
Without Electron and the likes, a fraction of the apps that are now almost effortlessly cross-platform would exist for Linux, for example.