Live data from Hacker News

SSH Remoting

zed.dev

191–200 of 227 posts

Re: SSH Remoting

#191
post #147
post #142

Earlier quoted context omitted.

I know, this is the standard VC playbook: First growth at all costs to get everyone into the ecosystem, then pull up the net and monetize. The latter phase is usually when all the subscriptions, value-add nag screens, data sharing agreements and other enshittification goodies pop up. And how would it work otherwise? You can't perpetually offer a product for free (in all senses of the word) AND satisfy exponential ROI…

The other option I see is being owned by a behemoth like Microsoft, in VSCode case, who can pay millions per month in engineering salaries and PaaS, while keeping it free. They are so big they can monetize it using Copilot or not even monetize it properly, just to get good faith from Developers, Developers, Developers. I like it.

No, the other option is something like Sublime Text that has a small team working on it and is paid for by a very fair one-off payment by the customer.

Re: SSH Remoting

#192
post #126

Earlier quoted context omitted.

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.

And while doing this, they fuck the whole market.

Re: SSH Remoting

#193
post #126

Earlier quoted context omitted.

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.

Well as an end user this is pretty much OK right, so long as you are aware of the deal? VC funded companies have subsidized and then abandoned a lot of useful OSS code over the years. Whenever you encounter a VC backed open source project you know the rug pull will come eventually. It doesn't make the code they have written any less useful. If the tool is good enough then it will be forked and live on.

No, it's not ok. It fucks the whole market by subsidizing the growth with VC money. Either a big company will buy them, consolidating their power, or they will IPO and the VCs will cash out and let the public bear the cost. It fucks the customers who are not as well-informed about this as you are. In summary, it fucking sucks.

Re: SSH Remoting

#194
post #173
post #154

Earlier quoted context omitted.

Thank you both for sharing the experience. I'm tempted to go lightweight laptop + beef server. Do you get used to the the input delay? I guess coding is not a FPS game so it's fine. Just a flow of words being edited.

There's no input delay in VSCode (editor, ui) because the UI is local. Delay in saving/reading/sesrching in files is not noticable for me. (edit to explain: VSCode is still running locally, but it also installs the server-side (headless) component on the remote machine. That way editing files is local/fast, but stuff like running the code, search/replace/etc also works fadt because it's handled by the serverside). Te…

Thank you. Sounds like best of both worlds.

Re: SSH Remoting

#195
post #166
post #154

Earlier quoted context omitted.

Thank you both for sharing the experience. I'm tempted to go lightweight laptop + beef server. Do you get used to the the input delay? I guess coding is not a FPS game so it's fine. Just a flow of words being edited.

Do you get used to the input delay? The input delays are very dependent on where the server is and what it is doing. If the server is idle and close by (ping wise) delay is virtually indistinguishable from local VSCode. If I'm connecting to the server via a VPN in a different country while stressing all the cores with some background compiling or number crunching work, input delay gets quite noticeable.

I guess editing files in the same continent must feel good enough.

Thank you! I should try a project in this way.

Perhaps rent some hetzner VPS.

Re: SSH Remoting

#196
post #191
post #147

Earlier quoted context omitted.

The other option I see is being owned by a behemoth like Microsoft, in VSCode case, who can pay millions per month in engineering salaries and PaaS, while keeping it free. They are so big they can monetize it using Copilot or not even monetize it properly, just to get good faith from Developers, Developers, Developers. I like it.

No, the other option is something like Sublime Text that has a small team working on it and is paid for by a very fair one-off payment by the customer.

Sounds like a third option. I have a Sublime license and I like it.

But no need to discard VSCode.

They are different tools anyway.

Re: SSH Remoting

#197

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).

Happy path is Open-Core where all enterprisesque features and plugins are part of a commercial pro model. Unhappy path involves switching licenses sometime later or project simply dying because of ROI.

Yep. Maybe a good copilot written in Rust and tightly integrated into Zed. Offer a subscription model. I'd pay for that.

Re: SSH Remoting

#198

How are people so happy with Zed? I've tried it, it's fast sure, but it lacks some very essential features like inline error highlighting and button for running code like how Intellij has it, there is no extensions that cover this either. At the moment, the Zed IDE is more like an lightweight ai-assisted text editor for me.

I think that is precisely why people, and myself, ate happy with Zed. I don't, personally, care for those kinds of features. I want something that is snappy, and bloat free. I beloved extensions are planned so that will come in time. I'm terms of inline error highlighting, it absolutely has that. is your LSP just not working correctly?

> is your LSP just not working correctly?

I don't know, I can't tell, but I would guess it does not. I just got the one and only Java extension there is (the other has has something to do with Eclipse). Yet, no error highlighting.

Re: SSH Remoting

#199
post #6

Earlier quoted context omitted.

for a start, zed doesn't work on Windows. I'm not exactly a fan of MSFT but at work, I must use Windows...

It does work. Automated builds are here: https://github.com/deevus/zed-windows-builds

Builds are there, but they don't work. At least on my laptop.

Re: SSH Remoting

#200

Those who do not understand Emacs are doomed to repeat it. Poorly, in worse languages. —C.S. Santayana Emacs TRAMP mode has been doing this for 26 years, since November 1998. Fashions come, and fashions go, and Emacs remains. Anyone remember Atom? Anyone remember TextMate? Just use vi or Emacs.

What's the point of this comment? Zed didn't exist in 1998, so I think it's forgivable that Zed didn't support remote editing in 1998. It's pretty funny you'd comment this at the same time there's a thread on the front page with people complaining about emacs bugs/performance issues: https://news.ycombinator.com/item?id=41954030 Is that really the best we can do? Should we have frozen tech in 1998 with our 28.8kbps m…

> What's the point of this comment?

To encourage people to use Emacs (or vi).

> Should we have frozen tech in 1998 with our 28.8kbps modems

We had Ethernet and high-speed networks in 1998. The rest of the world has just caught up, that’s all.

> Why did you switch to this emacs fad when you could have stuck with ed(1)?

Emacs is an improvement over and above vi & ed. No other current editor is an improvement over and above Emacs. The only improvement Emacs is lacking is Common Lisp extensibility.

> I think it's great that people are advancing the state of the art.

But they’re not — they’re reimplementing the decades-old art. Why waste time using worse technologies to extend worse editors when one can invest one’s time using better technology to extend a better editor?

Post reply on HN