On 29/12/14 10:50, Richard Hughes wrote:
On 29 December 2014 at 03:28, Stephen John Smoogen <smo...@gmail.com> wrote:
we either are going to have to get out of the way of the
steamroller or get rolled over it.

[cut]

Linux isn't UNIX. The desktop doesn't revolve about command line tools
anymore. If you can't accept that, you probably need to change
industry. Sorry to be blunt.

2014-12-28 21:38 GMT+02:00 Michael Catanzaro <mcatanz...@gnome.org>:

What's important is that we want Workstation to be excellent for users who
never touch the terminal.

Great. But what if the design decisions based on this leads to a system which becomes needlessly complicated for other users, which also uses CLI tools?

Frankly, I think it's easier to alienate current devs (some of which using CLI tools) than to attract new ones. So, pushing this goal too hard might have consequences.

> On 28/12/14 10:50, Richard Hughes wrote:
on 28 December 2014 at 00:23, Alexander Ploumistos
<alex.ploumis...@gmail.com> wrote:
Should Fedora build another program as a package manager?

GNOME PackageKit is still available (and maintained upstream) and is
what I use for installing things like mingw packages that I need for
development.

This certainly works, but is it really a reasonable trade-off in a developer context where things like compilers and interpreters are part of the very core? What role does Gnome Software play here? How fruitful is the idea to hide packages in this context?

Note that I have full respect for your goals. I use Gnome myself, and I didn't find 3.0 to painful :) It's just that I don't really see how the priorities for Gnome Software aligns with developer realities (while they make perfect sense for other types of users)

That said, everything is fine if the Fedora Workstation target user is a developer just using GUI tools. But I don't see this in the PRD.

Cheers!

--alec

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Reply via email to