Live data from Hacker News

Zed for Windows: What's Taking So Long?

zed.dev

81–83 of 83 posts

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

#81

Earlier quoted context omitted.

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

Doesn't the blog post specifically say they are shipping their own glyph rasterizer?

No?

> To work around this limitation, we decided to stop using Direct2D and switch to rasterizing glyphs using DirectWrite instead.

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

#82

Earlier quoted context omitted.

> Industrial and embedded systems are very often Windows-based I find Windows to be the outlier against a sea of embedded Linux devices. > Heaps of games are developed on Windows Inertia. > Windows-based software itself is developed on Windows. Plenty of Windows-based software is developed on Linux with Wine.

> I find Windows to be the outlier against a sea of embedded Linux devices. I think you're thinking of consumer devices, not industrial. > Inertia. I think that's a tough case to make. Windows offers legitimate technical advantages for gaming and game development. Integration with large vendors' tooling like NVIDIA and AMD is pretty huge. There are real workflow benefits. > Windows-based software itself is developed…

> Integration with large vendors' tooling like NVIDIA and AMD is pretty huge. There are real workflow benefits.

This seems very much like something that happened because it had such a large market share, not because of any inherent technical advantages

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

#83

Earlier quoted context omitted.

Try compiling anything in C

Are you saying that it is somehow complicated to press Build in the VS window?

Visual Studio uses MSVC along with its own project format. Most C projects depend on specific tool chains or compilers.
Post reply on HN