61–70 of 300 posts
Depending on your usage, you may not need a separate app. Jetbrains[0], Visual Studio[1] and VSCode[2] have support for http files. [0]: https://www.jetbrains.com/help/idea/http-client-in-product-c... [1]: https://learn.microsoft.com/en-us/aspnet/core/test/http-file... [2]: https://marketplace.visualstudio.com/items?itemName=humao.re...
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
Very cool. Can you provide clarity on is a commercial license is needed. The license appears to be MIT but the yaak.app website gives the impression a license is required, even stating as such in FAQ.
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
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.
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?
Lately I've just been using a Phoenix LiveBook notebook, with the Req package loaded into it. I can make requests, do arbitrary transforms on the data, and generally stay right at home in a language I like and understand
If you don't know elixir, I'm sure jupyter or some other notebook system would do just as nice of a job
Earlier quoted context omitted.
Hey, I'm the creator of Yaak! Let me know how it could be even better :)
Flatpak and snap please
Earlier quoted context omitted.
Curious to know more about the commercial licensing scheme for Yaak: if i’ve read correctly, purchasing a pro license if based on « good faith » as the features are exactly the same as the MIT licensed Hobby version? Sincere question, been studying lots of OSS commercial licensing and always wonder what works in which context
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!
It makes good sense because companies actually have an absurd amount of liability to you if they violate your agreement.
https://github.com/jamierpond/yapi
Run this:
yapi -c ./users.yapi.yaml
# users.yapi.yaml
# yaml-language-server: $schema=https://pond.audio/yapi/schema
url: http://localhost:3000
method: GET
path: /api/users
query:
select[name]: true
select[tag]: true
limit: 10
Earlier quoted context omitted.
Curious to know more about the commercial licensing scheme for Yaak: if i’ve read correctly, purchasing a pro license if based on « good faith » as the features are exactly the same as the MIT licensed Hobby version? Sincere question, been studying lots of OSS commercial licensing and always wonder what works in which context
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!
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