What killer feature(s) would the MX devs love to implement?

[Arnox]

Assume you have unlimited time but not money.

[dolphin_oracle]

Working desktop-agnostic gui switch nvidia Optimus graphics. Solutions for Ubuntu and arch based distros tend not to work on Debian.

[MikeR]

Thanks, guys. Great distro!!

[MadMax]

Not a dev, but I'd like automatic and working in-place-upgrades from one main version to another like e.g. Mint does it :)

[Charlie Brown]

... But Mint's is actually no different than MX's:

It's done through normal updates
However it won't upgrade i.e. from 17.3 Rosa to 18.0 Sylvia (different Ubuntu bases).. so, you need to reinstall.

[MadMax]

There is mintupgrade which allows jumps of major versions I used this to upgrade my Mint system from 20 to 21 successfully.

https://linuxmint-user-guide.readthedoc ... nt-21.html

[Germ]

Not a dev, but I'd like automatic and working in-place-upgrades from one main version to another like e.g. Mint does it :)

[manyroads]

Also not a dev, but I have wished for years that there was an MX minimal version that supported the choices of Debian Test and Unstable

EDIT: and let me add in my waxing: it would be nice if the version allowed init choice(s) as well.

I believe that type of test bed would allow a lot of pre-trial work on MX before major technology changes, like Wayland.

[AK-47]

Where do I start?

• Fine-grained window and decoration metrics and colour scheme support, as was possible on Windows 7 and earlier.
• 3D style/skeumorphic themes and icons, not like the boring flat icons and boring flat borders of today.
• UAC-style Sudo prompt that can't be tampered with by applications (or at least, is hard to do so). Or a simple "Yes/No" prompt instead of having to enter the password every time, if so desired.
• A proper GUI toolkit that isn't a glorified OS on steroids (Qt), isn't encumbered by regular breakage (GTK) and well-integrated into the desktop environment.
• Move much of the drivers out of the kernel and as separate modules, so the kernel doesn't have to be rebuilt every time it's updated.
• Minimal non-bloaty boot loader that doesn't take 30 seconds to decide that, yes, that disk drive is indeed, a disk drive.
• Device Manager style GUI hardware manager.
• Case-insensitive file system
• A proper servicing stack for updates, instead of the bodge "let's run this and hope it doesn't crash the session" solution.
• One single, coherent service management system.
• One single, coherent init system (instead of five)

[siamhie]

EDIT: and let me add in my waxing: it would be nice if the version allowed init choice(s) as well.

I believe that type of test bed would allow a lot of pre-trial work on MX before major technology changes, like Wayland.

antiX is playing around with that idea currently.

We offer you a development release of antiX-23-full edition (32 and 64 bit) shipping with 4 init systems out of the box and still systemd-free!

*sysVinit
*runit
*s6
*s6-66

This ‘spin’ has been developed by ProwlerGR and is fully supported by the antiX team, even though it is in development stage.

* Multiple grub (isolinux) entries available allow to boot live into any of the 4 available inits
* The s6-rc Service Manager (inspired by the runit Service Manager), comes preinstalled making s6-rc management a breeze.
* Service files have been optimised, providing a very strong foundation for any official work to come.

UNOFFICIAL antiX-23 “init-diversity” spin. https://www.antixforum.com/forums/topic ... sity-spin/