> There have been drastic price increases in various areas in the IT branch recently. That is why, unfortunately, we must also increase the prices of our products.
> The costs to operate our infrastructure and to buy new hardware have both increased dramatically. Therefore, our price changes will affect both existing products and new orders and will take effect starting on 1 April 2026.
> We have genuinely tried hard to optimize our costs and to prevent increasing our prices for as long as possible. But we can no longer compensate for the strain that it has placed on our operations. We want to continue to deliver quality products that meet both our standards and your expectations, so we must take this step.
Seems poor translation. The German version only speaks about rising costs in various areas, no mention of any IT branch. They probably meant the whole IT market in general, not specifically their own company or some branch of it.
It's a German hosting company making a translation error from the German "IT-Branche". The wording doesn't appear in the German version, but very well could have at some point in the process.
Knock-down effects from the RAM shortage, starting to see CPUs shortage (lead times for Intel at 6 months for server-class CPUs, AMD also notified enterprise customers about a crunch), GPUs shortage, storage prices are increasing a lot as well.
Everything is much more expensive on the hardware-side at this moment, I think we will see these price increases across any provider that requires hardware, I'm just waiting until Backblaze notifies they will also need to increase pricing due to this.
AI is sucking money from everything, not only financial markets, it includes all of us consumers of anything that requires hardware to run on.
Hopefully this craze dies down in the next 1-2 years because it will be untenable to be paying 2-3x prices for the same technology we had for quite cheap just a year ago...
Coolify has been refreshingly nice to use for me too. My few -
1. Bugsink to replace sentry
2. Trying to figure an otel friendly observability stack with multi tenancy, but clickstack and signoz both feel painful to setup and manage as coolify projects.
Wow, I've been looking for a postman/Bruno/foo replacement that I could use inside a remote ssh server or remote dev containers in vs code. This might be it!
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.
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.
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 sending it back into the shell of an editor, so it appears to be largely indistinguishable from a session running on your local machine.
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 interacting with DBs/Redis. Just forward the port your DB communicates on and use whatever client on your local machine to interact with it.
As far as I know this works with any service that communicates via TCP
Yeah, it would help with using the tool to access a private-to-the-remote API.
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.
The REST Book extension was made by a VS Code dev and does a decent enough chunk of what is needed, at least for simple use cases.
Handy Dandy Notebook as well, but that requires some reformulation to get everything in terms of standard curl/node/python/etc commands. (whether that’s better or worse than a custom http dsl is a matter of some debate)
Might be a useful travel hack for those who struggle to book a schengen visa appointment (which is needed by several nationalities who want to travel to Europe).
This site shows you visa appointment availability for various destinations across US, UK and more cities in a simple table - refreshed periodically. So you don't have to login to keep checking each one. Hope it saves you some time and money.
Which real world do you live in? Real businesses spend a good percentage of their efforts in cutting costs. And if they have a large consumer base they push newsletters too, then yes, as an agency, I can tell you that a lot of clients will make the switch.
There a bunch of open source self-hosted newsletter systems doing well (oh, and they're mostly subpar). I like the direction in which sendy is heading and with the amazon ses edge to it, its a great great idea. If sendy would throw in a few more features like multi-user login and access control, I'll make the switch and will convince a few of my clients too.
