I am curious why they went with Weston as their Wayland compositor as opposed to Mutter, if only because it seems to be the most popular due to Gnome. I'm not familiar enough with the trade-offs between the two. Anyone care to theorize why?
I am curious why they went with Weston as their Wayland compositor as opposed to Mutter, if only because it seems to be the most popular due to Gnome. I'm not familiar enough with the trade-offs between the two. Anyone care to theorize why?
Depending on the OEM you work for and how vertically integrated your organization is, you may also have a large and complex supply chain catering towards your products, with complicated RASIC matrices for who supplies you want and vendors held to KPIs for their BSP and their hardware. Due to various factors Weston may be what they already have patches in hand for, e.g. for proprietary buffer integration, etc.
(I work on KDE Plasma, including its Wayland support, and am a system architect for a large automotive OEM making Wayland-based infotainment systems, neither of which use Weston however.)
Unsurprising because it's not the first time Sony bet on an unusual language (https://news.ycombinator.com/item?id=1938652) and people on HN were similarly excited. Days later the initiative was put on hold and the domain doesn't even resolve today. I think it's safe to say that their initiative did not end up as a huge success.
Surprising because according to their own presentation they want to use an alpha version technology created by a company which is known to be cancelling projects on a whim and which is not really using said technology for anything important.
A decade later one things remains clear: you can count on HNers to jump on any obscure programming language and praise it to the skies.
flutter channel dev
flutter upgrade
flutter config --enable-linux-desktop
The app then built without issue, and executed fine... except for a rather annoying bug: nothing was painted in the window until I resized it.