Isn’t insomnia open source?
Hoppscotch: Open source alternative to Postman / Insomnia
51–60 of 129 posts
Re: Hoppscotch: Open source alternative to Postman / Insomnia
#52Without sounding like every other developer who hates on electron, I would really appreciate an http client with a Gui that was lighter, like iced or slint. I appreciate the versatility of electron and it giving us beautiful and usable apps but I have 16 GB of ram, I can't upgrade it and I genuinely have multi second hangs after I have 3 instances of VSCode, Firefox and Chrome open along with Bruno.
Sounds like you're looking for https://yaak.app/ .
that's close but it uses Tauri, which maybe lighter than electron but we're still running an instance of a web browser/web view
Re: Hoppscotch: Open source alternative to Postman / Insomnia
#53Earlier quoted context omitted.
Yes, But. It doesn't seem like the worst - yet - but Bruno also ramped up their monetization. So far it seems survivable. But given how things have gone before, it's unclear how viable Bruno will really remain. https://news.ycombinator.com/item?id=42170934
HTTPie is imo the best one now.
Been on the old CLI version of HTTPie for years now. Or are you talking about the GUI version?
Re: Hoppscotch: Open source alternative to Postman / Insomnia
#54Earlier quoted context omitted.
Sounds like you're looking for https://yaak.app/ .
that's close but it uses Tauri, which maybe lighter than electron but we're still running an instance of a web browser/web view
There's a TUI application out there that might be up your alley, but I can't remember what it's called...
EDIT: There's one called Posting which seems to be the most popular: https://github.com/darrenburns/posting
Re: Hoppscotch: Open source alternative to Postman / Insomnia
#55Wait, wasn't insomnia supposed to be an open source alternative to postman?
Yeah, but they went the cloud-first enshittification route like a year and a half ago.
https://github.com/Kong/insomnia/issues/6577
I still use Insomnium, a (dead) fork of Insomnia that removed all the telemetry on a version of Insomnia just before this nonsense occurred.
Re: Hoppscotch: Open source alternative to Postman / Insomnia
#56Terminal based: https://posting.sh/
That’s incredible, amazes me that you can get a GUI like this in terminal. Next someone will put doom in the terminal
Re: Hoppscotch: Open source alternative to Postman / Insomnia
#57Earlier quoted context omitted.
that's close but it uses Tauri, which maybe lighter than electron but we're still running an instance of a web browser/web view
There's a TUI application out there that might be up your alley, but I can't remember what it's called... EDIT: There's one called Posting which seems to be the most popular: https://github.com/darrenburns/posting
https://github.com/LucasPickering/slumber is also a good TUI alternative
Re: Hoppscotch: Open source alternative to Postman / Insomnia
#58btw, JetBrains IDEs have built-in HTTP-client. Not so GUI rich, but very convenient for development and no need for a separate if you're already using the IDE https://www.jetbrains.com/help/idea/http-client-in-product-c...
A big plus imo is that you can check in and version control the files alongside your application. Very convenient when working on micro services in a team.
Re: Hoppscotch: Open source alternative to Postman / Insomnia
#59Am I the only one who use CURL over such tools? I don't want a 300MB electron client doing GET/POST work, especially those with hidden telemetry on.
I always use curl, jq, etc. It's so simple and straightforward. But I would be lying if I claimed it to be easy to convince my teammates to use the same toolset I use.
Some ppl “just need to press a button” so i’ve been told. I like httpie, but curl and wget could hardly be more mature tools.
Re: Hoppscotch: Open source alternative to Postman / Insomnia
#60I just wrote my own [1] and I will be Sure that this one will never be monetised [1] https://github.com/warmuuh/milkman
Nice and kudos for your efforts.
For convincing people it never being monetized this is not enough.
You'll need
1. A copyleft license (to prevent the Redis case)
2. No CLA (to prevent unilateral relicensing)
3. A large enough and diverse enough set of contributors that makes relicensing unpractical enough for user to believe it will never happen