Earlier quoted context omitted.
Thanks. That explains why OSs use the GPU for rendering windows and effects, but it's still not clear to me why a code editor would do the same. The features you list (transparency, glass effects, shadowing, window management, etc.) seem to be outside the purview of a text editor. If you're saying that Zed is built on something like Skia, then it would already be cross-platform and not have to worry about Vulkan vs.…
> but it's still not clear to me why a code editor would do the same. Happy to elaborate further. Old school text rendering began with a table of character codes to actual, fixed-size bitmaps (this was a font), and rendering was straightforward: divide the framebuffer resolution by the bitmap resolution, clip/wrap the remaining, just place the bitmaps into the resultant grid, and pipe the framebuffer to the display.…
Zed for Windows: What's Taking So Long?
71–80 of 83 posts
Re: Zed for Windows: What's Taking So Long?
#72Earlier quoted context omitted.
> Plenty of Windows-based software is developed on Linux with Wine The overwhelming majority of software written against MinGW (or worse, Cygwin) are bad/lazy ports of Linux-first software. Case in point: Git and Perl, both of which drag along an entire coreutils ecosystem ( each , so you have two copies of `ls`) along with the main binaries. First-class Windows programs that are used every day like Office, Chromium…
Ironically it was the act of doing that: spinning up a VM to test a release on Windows, which really turned me against it forever. During installation, I counted 4 un-skippable EULAS about "sharing data" and then asked me what my ad preferences were. To add insult to injury once I finally did get it installed, the start menu was full of Xbox apps and the taskbar had some news headline about the Kardashians on it. I d…
I install the Enterprise/Education versions.
Re: Zed for Windows: What's Taking So Long?
#73Earlier 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.
>If you are a developer you should have switched to Linux years ago anyway. These days, WSL2 effectively eliminates a need for that for most developers.
Otherwise no.
Re: Zed for Windows: What's Taking So Long?
#74Earlier quoted context omitted.
I’m almost nerd-sniped enough to try and see exactly where it breaks down. What’s a native render function? Do you mean just using a graphics API as opposed to an off-the-shelf UI library?
> What’s a native render function? As in using DirectWrite or GDI on Windows; or Core Text on macOS. As opposed to shipping your own glyph rasterizer.
Re: Zed for Windows: What's Taking So Long?
#75Earlier quoted context omitted.
Ironically it was the act of doing that: spinning up a VM to test a release on Windows, which really turned me against it forever. During installation, I counted 4 un-skippable EULAS about "sharing data" and then asked me what my ad preferences were. To add insult to injury once I finally did get it installed, the start menu was full of Xbox apps and the taskbar had some news headline about the Kardashians on it. I d…
> I don't know how people put up with it. It feels disrespectful. I install the Enterprise/Education versions.
Re: Zed for Windows: What's Taking So Long?
#76I’m sure this is a dumb question, but why does a code editor need to render on the GPU like a video game? Is it just for niceties like smooth scrolling?
It doesnt really do a tech breakdown of why it’d be impossible CPU side, but mentions a couple of things about their design process for it.
Re: Zed for Windows: What's Taking So Long?
#77Re: Zed for Windows: What's Taking So Long?
#78This 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.
Re: Zed for Windows: What's Taking So Long?
#79Re: Zed for Windows: What's Taking So Long?
#80Earlier quoted context omitted.
As mentioned here... Probably Skia, which would've saved them the effort of writing any GPU backend, let alone three.
Isn't Skia controlled by Google?