11–20 of 169 posts
Earlier quoted context omitted.
It's a blog post directly on their website. Is it really unreasonable to need to click to the home page for more context?
People on the internet expect everything to be spoonfed to them.
[flagged]
Some troubleshooting tips: - Move your mouse cursor to the "Zed Industries" icon in the upper-left-hand-corner, then click. - This "hypertext link" will instruct your browser to load the site's root "index.html", sometimes known as a "landing page". - The "landing page" is a great place to start if you're unfamiliar with a site or product! Here, you'll find the following text prominently displayed: "Zed is a high-per…
Seriously, what do people think when designing headers like this? Like wow we should totally link to every other part of our site except the homepage.
Because who would want to go there after they found out about a project through a blog post?
I know it’s small thing but it annoys me so much when the blog section of a site doesn’t have a link back to the home page. Seriously, what do people think when designing headers like this? Like wow we should totally link to every other part of our site except the homepage. Because who would want to go there after they found out about a project through a blog post?
This is not always great for accessibility (they don't have alt=, title=, or aria-*= attributes on the or tags) but seems to be a common pattern.
Unless I missed it, the video doesn't actually answer the question. They talk 38:50 onwards about how they don't want to pull in GTK / Qt as dependencies, rather they just want to be able to read the toolkits' config and render a mimicking UI themselves. Then they show the editor opening a "native" file dialog, but don't actually say how exactly they did it.
Anyway, I assumed they would use xdg-desktop-portal, and based on searching the repo that does seem to be the case.
I know it’s small thing but it annoys me so much when the blog section of a site doesn’t have a link back to the home page. Seriously, what do people think when designing headers like this? Like wow we should totally link to every other part of our site except the homepage. Because who would want to go there after they found out about a project through a blog post?
The logo in upper-left links to zed.dev, if that's what you mean. This is not always great for accessibility (they don't have alt=, title=, or aria-*= attributes on the or tags) but seems to be a common pattern.
There's a bit of detail here: https://github.com/zed-industries/zed/issues/7015
But I'd be curious to read a longer writeup on the tradeoffs and how they came to their decision.
>Yup, that's a native file dialog, but we don't use GTK in Zed and that clearly is GTK — so, how does that work? You'll find the answer in the companion video in which Mikayla and I dive deeper into this and also touch on the question of whether or not we should use GTK or Qt or something else (spoiler: it's complicated). Unless I missed it, the video doesn't actually answer the question. They talk 38:50 onwards abou…
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 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.
>Yup, that's a native file dialog, but we don't use GTK in Zed and that clearly is GTK — so, how does that work? You'll find the answer in the companion video in which Mikayla and I dive deeper into this and also touch on the question of whether or not we should use GTK or Qt or something else (spoiler: it's complicated). Unless I missed it, the video doesn't actually answer the question. They talk 38:50 onwards abou…