Ok , I kinda see how its useful when you have user based accounts at login at a facility…
But It still seems like just adding process’s to something that was fine , and actually useful , sometimes someone just needs to jump on but has wacky hotkeys , no problem with the old system.
In very basic situations where there is just one login to the machine , this new way will become pretty annoying fairly quickly if there are more than one person using the machine I would say.
I think this ticks off a few things that were requested.
– import/export user for mobility
– user shortcuts, preferences, presets all travel with that export.
– software version agnostic user (no more making a user for each version)
– shortcuts are backwards/forwards compatible.
I feel like this addresses many things that freelancers and facility admins both wanted.
Is switching users really that painful?
Having to create an OS user might be weird but it seems to me like there will be less pain later because you won’t have to keep doing this over and over.
Single users/single use-case on a workstation is a rarity for freelancers.
It is more common for a freelancer with a laptop to use a single administrative account to connect to multiple domains over the lifecycle of that user account.
Not only is this impractical but insecure.
Binding your non-secure hotkeys/preferences in a portable way means that it’s trivial to transpose your working characteristics when flip-flopping between post-house-X and post-house-Y or SECRET-CLIENT-X or SECRET-CLIENT-Y.
To be clear - I never asked for this functionality because I’m an unqualified buttton pusher but i’m happy that this transition has been implemented so successfully. (I suspect that user prefs is only the start…)
I don’t get what is so hard about creating a different user on a system? Instead of changing what user is using Flame at application level, you’re basically doing the same thing at OS level.
With all the benefits this new approach brings and all the user requests that it satisfies, is this really something worthy of complaint?!
Exactly… every other software saves user prefs in the user home directory. Flame took to long to switch, then everyone got complacent and used to the old “black box” method. This has been a 10 year journey of Flame adapting to behaving like a normal app. It started with undoing Flame running as root user and having un-secured access to EVERYTHING. The next step would be undoing the spaghetti web of services that are Stone+Wire, and the most fragile and problem prone part of Flame.