From: "Jeebs" <Jeebs@yango.us>
To: jhoger@pobox.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu development schedule?
Date: Mon, 30 Aug 2004 17:51:31 -0500 [thread overview]
Message-ID: <002001c48ee5$456d6a30$20389c3f@computername> (raw)
In-Reply-To: 1093903154.26682.44.camel@aragorn
> There are already projects around adding front ends. QEMU works just
> fine from the command line. This is a proper separation of work from a
> software designer's point of view.
The only gui front end I've seen is Qemu Workstation, and the last I
checked, it was way out of date and didn't work with the current builds.
The command line is okay, but it's a little inconvenient at times. And
switching back & forth between the target screen and the command screen
doesn't always work with the Windows version. I often end up with just a
black screen. (Maybe that has been fixed. I've been busy the past two
weeks and haven't tried any of the daily builds on FreeOSZoo.)
> For most, usability of an emulator can be summed up in one word: speed.
> Any effort to address speed improvements (and at the same time,
> stability which is ongoing) is core development.
I think usability and accuracy tend to be a bit more important.
It doesn't matter how fast it is, if it can't emulate a real computer enough
to do what you need / want to do.
(Of course, that doesn't mean you should make it as slow as Bochs...[grin])
> Are you sure it makes sense have the core developers concentrating on
> Windows installers or front ends?
I'm not really sure who the "core" developers are. All I ever see is
Fabrice.
Everybody else just seems to be doing the occasional patch to fix some
little aspect etc.
I've been lurking here for 3+ months and I'm not sure what organization, if
any, there is in this project.
> For those that can't wait for "polish," commercial products are out
> there for the Windows platform, and Linux too.
I'm currently using VMWare.
But as I said in my message, I was just getting the feeling that things were
being implemented on "whims" by lots of people, with no real plan of what
was needed, what was important, etc. etc.
That's the way it often is with open source porjects. Everybody does their
own thing when ever they feel like, and since most people don't like to do
the "grunt" work, many important but less exciting issues often get pushed
off to the side or only done "good enough for now".
> Having watched this project for a while I see QEMU as a very healthy
> project. It is growing rapidly and improving in core functionality. In
> some areas it has already outstripped commercial offerings.
I fully agree with out.
It's developing very very rapidly. That's one of the reasons I've been
following the development for the past few months.
> But I suppose the only real indicator of real success of FOSS projects
> is when the complaints start rolling in ;-)
I wasn't trying to complain.
My message was a genuine question.
And it was sort of a 'notice' to people that maybe it might be a good idea
to start working on things that are at least as important, but aren't
"sexy".
next prev parent reply other threads:[~2004-08-30 23:06 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 21:44 [Qemu-devel] Qemu development schedule? Jeebs
2004-08-30 21:59 ` John R. Hogerhuis
2004-08-30 22:51 ` Jeebs [this message]
2004-08-31 11:59 ` Johannes Schindelin
2004-08-31 15:58 ` Jeebs
2004-08-31 16:27 ` Joe Batt
2004-08-31 17:42 ` Jeebs
2004-09-01 19:25 ` Kai Cherry
2004-09-01 19:33 ` andrej
2004-09-01 19:46 ` Joe Batt
2004-09-01 20:34 ` Mike Tremoulet
2004-09-01 20:46 ` Kai Cherry
2004-09-01 20:35 ` Kai Cherry
2004-09-02 20:46 ` Jim C. Brown
2004-09-03 7:52 ` [Qemu-devel] Filegetopt (Was: Qemu development schedule?) Renzo Davoli
2004-08-31 16:32 ` [Qemu-devel] Qemu development schedule? Johannes Schindelin
2004-08-31 17:40 ` Jeebs
2004-09-01 15:43 ` Lionel Ulmer
2004-09-01 17:03 ` John R. Hogerhuis
2004-09-01 19:07 ` Kai Cherry
2004-09-02 10:20 ` Info
2004-08-31 17:42 ` John R. Hogerhuis
2004-08-31 19:07 ` andrej
2004-08-31 19:44 ` Kai Cherry
2004-08-30 22:07 ` Hetz Ben Hamo
2004-08-30 22:59 ` Jeebs
2004-08-30 23:34 ` John R. Hogerhuis
2004-08-31 9:21 ` Kai Cherry
2004-08-31 10:15 ` Patrick Mauritz
2004-08-31 10:23 ` Kai Cherry
2004-08-31 17:23 ` Gianni Tedesco
2004-08-31 19:08 ` Kai Cherry
2004-09-01 20:53 ` Magnus Damm
2004-08-31 20:27 ` Fabrice Bellard
2004-08-31 21:50 ` René Korthaus
2004-09-01 22:04 ` Jim C. Brown
2004-08-31 22:02 ` Patrick Mauritz
2004-09-01 21:58 ` Jim C. Brown
2004-09-02 7:26 ` Lionel Ulmer
2004-09-02 20:56 ` Jim C. Brown
2004-09-02 23:28 ` Lionel Ulmer
2004-09-03 0:07 ` Jim C. Brown
2004-09-03 8:32 ` Fabrice Bellard
2004-09-03 7:29 ` Adrian Smarzewski
2004-09-03 8:28 ` Fabrice Bellard
2004-09-02 23:53 ` Daniel Serpell
2004-09-03 0:13 ` Jim C. Brown
2004-09-03 1:35 ` John R. Hogerhuis
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='002001c48ee5$456d6a30$20389c3f@computername' \
--to=jeebs@yango.us \
--cc=jhoger@pobox.com \
--cc=qemu-devel@nongnu.org \
/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).