Wine fans have a reason to smile today. Wine 11.0 is finally here, and it is a big deal for anyone running Windows software on Linux. After a full year of work, more than six thousand code changes, and hundreds of bug fixes, Wine is moving forward in a way that feels like a turning point. This release tightens up major subsystems, improves performance, expands hardware support, and carries a big win for compatibility. If you have been waiting for Wine to feel smoother and a little less fussy, 11.0 might be the moment you jump back in.
The problem of graphical settings. Needs more work, quickly gets confusing, ages badly. A fine .cfg from 1980 is still a fine .cfg now. It’s place in the FS hierarchy might have changed but that’s not a concern of the .cfg.
There’s really no excuse, proper project management would have replaced the UI and verified the new version included all the old functionality, organized well together with whatever new functionality they added. I think they were trying to keep old hats happy with the changes by letting them keep their old version, but it’s better to just rip the band-aid off if you’re gonna change it, now it’s a mess for everyone.
Ah, Microsoft-specific, i think it’s mostly because of their 10+ UI frameworks.
Why not both? A frontend for a cfg file for convenience and flexibility
The boring answer is that it is more work and most FOSS developers are volunteers.
Sure, yes. Even in games, it’s a nice thing if you can set some engine options or custom resolutions not represented in the GUI.