On Thu, 2005-07-14 at 14:42 -0700, Frederic Fouche wrote:
> This thread is going nowhere,
Indeed. You aren't listening to a simple point.
> It was said that an application written years ago might not work if
> Xaaes gets new implementations, as drastic as they may be.
No - no one ever said anything like that. The additions don't prevent
older applications from running. Its still backwards compatible. So,
if you can run old apps on the new OS, then you don't have to reboot.
> Same thing that happened with other OS, (linux, see gtk2 vs gtk1 as
> someone mentioned earlier), same with macos and windows XP.
You really need a better example!
You keep saying stuff like this, but its not true! GTK1 applications
run under Gnome2/GTK2 just fine. If one had to reboot to run XMMS (a
GTK1 application), than I can guarantee it would have been forked and
rewritten by now (actually it has, but XMMS has more plugins than the
fork) but it runs just fine, so it stays. So, thanks for the example
that proves my point. XMMS would have to be rewritten to be GTK2
compatible and use GTK2 features, but it still runs with no changes, no
reboots, no logging out - just double-click and mp3 and up pops XMMS.
Also, GTK2 was done because of shortcomings in GTK1. GTK2 is faster and
more efficient, has way more features for the developer, and therefore
the user, and application development increased dramatically when GTK2
came out. Thats what we want to do with XaAES.
GTK3 should be coming out soon! They're cleaning up incompatible APIs
and the 4 ways to write fonts, and 3 different canvas widgets and 20
different ways of handling graphics and using Cairo for all of it, and
it will break binary API again. Apps will have to be rewritten to work
with GTK3, but GTK2 will still be there, and GTK2 apps will still run
without rebooting. Thats what we want to do with XaAES.
Thats the sort of upgrade we're talking about. New API, needs new stuff
to work, new features, but old apps will continue to run.
> If you want to run all your applications (old and new), you will need
> to reboot to change your OS.
Not *MY* OS. How can you make such a statement when I'm currently
running everything I need to, and my boot menu has nothing on it but my
main OS and an emergency partition with some rescue tools (I'm a Unix
Admin so I'm careful)! I have stuff (somewhere) that goes back to Linux
pre-1.0 days, back when I still had an STe, and it will run on newer
systems providing you have the libraries around that it was meant to
link with.
> This is fairly clear and simple, yet you always find a comeback to
> continue arguing.
>
> Obviously I am missing something, so I'll stfu.
Here's what you are missing. I do NOT reboot to run an older
application. Not ever!! I don't believe its acceptable to do so.
Thats the one point you keep missing. You keep saying that its some
impossible utopia, but thats the situation I have RIGHT NOW.
But yet, you call me a liar and tell me STFU. Evidently I struct a
nerve if you lash out and tell me to STFU, and I stand by my accusation
of some sort of insanity or mental disorder.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com