Earlier quoted context omitted.
Or… use one of the existing cross platform toolkits that have existed for decades. Text Editors, traditionally, did not require shaders to run or be performant, and not require entire systems worth of RAM.
Cross platform toolkits, more than other software components incur massive tradeoffs. They’ve written one themselves, tailored to their needs and open sourced it along the way. I guess I don’t see the problem here. If one that’s existed for decades fits your needs better then use that.
Linux When?
91–100 of 169 posts
Re: Linux When?
#92From what I understand Zed is a text editor that is built like a game engine, which I understand is why the marketing copy uses the term "multiplayer" rather than "multiuser". I didn't find other mention of its multiplayer capabilities, which is too bad. Has anyone used it for that purpose, I'm curious as to what the experience was like.
it was used back with a popular website which opened a text document and anyone viewing could type, but I can't remember the name. That became a thing in Google Docs, Microsoft Office, Floobits, and lots of self-hosted and cloned sites.
Re: Linux When?
#93> On macOS, for example, Zed makes direct use of Metal. We have our own shaders, our own renderer, and we put a lot of effort into understanding macOS APIs to get to 120FPS. So they are taking the exact opposite approach of Electron (VS Code). In my mind, if you're someone who types in HN comments in a rage because your text editor (VS Code) eats up 200+ MB ram, you don't get to cry about Zed not being supported on L…
This is my problem with Electron applications. I'd be fine with them gobbling up a few GB if they were stable.
Re: Linux When?
#94What is the accessibility story with Zed? I have a vague memory that atom had none of it.
Right now: mixed. We provide both user defined themes and theme overrides that let people color-correct things as they need, we have a strong cultural focus on keyboard accessibility for all UI elements, you can increase or decrease the font size in the editor and the UI, and we have strong support for IME on macOS and will be extending that to Windows and Linux. However, our accessibility to screen readers is non-ex…
A note, the tab key is not all that important. f6 for jumping the different parts of the screen and the arrow keys for neighbouring elements could be a good substitute for most cases. Add a few key bindings and tabless is not an issue any more.
Re: Linux When?
#95If Apple had just adopted the Vulkan standard instead of going off with their own proprietary graphics API this would have been a non-issue. Smacks of Canonical and their repeatedly doing one thing while ignoring the rest of the community standardizing on something else.
Metal predates Vulkan. But also I'm pretty sure Apple doesn't care if an app is portable.
I'm kind of tired of this contention cropping up again and again. Technically true but insufficient & obfuscating more than revealing.
Re: Linux When?
#96Earlier quoted context omitted.
Right now: mixed. We provide both user defined themes and theme overrides that let people color-correct things as they need, we have a strong cultural focus on keyboard accessibility for all UI elements, you can increase or decrease the font size in the editor and the UI, and we have strong support for IME on macOS and will be extending that to Windows and Linux. However, our accessibility to screen readers is non-ex…
Thanks, will keep an eye on the developments there. A note, the tab key is not all that important. f6 for jumping the different parts of the screen and the arrow keys for neighbouring elements could be a good substitute for most cases. Add a few key bindings and tabless is not an issue any more.
Re: Linux When?
#97Earlier quoted context omitted.
Or… use one of the existing cross platform toolkits that have existed for decades. Text Editors, traditionally, did not require shaders to run or be performant, and not require entire systems worth of RAM.
Out of curiosity, how many of them run at 120 FPS? (honest question - I've never looked into it myself)
It also seems like you can configure VSCode to go faster: https://stackoverflow.com/questions/52230196/vs-code-is-visi...
But honestly, 'responsiveness' should come from not blocking the main/UI threads, and rendering in the right order of importance.
Re: Linux When?
#98Will it run on iGPU?
Re: Linux When?
#99I found a few issues, but overall it already works quite well and is very fast. It might even get me to give up on Neovim!
Re: Linux When?
#100> On macOS, for example, Zed makes direct use of Metal. We have our own shaders, our own renderer, and we put a lot of effort into understanding macOS APIs to get to 120FPS. So they are taking the exact opposite approach of Electron (VS Code). In my mind, if you're someone who types in HN comments in a rage because your text editor (VS Code) eats up 200+ MB ram, you don't get to cry about Zed not being supported on L…
> In my mind, if you're someone who types in HN comments in a rage because your text editor (VS Code) eats up 200+ MB ram, you don't get to cry about Zed not being supported on Linux from day one, because you can't have your cake and eat it too - if you want it on your platform, you gotta wait for the shaders to be written. This is certainly one takeaway. On the other hand, this very blog post points out that a commu…
... and that even if it means signing away their rights in a CLA to a for profit company. This is on another level than contributing to the Linux kernel that is GPL2 plus practically not relicensable because of the multitude of copyright holders.