This is exactly why I made Yaak [1]. It's fully offline, no telemetry, open source, and can even sync with Git. https://yaak.app
You're already going down the path Postman did. No way I'm using that.
Postman which I thought worked locally on my computer, is down
71–80 of 300 posts
Re: Postman which I thought worked locally on my computer, is down
#72Earlier quoted context omitted.
This is a conscious bet I'm making. Yes, it's a good-faith license. The license doesn't even apply to the OSS version (only prebuilt binaries). The bet is that super fans will pay for it in the early days and, as it gets adopted by larger companies, they will pay in order to comply with the legalities of commercial use. So far, it's working! The largest company so far is 34 seats, with a couple more in the pipe!
Excellent work! Looking forward your post about some milestone ARR boundary, the gory details of how you got there.
My runway reaches infinity around $10k MRR so I'll likely do a post around then. Currently 11% of the way there!
Re: Postman which I thought worked locally on my computer, is down
#73I think for the most part everyone has accepted that Postman grew into a monster that bloated with features and presumably that comes with online dependence.
$dayjob sent an email to everyone with postman installed and asked us to uninstall when postman switched to online. $dayjob IT still maintains a wiki page and includes it on the banned software list. Used to be ubiquitous over there.
Re: Postman which I thought worked locally on my computer, is down
#74This is exactly why I made Yaak [1]. It's fully offline, no telemetry, open source, and can even sync with Git. https://yaak.app
You're already going down the path Postman did. No way I'm using that.
How so? It's completely open source and doesn't rely on cloud accounts or servers. It's also just me. Postman has 1000 employees and $200M+ in funding
Re: Postman which I thought worked locally on my computer, is down
#75Re: Postman which I thought worked locally on my computer, is down
#76Re: Postman which I thought worked locally on my computer, is down
#77This is one of many reasons why I prefer curl[0] and a bit of shell scripting. With this approach there is no dependency on a vendor's servers.
Re: Postman which I thought worked locally on my computer, is down
#78Earlier quoted context omitted.
This is a conscious bet I'm making. Yes, it's a good-faith license. The license doesn't even apply to the OSS version (only prebuilt binaries). The bet is that super fans will pay for it in the early days and, as it gets adopted by larger companies, they will pay in order to comply with the legalities of commercial use. So far, it's working! The largest company so far is 34 seats, with a couple more in the pipe!
Having often thought this is how I would attempt to monetize if I built a developer tool, I'm glad to hear that it's working. It makes good sense because companies actually have an absurd amount of liability to you if they violate your agreement.
Without telemetry, how will you know that anyone at all is using your software let alone only within the agreement of any licensing terms?
Re: Postman which I thought worked locally on my computer, is down
#79Earlier quoted context omitted.
I was looking at Yaak, and wondering if you've plans to bring it inside VS Code some day? how would someone use this in a project that operates within VS Code Remote where the source sits on a remote server and isn't physically on the file system.
No plans for VSCode integration, no. It's only great because it's designed for a very specific use case and environment. I'm not quite sure why Yaak wouldn't work in this case. It it because your running server wouldn't be accessible to Yaak, running on your system?
In case you aren’t familiar (and with apologies for my verbosity if you are): VSCode Remote can be best understood as a sort of hybrid of a local text editor and a remote web-based or X11 view of an editor for a remote session.
When you use a remote, the code is on the remote and all your editing functions (search, version control, terminal, extensions) happen in the remote via a worker process.
So in a remote session, everything is “local” to the remote. You may have no file “mount” of the thing at all on your host desktop machine. If you do a git commit, it’s running inside/on the remote. If you do a file search the files are searched on the remote, rather than downloading them over some network filesystem and searching locally.
The GP’s point is, I think: if you implemented Yaak as a VSCode extension, it could be made to function either in a local session or inside a remote (on a server accessed via SSH, a docker container, on the linux side of WSL etc.) and therefore have fast rather than slow access to the code, git repo etc.
I do essentially all my dev work (apart from compiling the odd mac app) inside remotes of various kinds to create reproducible environments, avoid cluttering the host, sandbox the tools, give me freedom to work from more than one machine etc., and I run into this sort of thing quite a bit.
There are at least two clients like this for VSCode —- Thunder Client and EchoAPI, and I believe both function in a remote session.
P.S. I loved Insomnia before the bad happened; it really helped with learning APIs. Thanks.