[jkbr]

> closed source (despite their website proudly claiming "Open source")

HTTPie CLI has been open-source for a decade. HTTPie Desktop has yet to be open-sourced. We first want to get the product, architecture, and codebase somewhat stable. As the README says, we use the GitHub repo to host releases and issues.

[salusinarduis]

You gave this exact same answer to me in your Discord a year ago. If nothing sketchy is going on why not just open source the thing?

At a minimum you should remove the banner at the bottom of the page claiming it's open source.

[jkbr]

> You gave this exact same answer to me in your Discord a year ago. If nothing sketchy is going on why not just open source the thing?

We appreciate your interest, but we never gave an ETA. I do regret having made the intention public, though.

> At a minimum you should remove the banner at the bottom of the page claiming it's open source.

That’s a good point. As I wrote in another comment below: I’ve now updated the website template not to show the image with the slogan on this page. Thanks for the feedback.

[salusinarduis]

Good on you for altering the page. I very much hope to see the desktop client become open source soon, as I would very much like to use it. Best of luck with the project.

[da39a3ee]

I don't understand; why do you think it is "sketchy" to try to make a living out of software?

(For reference, I work as a software engineer and am also the author of a popular open source project which I give away for free and have put thousands of hours into.)

[jeanlucas]

>I don't understand; why do you think it is "sketchy" to try to make a living out of software?

I don't think the original comment meant that it is sketchy to make a living out of software. 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 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.

But this is just how I read it.

[jkbr]

> 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! ;-)

[da39a3ee]

> having a github repo with no code just to attract devs and look open source-y

It's an HTTP client. The client codebase is here:

https://github.com/httpie/cli

Why everyone is getting their knickers in a massive twist because they have an Electron wrapper that they haven't open sourced is mystifying.

I haven't studied the codebase but I highly doubt they are going to have a separate client implementation for the Electron product vs the CLI! They're just trying to create a nice Electron client, in addition to their well-known CLI, and start a business around it aren't they?

[jkbr]

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.

[da39a3ee]

Thanks, of course, that makes sense. How are you planning on doing it -- use a language like Rust that can easily be called from both and packaged? Or rewrite the CLI in Typescript?