https://shellnox.dev - instant linux vms via an ssh api. Svales to zero, pay only for what you use

That domain doesn't exist.

now someone do a "VIM appearances in pop culture" :)

See https://www.reddit.com/r/neovim/comments/1u0vg28/vim_appeara...

This is from the person who wrote the original article on Emacs.

Technically, this is true

I have it enabled for an ssh interface for managing linux vms: https://shellbox.dev

Even supports post quantum encryption :)

what's this glorious "do whatever you want" era???

The memory footprint is great, it allows finally running these coding agents in extra small instances -- say x1 on shellbox.dev

Hmm, if they're this small something like smolmachines (like shellbox, but free and local) might be a great fit.

Instant linux boxes via ssh that suspend on disconnect. Checkout https://shellbox.dev

The idea is to have "real" linux, exposing ipv6, supporting nested virtualization, docker, etc.

Cool, thanks for sharing. How would you compare Shellbox with exe.dev?

[1] https://exe.dev [2] https://blog.exe.dev/series-a

In exe.dev you have a subscription and you get some constant compute, paid whether used or not. that compute is shared between the vms. In shellbox every box has its own dedicated compute and if you don't use any, you don't pay.

Shellbox also gives an ipv6, an email endpoint, wakeup on the web endpoint, it supports nested virtualization, docker, etc. And... it is much cheaper even if you use it 24/7. Ahh and also you can send ssh exec commands, ssh forwarding, and more. It is "real" linux, like you get on classical vps providers

Cool, I really like it!

Sadly this is what sells. Standing out in this regard checkout https://shellbox.dev maybe swinging too far though?

Anchor based editing requires injecting new anchors to the context, and dirac does so via a diff. So how is this more efficient (token-wise) than search and replace?? Even at a single token per hash. Also, code is read more than written so these just add up. I experimented once with stable anchors, albeit longer than a single token, and found it a downgrade.

My conclusion is that the efficiency dirac sees comes mainly from showing file skeleton by default

I'm not sure one way or another but I've been using a related tool called Tilth by another poster here. It doesn't do anchor-based editing, but it does do syntax-aware search and will e.g. report the line range for function definitions, provide file outlines with line numbers on a file name match, etc.

https://github.com/jahala/tilth

This seems really good...going to test it :)

ohh this is really nice :) testing it

I have six patches that I will at some point upstream, the main bug/surprise is the .gitignore behavior is not what's documented, but even without it seems to work quite well.

> My conclusion is that the efficiency dirac sees comes mainly from showing file skeleton by default

how hard do you think it would be to bring this optimization to oh-my-pi and opencode? I am testing dirac and it's very cool but the tooling isn't there yet comparing to oh-my-pi in terms of UX.

Would love some more feedback on this. Where do you think are major gaps?

Thinking back, I might have jumped the gun here. I can't objectively evaluate UX without spending more time with the tool. I'll try to daily drive it a bit before I can form an opinion.