640k … there is something poetic about that number.
replyI figure that's how much RAM I can expend for Microsoft products.
replyCan you explain how this works? Doesn’t this also stop you from connecting to it over ssh via vs code?
replyYes that's the point. If vscode didn't insist on installing potentially gigabytes of blobs then this wouldn't be necessary.
reply(I'm a vimmer anyway... And emacs is too bloated to fit too, conveniently.)
> And emacs is too bloated to fit too, conveniently.
replyIf you connect via ssh, you could use Tramp. It does not install emacs on the target, but instead use a somewhat permanent connection as a tunnel for most emacs commands (transparently). Works too with docker, podman, distrobox, etc,...
yep, it's a shame vscode doesn't do something similar and instead copies a huge runtime (evidently, multiple times?!?) onto unsuspecting hosts.
replySounds like a feature.
reply