Removing OnlyShowIn / NotShowIn from desktop actions

[Sebastien Bacher]

Le 03/07/2013 23:04, Aaron J. Seigo a écrit :
> You apparently live in more segregated world than the rest of us.

Hum, I don't think that's true. I do work in an environment where the 
decisions taken are often "challenged" by others, because they have 
different views and want to ship the same components in a different way 
though

>
> I know people who write QML applications for Ubuntu Touch in a Plasma Desktop,
> and people who write Plasmoids in Gtk+ based desktops.

Right, I'm not trying to argue against that and it's fine. I'm speaking 
about defaults.

Staying on the IDE example, if you have templates for 15 
languages/toolkits, you can either:
- list the 15 in your context menus,
- list none (e.g because you don't want to pick a preferred)
- decide to put in front those you selected.

If in your environment/enterprise there is a preferred technology, it's 
likely that the system administrators will want to list the preferred 
choice there...

>
> As I noted in my first email, this feature is a great way to build artificial
> lock-in. Thank you for demonstrating my point so clearly.

I don't think making calls on a selecting a limited number of options to 
expose in your UI = building artificial lock-in. The alternative is to 
list every single possible option or none, and I don't believe either of 
those is better for users.

The example there is maybe not well chosen and I don't intend to try 
"defending" it further. I didn't want to start an argument in the first 
place (especially not on a made up example), I was mostly sharing a 
different perspective on the topic.

Thanks for reading, and feel free to ignore the point raised here if it 
doesn't make sense in the context.

Cheers,
Sebastien Bacher