From: a@9srv.net
To: 9fans@9fans.net
Subject: Re: [9fans] Newbie - wassup everyone?
Date: Sat, 20 Apr 2013 23:13:36 -0400 [thread overview]
Message-ID: <84315c5350862c9cde01bc62af914c57@9srv.net> (raw)
In-Reply-To: <h6t9jw7m0f72wm3ahr9itnni.1366508689121@email.android.com>
// What do you guys think?
Generally, I think you'll find the answer is "we quite like it".
The main reason it is the way it is (and, talking about just
the UI, it's more or less been this way since 1989) is that
folks who become familiar with the system generally find
it quite powerful. You talk about "sleek", and in the sense
of "minimal waste", rio very much is. What is isn't is shiny.
And I suspect you'll find relatively few people on this list
who'd rather rio look more like OS X.
There's plenty of room for experimenting in wms (I've
been an advocate for some variation of the "alternative
wm" project in GSoC for years now), but I suspect you'll
get very little traction focusing on issues of insufficent
glitz.
Anthony
next prev parent reply other threads:[~2013-04-21 3:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 1:44 Keith
2013-04-21 3:13 ` a [this message]
2013-04-21 3:50 ` andrey mirtchovski
2013-04-21 7:06 ` lucio
2013-04-21 12:21 Erik Quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84315c5350862c9cde01bc62af914c57@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).