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?
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.
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?
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.
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?