Live data from Hacker News

Zed for Windows: What's Taking So Long?

zed.dev

21–30 of 83 posts

Re: Zed for Windows: What's Taking So Long?

#21
post #4

This is why you don’t make your own cross platform toolkit.

while I would agree in general, there could theoretically be SOME applications where the range of UI controls (and systems) is small enough where it could pay off. But things tend to expand in surface area... So with that, this presents a HUGE opportunity for someone to build something akin to Zed, but not with the baggage that their technical strategy brings.

> So with that, this presents a HUGE opportunity for someone to build something akin to Zed, but not with the baggage that their technical strategy brings.

Not sure it’s so clean-cut. More than avoiding baggage, you’re just shifting it elsewhere. The question is if you want to own (and can handle) the baggage and benefit from the control that brings.

Re: Zed for Windows: What's Taking So Long?

#22
post #20
post #4

This is why you don’t make your own cross platform toolkit.

You'd rather see another crappy, slow editor packaging an entire browser? Because that seems like what people are using for "cross platform toolkits" these days. I'm glad Zed is being ambitious, it's truly a joy to use because it feels native. And to be honest, it's Windows, who cares. If you are a developer you should have switched to Linux years ago anyway.

No, there are good reasons developers are on Windows. Industrial and embedded systems are very often Windows-based, for better or worse. Heaps of games are developed on Windows. Windows-based software itself is developed on Windows.

Re: Zed for Windows: What's Taking So Long?

#23
post #4

This is why you don’t make your own cross platform toolkit.

The FOSS community has become full of ideological landmines, with projects now including clauses in their requirements, often vague and ill defined, about how those who build upon their projects must act and believe. As a result, some are now finding it less risky to roll their own base dependencies instead of using someone else's project that could at any time become problematic for non-technical reasons.

While I doubt this had anything to do with the decision by the Zed team to make their own toolkit, it is something becoming more common. Hopefully it doesn't start happening in the encryption space.

Re: Zed for Windows: What's Taking So Long?

#24
post #4

This is why you don’t make your own cross platform toolkit.

Or why you don't insist in using Khronos stuff on Windows, when most OEMs only care about the native API, DirectX.

Lets recap that this lesson has been learned by Godot developers, regarding their backends as well.

The ICD mechanism is a kind of escape hatch leftover due to backwards compatibility, and even user mode drivers build on top of DirectX runtime infrastructure.

Re: Zed for Windows: What's Taking So Long?

#26
post #20
post #4

This is why you don’t make your own cross platform toolkit.

You'd rather see another crappy, slow editor packaging an entire browser? Because that seems like what people are using for "cross platform toolkits" these days. I'm glad Zed is being ambitious, it's truly a joy to use because it feels native. And to be honest, it's Windows, who cares. If you are a developer you should have switched to Linux years ago anyway.

I use computers since 1986, UNIX variants since 1992, and yet Windows is where I spend most of my time.

I find hilarious this FOSS concept that developers only use Linux, I wonder who writes software for all other operating systems in the world.

Re: Zed for Windows: What's Taking So Long?

#28
post #20

Earlier quoted context omitted.

You'd rather see another crappy, slow editor packaging an entire browser? Because that seems like what people are using for "cross platform toolkits" these days. I'm glad Zed is being ambitious, it's truly a joy to use because it feels native. And to be honest, it's Windows, who cares. If you are a developer you should have switched to Linux years ago anyway.

No, there are good reasons developers are on Windows. Industrial and embedded systems are very often Windows-based, for better or worse. Heaps of games are developed on Windows. Windows-based software itself is developed on Windows.

Being ~2 weeks into migrating from Windows to Linux for my dev machine, there are a lot of good reasons why people use Windows, and I keep learning more each and every day!

From a lock screen that appears ~3 seconds after my desktop does (during which time I can interact with my desktop...) to getting Nvidia GPU passthrough working in Docker being harder running on Linux natively than what it was making it work on WLS (...) to absurd amount of time it takes my machine to come out of sleep.

Oh also the popping and clicking over my BT headset every time someone speaks in a meeting. That was wonderful.

Despite using an older model MB, I needed to install some kernel extensions to get system temperatures working.

Also if I want to develop desktop software, I'm going to be writing against Windows anyway because at least that is somewhat documented, vs the ever changing landscape of Linux desktop software development. (Windows used to be the OS for desktop software, but Microsoft shot themselves in that foot, then removed the entire leg, long ago, by constantly changing and deprecating frameworks, ugh, 20+ years of API stability down the drain...)

Post reply on HN