251–260 of 300 posts
Earlier quoted context omitted.
> Now I just have a Makefile with a bunch of curl invocations There are several FOSS command line tools that can do this easier, e.g. https://httpie.io/cli
That syntax just seems slightly more confusing than curl, not easier except for very specific simple requests.
Other than that, sure, mostly similar.
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
Earlier quoted context omitted.
Pretty obvious why if you use the software. I get the whining, but teams need ways to share their complex workflows, and teams are where the money is for all dev focused software. That's who pays for all your tools to have free versions. People who use make and curl to jury rig some unshareable solution together that no-one else in their company would even bother trying to use aren't worth any money to companies.
My experience is the opposite. Teams that are knowledgeable jury rig their own custom solutions without all the enterprise cruft. They make solutions that fix their problem and they do it faster than the teams who use bloated enterprise solutions. I am tired of seeing over engineered enterprise solutions that that are implemented and never used because they can’t be integrated into the dev workflow easily. Simple bas…
Bash and Perl scripts run, truly, everywhere - so you get real collaboration. I can share it with anyone on my team and they can use it.
Earlier quoted context omitted.
This looks awesome! I've been wondering what to do with Insomnia since its enshittification. One idea: since you are doing good-faith licenses anyway, maybe you could add in the possibility to pay for some kind of one-time license? I don't particularly need or want updates from my API tool, I just want it to work and not break. I would be fine with paying a one time commercial license that gives non expiring right to…
I think this is covered by lifetime fallback license, under pricing->FAQ - but not sure, seems so.
I stopped using Postman when it magically started connecting to a central server for… nothing useful, really. I have no idea why people would design software this way, especially a development tool that should work with any web server, under any network condition (including fully offline against localhost). Now I just have a Makefile with a bunch of curl invocations, or Python tests with requests to match against exp…
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...
Converted a bunch stuff just laying in my shell history into actual actionable files finally :D
Ah, yes, the cloud-dependent tool that forces you to pay per seat and log in for any type of collaboration is down when their cloud provider is. Anyways, the folks have spoken, no need to double down. There are more than a dozen alternatives to it, and new ones are coming up. I'm helping build a new one. - Completely offline. - Gives the ability to build reusable blocks (headers, query params, etc) - Let's you docume…
Earlier quoted context omitted.
Wrote this late at night and didn’t explain what I meant by X11 view. I was thinking back to running X sessions on remote machines, sending for example a text editor view back across the network to my desktop. VSCode remote feels to my fiftysomething brain to be logically quite like that, only you are sending the display back from the remote worker using web techniques, and rather than to a display manager, you are s…
Maybe I’m misunderstanding, but I think what you want already exists as VSCodes remote SSH tunnel port forwarding (not the one that makes it publicly accessible). Startup a dev server on the remote machine and forward the port to localhost. It should now be accessible via http://localhost:[port] on your local machine in the browser or any application, as if it’s running locally. I find it’s very useful for also for i…
Won't immediately help with giving that tool access to the file system or Git.
For a local VM, you can have file system mounts, fast enough for Git.
SSHFS could help in some genuinely distant remotes with access to the file system (though SSHFS in the context of multiple file writers is fraught with risk of file corruption; been there, bought that T-shirt).
With properly network-remote VMs, nothing helps that much with giving the tool access to performing Git operations on changes inside your remote: Git is slow over network file systems even when they are quite local.
This is the real power of the VS Code remote after all; everything happens there.