Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SSH Remoting

zed.dev

Post reply on HN
Print view View original

121–130 of 227 posts

Re: SSH Remoting

#121

Post by mbreese »

madeofpalk wrote: post #108
larodi wrote: post #81

Earlier quoted context omitted.

Indeed seems very uncommon where I am, even the IntelliJ’s are more often pirated than paid for. From my perspective it is very weird to expect to beat MS (who produces two great IDE’s, not one) on their own game with this approach to dev. I’m not saying it’s impossible to have the most important features replicated, but, c’mon, this is software, it breaks as it builds and some things are not possible Overnight even…

You don't need to beat microsoft in order to have a viable business. You just need to get enough market share.

But, you also have to be better than what’s freely available by enough to get someone to pay for it. Having a good product isn’t good enough, you have to be significantly better.

Dev tooling is a notoriously difficult space to make money. Free tools tend to win because if a tool costs money, a developer is just as likely to write their own version. (For better or worse)

Re: SSH Remoting

#122

Post by fredoliveira »

eddythompson80 wrote: post #103
szundi wrote: post #40

Earlier quoted context omitted.

What a perfect attack vector even if Zed and Vscode people are completely honest

What’s the attack vector? Someone with ssh access to your machine can run code on your machine? That’s part of ssh.

Presumably the attack vector is that someone malicious at Zed or VSCode could change the code in the server components to introduce a backdoor that could be used later.

Re: SSH Remoting

#125

Post by frankjr »

eddythompson80 wrote: post #117
frankjr wrote: post #110

Earlier quoted context omitted.

Hmm, are the docs outdated then or are they talking about something else? > The Visual Studio Code Remote Development extensions and their related components use an open planning, issue, and feature request process, but are not currently open source. https://code.visualstudio.com/docs/remote/faq#_why-arent-the...

That’s the extension which launches the server. The server itself, which is what runs on the remote machine, is part of the vscode repo itself. You can see this open source extension for an example of what the extension does as well as an explanation of what it does https://github.com/xaberus/vscode-remote-oss Mainly just sets up the UI/connect commands in vscode UI and launched REH (the vscode server) on the remote…

Thank you for pointing this out.

Re: SSH Remoting

#126

Post by shafyy »

krelian wrote: post #61
pseudony wrote: post #48

Can someone explain. What is the catch ? Zed is worked on by paid employees. So who is the product, how is the money made and is it open source and if so, how much ? (Vscode has strings attached too) Just interested since building my workflows around a company's products usually ends in tears (figuratively).

This is answered in their FAQ: https://zed.dev/faq : We envision Zed as a free-to-use editor, supplemented by subscription-based, optional network features, such as: Channels and calls Chat Channel notes We plan to offer our collaboration features to open source teams, free of charge.

For a VC-backed company, this will never ever generate enough revenue growth. So, the real answer is: "If all goes well, we will keep raising VC money and get acquired and shutdown / butchered in 5-10 years".

Like Bluesky, this monetization plan they present is just something to calm down the haters and sceptics. But if you think for two seconds, it does not make sense.

Re: SSH Remoting

#127

Post by [deleted] »

mbreese wrote: post #121
madeofpalk wrote: post #108

Earlier quoted context omitted.

You don't need to beat microsoft in order to have a viable business. You just need to get enough market share.

But, you also have to be better than what’s freely available by enough to get someone to pay for it. Having a good product isn’t good enough, you have to be significantly better. Dev tooling is a notoriously difficult space to make money. Free tools tend to win because if a tool costs money, a developer is just as likely to write their own version. (For better or worse)

[deleted]

Re: SSH Remoting

#128

Post by mbreese »

keybits wrote: post #44

Zed with SSH Remoting and Orbstack is pretty much my dream setup for programming on a Mac. I can now spin up a Linux machine in Orbstack[0] in a few seconds and then SSH into it from Zed for a fast Linux development environment with a fast macOS native editor. It feels a bit like the macOS version of WSL and VSCode. Just a whole lot nicer (subjective of course)! A couple of years ago I was inspired by what Mitchell H…

I’ve been using Colima to host docker containers and VSCode with devcontainers to do something similar. Being able to spin up a full stack environment on the fly for working is amazing. It may not be as fast as Zed, but it’s a well thought out workflow that’s very reproducible. It’s been a quick workflow to start using, but is still quite flexible.

Regardless of which stack you use, I think this is a great style of working. When you have a reproducible dev environment, everything is so much easier. (As vagrant users will probably attest to - it’s not a new method).

But having this feature of SSH remoting is also quite handy without the dev environment stack stuff. I also find it quite nice to work with a local client, but remote SSH environment when I’m doing data work (large genomic data files). In this case, instead of reproducibly, the main benefit is data locality. If my large dataset is on a different server, it’s far more convenient to write the analysis code on that remote server. This new Zed feature seems like it will also support this workflow, which is also a win in my book.

Re: SSH Remoting

#129

Post by benterix »

shafyy wrote: post #126
krelian wrote: post #61

Earlier quoted context omitted.

This is answered in their FAQ: https://zed.dev/faq : We envision Zed as a free-to-use editor, supplemented by subscription-based, optional network features, such as: Channels and calls Chat Channel notes We plan to offer our collaboration features to open source teams, free of charge.

For a VC-backed company, this will never ever generate enough revenue growth. So, the real answer is: "If all goes well, we will keep raising VC money and get acquired and shutdown / butchered in 5-10 years". Like Bluesky, this monetization plan they present is just something to calm down the haters and sceptics. But if you think for two seconds, it does not make sense.

It might happen the way you describe, or, if they get more popular, then may try to think harder and offer more paid options. Now they're in a growth stage - they need to convince the largest possible number of developers they should switch from VS Code, and that is already a difficult task.

Re: SSH Remoting

#130

Post by Protostome »

eviks wrote: post #113
Protostome wrote: post #36

with a little bit of work, vi/emacs works great as an IDE for most setups... The learning curve is steep but once you get the gist, you never go back to those bloated IDEs. (Disclaimer: I haven't tried zed, but have been working throughout my career with Eclipse, Visual C/C++/Basic (!), Atom)

> The learning curve is steep So it's not "a little bit of work"

Compared to mastering C++, vim is a piece of cake. For me it was a major productivity boost.
Post reply on HN