Am 29.12.2014 um 01:19 schrieb Peter Hutterer:
On Sun, Dec 28, 2014 at 09:42:07PM +0100, Alec Leamas wrote:On 28/12/14 18:05, Michael Catanzaro wrote:On Sun, Dec 28, 2014 at 9:48 AM, Alec Leamas <leamas.alec@xxxxxxxxx> wrote:Possibly. But isn't there quite a difference between the "novice user" and the Fedora Workstation target user i. e., developers?Not necessarily. I wrote: "Yes, Workstation targets developers, but not exclusively, and also developers who use fancy IDEs and who don't work with the terminal. I just don't want this thread to degenerate into a discussion of this lousy definition [of normal/novice users], since it's not important. What's important is that we want Workstation to be excellent for users who never touch the terminal."Hm... developers which never touches the terminal?! Seems like a really narrow group (?)it's not as narrow as you may think, developers may use the terminal selectively for some tasks and the GUI exclusively for others. That subset isn't the same for all developers, so you end up having to provide all features working well in the GUI.
exactly!but not hide terminal apps and pretend nobody should have a need to use them these day
e.g. I hardly ever use nautilus to handle fils, but I also hardly ever use the terminal for any configuration, connecting to networks, firewall stuff, etc. etc. I hardly ever use it to start non-terminal apps except for eog/evince. so even though I use the terminal heavily, I still would count myself in the above group and I definitely need a good GUI around my terminals. And, I want my desktop to be simple and get out of the way of what I actually want to do.
exactly!but that completly different to "a user should not need to know what a terminal is or find terminal apps in the software center even if he knows them by name for good reasons"
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
