Canonical Developers To The Community: Help Us Figure Out The Direction Of Mir

[Geopirate]

We have the Gnome, KDE and Enlightenment Wayland implementations, is Mir already on par with these? If not that's where they should really put their efforts. I know it's unreasonable to expect everything to get ported to Wayland overnight but it's happening over time, but the time they get Mir into shape, there will be more and more apps. I know there are a lot of power users on this forum, but it's getting pretty close to the point that regular people can run a pure Wayland system.

[Awesomeness]

Dumping MIR will help nobody. Helping MIR could help the smaller Desktop Environments to get wayland support, like MATE. MATE does not have the resources to migrate to wayland but with MIR they may get there.

Mate could just as well use libmutter for their window manager. Elementary does that for their Pantheon desktop. Seems to work fine. CLA'ed Mir crap is not needed for small desktops.

[DanL]

Such a thing already exists. It's called ndiswrapper

Ndiswrapper is OK, but it is still much better to just do some research before buying

ndiswrapper is for Win XP-based drivers, which are becoming rare, and Win XP-64 are even rarer. ndiswrapper is almost irrelevant today.

[starshipeleven]

3) The attitude that "people who need windows app or hardware should use windows" is why Linux remains at 3% desktop user share. Many of us have wanted to get off Windows but cannot because we are tied to proprietary apps and some hardware that Linux does not support.

If you're tied to proprietary crap and it is bothering you, then you should fight to break free from it, not whine to relax rules in a vane attempt to get your cake and eat it too.

You know "fight", that thing that requires resources to get some shit done at the end and resembles "work" in many ways.
Pay for opensource development, campaign for opensource awareness, that kinds of stuff.

The main disageement I have with RMS is that by supporting some binary drivers from Windows, in the long run, most of the world would be running a fully open source OS.

This is illogical. If you allow binary drivers then you aren't running a fully opensource OS.

[starshipeleven]

Such a thing already exists. It's called ndiswrapper

True, but for the sake of kittens I'll clarify.
Ndiswrapper is OK, but it is still much better to just do some research before buying, or finding a good source of supported wifi cards to swap.

[pracedru]

They should work on improving desktop Ubuntu so that it might get profitable.
MIR wont be the compositor for Ubuntu anyway.

[nomadewolf]

MIR is not comparable to wayland. MIR is AFAIK more like Weston (window management and compositor). Andit now works with wayland. Dumping MIR will help nobody. Helping MIR could help the smaller Desktop Environments to get wayland support, like MATE. MATE does not have the resources to migrate to wayland but with MIR they may get there.

Can't they 'copy paste' stuff from Gnome or KDE, instead of MIR? Or even Weston?
Anything but MIR.

[Steffo]

C++ is really horrible. From build tools, to testing, to package management, to STL, to the actual code. Rust is here a real relieve for embedded projects.

[DanL]

No, your post is unrelated to the topic.

Yeah, because I talked about the future of Mir. That was totally unrelated...

If the community decides that Mir is a no-go

That's not the question the referenced post/thread asked. Go read it, because you obviously didn't. If you want to dance on Mir's grave, go to sleep and maybe you'll have a dream about it.

[jpg44]

I do actually agree that the Windows App issue is gradually going away. Slowly. Not for necessarily good reasons from an open source or user rights perspective, because its due to Software as a Service. Running apps on a cloud rather than on the desktop is even worse, even where both are proprietary, due to who posesses the data. Its a throwback to the bad old mainframe days.

I've always thought, companies could save resources if they were using Qt for app development rather than for proprietary APIs. Often the issue has been the quality of the RAD and app development tools which is why people would develop for propreitary platforms. Its more developers choose their development tool by has the fastest workflow and best feature set than choose the API.