- cross-posted to:
- linux@lemmy.ml
- hackernews@lemmy.smeargle.fans
- cross-posted to:
- linux@lemmy.ml
- hackernews@lemmy.smeargle.fans
You must log in or # to comment.
Somehow all these OSS projects that start with only a Mac client seem so suspicious to me…
I wonder if they will enforce a login to use the software?
It’s open source, and they already said they were Mac only because they used Metal for rendering. It’s not suspicious for devs to use what they’re most familiar with.
because they used Metal for rendering
That in itself is a suspicious choice tbh
What’s suspicious about it…?
deleted by creator
Until you actually try to use Vulkan on macOS. Since there’s no native support, you end up needing MoltenVK.
deleted by creator
deleted by creator
Is there any particular problem with MoltenVK? As I see it, it’s by far the best solution for cross platform software on macOS in need of graphical hardware acceleration.
There’s nothing wrong with the software itself. It works great for what it does. On the other hand, it’s a compatibility layer, which always increases friction between things a little. I think the best use for this is running legacy software.
There aren’t many alternatives. Maybe in the future, we’ll see graphics API abstraction libraries like wgpu get used more. This gives developers a single API which can use DirectX on Windows, Vulkan on Linux, or Metal on macOS. This could allow support for entirely new graphics APIs without developers using it having to do anything.
Of course, that’s my opinion. People can build their software how they like.
They start with Mac clients because those devs use Macs.
While I generally agree with your skeptical attitude toward this, I think the fact that they were targeting Apple’s Metal graphics API to built the most performant possible IDE makes sense. You can’t just snap your fingers and have a Linux graphical stack start working with your software.
I think the reason they targeted macOS first is probably because many of the dev team uses Macs.
As a Linux user, I’ll happily wait for software like this to get ported to native Linux APIs so we get performant text editors instead of more Electron crap.
As a die-hard Linux user, I understand that most of their devs probably used Macs. Sadly, they are likely not an outlier which means many ( most ) of their target customers are Mac users too.
Overall, I applaud their focus and platform native approach. Let’s hope we get a decent Linux editor out of it at some point.
I miss the point why they don’t invested into Flatpak. I mean, with Flatpak they could’ve focus on make Zed works on the Flatpak platform and, as a consequence, it will be fine in every distro. The only thing that they should’ve be taking care is X11 and Wayland, but every other aspect to worry such as distro choice, QT/GTK, Gnome/KDE, etc would be vanished away
Or just install with cargo, have it run unrestricted and still work everywhere. I dont think rust apps need to be flatpakked
FWIW I’ve been able to compile Zed for Wayland only by removing any X11 references in the code and I’ve been using it for about two months or so.
