Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's based on X11, unfortunately. I've fully transitioned to Wayland based desktops I would be very happy to try FyneDesk if it would be based on Wayland.

I see they work on full Wayland support, and targeting to do it in v5.0. What's the ETA? Last release was 1.5 year ago!

> The 0.4 branch of releases marks the end of X11 native implementations as we will begin the move to Wayland (and XWayland) for 0.5. > https://github.com/FyshOS/fynedesk/releases



Plans shifted due to external factors - the next release will be X11 but after that (later this year) work begins on the Wayland transition.

Ideally we will support both through the transition but unclear at this time.


> You can expect work (on Wayland) to begin on that after the upcoming major release. We are waiting on a fix in an upstream library.

from the Author


I was under the impression that there’s a seamless compatibility layer for running X11 under Wayland?


Nope, while it is possible to run normal X11 apps under Wayland, there is no support for running X11 window managers.

Which is a damn shame, because window managers are where some of the greatest innovation is happening.


X11 window managers are replaced by wayland compositors. they are more complex, but multiple alternatives already exist.


Sure, but those are not backwards-compatible. If Wayland let me run my existing window manager then I would be glad to try it out.


i am responding to "window managers are where some of the greatest innovation is happening"

innovation is happening with compositors too.


Xwayland exists, but you need a compositor to be running to encapsulate the Xwayland container.


Wayland is a dead end. It will never replace X11 because it's architecture is fundamentally flawed and prone to lags by design.

It's support for CJK input is also basically broken with no chance of ever getting revived.

Our best bet on a solid Linux gui lies with XLibre.

However, saying that, a gui written in Go has very little reason to exist, because we already have excellent GUIs written in lower-level languages.

If there is anything Linux doesn't lack it it's desktops.


If you want to code everything in low level languages feel free. I guess assemblers still work well or you can just list machine code.

For those who want a fast to learn and use higher level language for this Go is a great tool and there are great projects out there. Two of them in the top 10 for all cross platform beating out a lot of other languages (no presence of GTK or Qt up that high... https://ossinsight.io/collections/cross-platform-gui-tool/)


>For those who want a fast to learn

Why would I want something "fast to learn"? That sounds like one of the most ridiculous arguments when choosing a tool to master ever. On the level of "I chose this university because it was walking distance from home".

I'm choosing a tool I'm going to be using for the next 40 to 50 years. Whether it takes a month or a year to learn makes no difference whatever.

I want a tool language which is widely portable, so that I could run my programs without rewriting them on as many machines I own as possible.

I also want them to run as fast, as possible, because I want to run many useful programs on moderate hardware.

I want to be able to use as many libraries and external utilities as possible, because nobody knows when I might need them.

It should also work without internet, because who knows when exactly the government is going to cut the wire.

These core features are what I b would not even consider a language at all. The rest is bells and whistles. Nice to have, but completely optional.

>Two of them in the top 10 for all cross platform

I've never heard about any libraries from that list. In any case they seem like tools to write webpages, not tools to write desktop software.


I would argue that regardless of Go is low-level, for something as fundamental as a desktop environement, a lower level language makes sense.


I guess that's an interesting opinion to have. Is this based on having built your own desktop environment or some other project that led you to this conclusion?

For me I prefer higher level code and tooling wherever possible. Building this has been blazingly fast compared to previous window managers I have worked on.


I prefer higher level code and tooling wherever possible

exactly this.

go actually strikes a balance of being one of the few high level languages that can compile directly to binary. there are not many languages that can do that. common lisp, erlang, o'caml and maybe red are a few others that i am aware of. there are probably a few more that are less popular that i don't know.

for me high level implies at least automatic memory management and high level data types.


I mean much of gnome shell is written in JavaScript. But of course GTK is C.

Does Fyne have bindings to other languages? A search for fyne python gave some hilarious AI slop from Gemini suggesting pip install fyne, but the fyne python package is something completely different and unrelated. The nice thing about GTK is it can be used from virtually any language (QT a bit less so but still a lot)


No. Fyne does not have any bindings and never will in the official project. The API is designed to work perfectly with the Go idioms and using it from any other language will be no where near as intuitive. Not to mention it would slow down the developers of the toolkit as well!


The metrics on that ranking are super questionable. Not least of which because gtk and QT are not developed on GitHub.


This takes forever to load.


First of all cool concept. I'm looking forward to playing with the DE even if it doesn't replace my daily DE. In my experience, extending an existing project in Go is much faster than lower level languages. The opinionated build and dependency system can seem limiting but really helps one get up to speed quickly on a new project. Just setting up a build environment for a low level language based project can be enough of a hassle/time sink to dissuade me from attempting with a quick toy project.


> However, saying that, a gui written in Go has very little reason to exist, because we already have excellent GUIs written in lower-level languages.

You say that as if it's a good thing. The fact that our platforms depend on C and C++ is not a feature, it's a bug.


I really dislike the way xdg-desktop-portal works though. Ive been totally unsuccessful trying to implement colour picking in Arch/Hyprland with it. The API is absolutely abysmal


Your comment seems very entitled.

When it’s ready, and faster if you help.


No doubt it could be read that way, but this is where the following site guideline (from https://news.ycombinator.com/newsguidelines.html) is helpful: "Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith."

Clearly there are stronger plausible interpretations of the GP. Following that guideline tends to prevent getting caught in snags like this little subthread, making discussion more enjoyable for everyone.

(I don't mean this as a criticism! it's just a nice case to comment on because it's particularly clear.)


It's not entitled to not want to try out some new thing if it has major drawbacks over what you are already successfully using.

If someone randomly comes up to you and offers you an apple with a rotten spot and you say "No thanks, there's a big rotten spot" would you expect them to scold you for being entitled and looking a gift horse in the mouth? _They_ came up to _you_ offering an apple!


Nobody came up to them though, they opened a hn article that wasn’t posted _for them_, decided the product isn’t for them, which is fine, but then decided to post about how it’s not for them. The project maintainer didn’t ask if the project suited gp, nobody did.


Nobody asked anyone anything. It's a post with people sharing thoughts. You don't even know if the maintainer is the same person as the author. As far as feedback goes, if the comment gets enough upvotes it shows a significant number of people share the sentiment, and would be something for the maintainer to consider if he wants a broader audience. Nobody expects the maintainer to respond or care though.


That’s like me abruptly telling you I don’t like the way you dress or the shape of your body. Unless you ask, it’s an unwelcome comment.


actually, it's more like you are selling clothes, and i don't like the style, and i am telling you which style i'd like to buy.

you don't have to produce my style, and i don't have to buy your clothes, but it's good to talk about our preferences so you have a better idea of the potential market.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: