Freedesktop.org on KDE/Gnome, New Goals 340
fdo writes "OSNews has a long and juicy interview with the freedesktop.org developers regarding many aspects of their project, including interoperability between GNOME/KDE, the new X Server, the new Hardware Abstraction Layer library, accessibility, package management and in general, all things desktop."
So I can copy and paste now? (Score:5, Funny)
Re:So I can copy and paste now? (Score:5, Interesting)
I Agree 100% that X clipboard copy-paste support is terrible and freedesktop should focus on that, instead of eye candy and breaking speed records.
I talk about exchange of non-ASCII data through clipboard (I want to emphasize that as I can see that many OSS types think that clipboard is for text only). I mean copying and pasting images, fragments of images (rectangular an irregular shares), with alpha channel; sound clips; video files; HTML with images copied to local application (not some lazy trick where HTML copied from Mozilla to OpenOffice has all HTML untouched and IMGs are still loaded from the network when you save that file and try to open it at home).
The X contains all necessary infrastructure, as explained here [jwz.org] and here [tronche.com].
When you actually try to use the X clipboard for something more that transferring plain text, the results are terrible. Read this [slashdot.org], this [slashdot.org] and this [slashdot.org] Slashdot comment. Shocking.
Re:So I can copy and paste now? (Score:2)
Personally I belive the clipboard should only contain text, but the people is already used to this file-system-on-the-clipboard. X needs this more than any visual candy they are adding now, and it should be really simple to implement.
Re:So I can copy and paste now? (Score:3, Interesting)
While I agree that the copy-paste support of most X application is terrible, I think it is important to state that it is the applications that are lacking, not X. As you write, the architecture is there for copy and paste, also for copying things other than text, it is just that most (all?) applications do not support it.
The reason is simple: if X lacked the support for this, then we would have a cache22 problem trying to get it implemented bot
Re:So I can copy and paste now? (Score:2)
I only read the first page of the article. I won't tell you the obvious of what you need to do...
Re:So I can copy and paste now? (Score:3, Insightful)
It's non-root for processes/users for all NT class OSes (NT/2K/XP)
Environment variables have been around since DOS days ($var vs. %var% big whoop)
And emacs? [gnu.org]
ACLs are a superior way (although logically equivalent) over the user/group semantics of POSIX. Try implementing "Payroll can read/write, HR can read, compliance can read, users can append" in an easily maintained manner using POSIX semantics.
Re:So I can copy and paste now? (Score:2)
They're not logically equivalent- ACLs are more descriptive theoretically. That's because although one can emulate most any kind of ACL with clever group-id setup, all Un*x that I've seen implement uid and gid as bitflags.
Meaning you have a hard upper limit on the number of groups. Meaning that you'll run of of POSIX groups when trying to emulate ACLs of above a certain complexity.
(Maybe the POSIX standard s
Re:So I can copy and paste now? (Score:2)
One trivial and quick example: if you had never, ever, ever used a computer before this first session, how would you go about turning off the system? Would you think to click on the "Start" button to stop?
Re:So I can copy and paste now? (Score:3, Insightful)
Considering that the Start menu is where pretty much all the functionality of Windows can be accessed by the user then, yes, I'd say it was a reasonable assumption. For those who like to play silly word games, the Start menu is where you "start" to do everything. Anyone who has used Windows for even a b
Pfft. (Score:4, Funny)
Not to mention thoroughly freaked out.
Re:Pfft. (Score:4, Funny)
Re:Pfft. (Score:5, Funny)
Last I knew a nipple was, by default, an ouput device
Re:Pfft. (Score:2)
Re:Pfft. (Score:2)
I think most users will find that a little too complex, in the sense of Oedipus.
This won't work (Score:2, Funny)
Re:Pfft. (Score:5, Funny)
"What do you mean you don't know how? A 2 year old could do that!"
Re:Pfft. (Score:2)
Would that make Douglas Adams the inventor of the ternary operator?
Re:Pfft. (Score:2)
Re:Actually probrably NOT a troll (Score:2, Insightful)
That expert never heard of lactation consultants [ilca.org].
Developers get to play too (Score:5, Insightful)
Finally an excuse for even the most die-hard "oh no, I don't play games" programmer to go and get a decent graphics card, and not to use a Matrox G500 because it does 2 screens best
Simon
Re:Developers get to play too (Score:2)
So you're saying the Matrox G500 is NOT a decent graphics card? For a dual-head system, it's STILL a damned decent video card. What Keith is talking about is video memory, not 3D video performance. A normal low-end 2D card with 64/128Meg memory is sufficient. No need to spend hundreds of dollars for cards requiring multiple heatsinks and a dedicated PSU power connector.
Re:Developers get to play too (Score:3, Interesting)
The big fast 3D-accelerated cards tend to come with a lot of RAM on-board. This could be used by a tech-savvy developer to justify a new graphics card to a not-so-savvy manager, and incidentally a new monitor too, a digital flatscreen one, to plug into the new graphics card, so I can still have 2 screens...
Re:Developers get to play too (Score:2)
Don't forget the users! (Score:5, Insightful)
Try more like... (Score:5, Insightful)
a) It came with their computer
b) It's "free" since it came with their computer
c) They don't know anything else
d) They are industry standards
e) They're the same as at work (familiarity)
f) They've had basic Windows training at work
g) Your poweruser friends likely know more Windows
h) It runs off-the-shelf software
i) It's inherently badly designed security-wise (security vs usability)
Pick any of the above, and I swear it's more of a reason than "easy to use". I bet 99%+ have never tried using a preinstalled, well configured Linux system (like the Windows install that came on their PC) at all. Without knowing the alternative, they have no basis to know that Windows is easier - they just assume so.
Kjella
We're not just talking Windows (Score:2)
I'm no Microsoft fan but you have to admit they know how to design pretty good interfaces on the whole.
Re:We're not just talking Windows (Score:2)
cu,
lispy
Re:We're not just talking Windows (Score:2)
Both word perfect and wordstar were also very late in moving to Windows, in fact I don't recall wordstar even making it.
Two fairly horrible to use pieces of sofware, certainly very hard to adapt to foreign languages to
Re:We're not just talking Windows (Score:2)
Re:We're not just talking Windows (Score:3, Interesting)
And do you know who made Word a decent-looking program?
Apple
The first GUI version of Microsoft Word was developed according to Macintosh user interface guidelines. After seeing how well that worked, Microsoft ported it to the IBM-compatible platform.
Re:We're not just talking Windows (Score:3, Informative)
Wow! People are moderating this down. It's as if they don't know. Maybe those of you who can't remember the 80s are ignorant of this, so I'll spell it out for the youngsters:
Re:Don't forget the users! (Score:5, Insightful)
A person once told me the best reason I've heard that people use windows:
Everybody uses windows because everybody uses windows
If Everybody used any other OS (OSX, Linux, FreeBSD, BeOS, Amiga, etc) for gaming, productivity, media, etc. Then EVERYBODY else would use the same operating system to maintain compatablitiy.
I have yet to hear a casual user say that they love windows.
The honest fact is that 90% of people don't care what OS they use, as long as they can listen to MP3s, play games (in my opinion, a MAJOR obsticle that desktop *NIX has to overcome... I was excited that I could get unreal tournament to run on my gentoo box), and open office (open/star/MS/whatever) documents.
The current state of *nix desktops is wonderful! KDE 3.x is definatly professional grade. XFCE4 is definatly ready for the desktop. Fluxbox is there for people that want the best performance with the smallist footprint. I dare ANYBODY to name something that can be done on a Windows based workgroup that can't be done on a *nix workgroup.
I'm sorry, but the ONLY area that linux is truely lacking is in the gaming department. This includes Graphics acceleration. I don't care if the drivers are closed-source (such as the nvidia drivers, which I must admit, are awesome), or open (the DRI for the ati cards isn't as good, but it's still not bad at all).
I'm willing to bet that if a company like loki got into the market now, with some big name titles, then the ammount of linux desktops would skyrocket. Sadly, the only precident of a comany like this is loki, which dipped it's feet in the water way too soon. Linux wasn't ready then. It is now.
As proof of this, I have at least 3 friends (granted, they are somewhat more computer literate than the 'average joe') that want me to install *NIX on their desktop. A year ago, there is NO way that they would have even THOUGHT about dual-booting.
I just don't believe that anyone can get away with saying that *NIX isn't ready for the desktop anymore.
Re:Don't forget the users! (Score:5, Insightful)
The bottom line is, your time is MUCH more valuable than the cost of a windows license.
Re:Don't forget the users! (Score:2)
Yes... duh... And why is it easy to get working on commodity hardware? Acidtripp101 just told you:
"because everybody uses windows"
It's the reason behind your reason.
Re:Don't forget the users! (Score:2, Insightful)
If you can't take the time to get to know your computer, and to get it the way you like it, you shouldn't be using a computer. If you don't want to learn how to use the internet, want to see which browser you like best, want to learn how not to get viruses or ads or shit like that, get off the internet, because it's as sure as shit is shit that you don't fully understand what a computer is.
A computer is a *tool*, and a way to access pretty much anything you
Re:Don't forget the users! (Score:2)
I am not counting download times, and your mileage may vary, but this it what a typical Linux install looks like for me (I have Linux-friendly hardware, so "getting it all working" is an unnecessary step, except for my quake3 and DVD/DivX addiction, which pretty much requires NVidia's drivers)
Install of RH9 including post-config: 35mins
Installing apt for RH: 5mins
Installing security-updates through apt: 5mins
Installing NVidia drivers: 10
Re:Don't forget the users! (Score:5, Interesting)
What's needed is not just the involvement of HCI people, but a commitment to accept the methods they bring to the table, and the results they produce. For example, if it's proven that a system like Mozilla's "Edit Ciphers" confuses more than helps, the project's drivers must be willing to listen, and get its code out of the main builds. If not, the HCI people can put as much time as they want into a product, only to burn out.
Re:Don't forget the users! (Score:5, Insightful)
Re:Don't forget the users! (Score:2)
Not everyone has good colour vision, not everyone is good with double clicking and so on..
Shortcuts should always be well thought out, experienced used should be considered as they can improve their productivity vastly with good shortcut
Re:Don't forget the users! (Score:5, Insightful)
Find them easy to use? Have you ever met someone who's tried MacOS, tried KDE, tried Gnome, tried Windows, and then concluded that Windows was easiest to use, went out and bought a copy?
No? Isn't it more likely that home users were forced to use Windows just as the office users?
If they did truly choose, you could imagine people going into the computer shop and hearing"this is the computer running WindowsXP, this is the same computer but running Windows98, and this is the same computer but running Gnome, which would you like to buy"
Most of the computer shops I've been to say "this is the computer, and YOU WILL buy WindowsXP, because otherwise we won't sell you the computer". Say what you like about building your own systems, or going to an Apple shop, but in most cases, somebody buying a computer is forced to use Windows.
Usability doesn't come into it. Full-page adverts in newspapers and consumer magazines, television adverts, and yes, illegal monopolistic action against suppliers who stock alternatives, is what makes people 'choose' Windows. None of these people do so because they've decided it's easy to use, quite the opposite, many people spend their lives cursing the difficulty of using Windows.
Re:Don't forget the users! (Score:2)
I've always been stunned by HCI-oriented UI designers who say things like "I don't care what color it is" or "just fill in this wireframe" to visual designers.
Usability testing is a Good Thing but it frequently takes place too late to fix any of the fundamental problems of the product.
I recommend Alan Cooper's
Re:Don't forget the users! (Score:2)
Re:Don't forget the users! (Score:2)
I tend to think it's because it comes pre-installed on everything. Windows is the dominant OS, that's true, but it's not necessarily by choice.
Re:Don't forget the users! (Score:2)
Re:Don't forget the users! (Score:5, Insightful)
Re:Don't forget the users! (Score:2)
Why focus primarily on Windows? sure it's a large chunk of their market but Office is one of their best products if you can forgive Clippy.
Naming too complex (Score:5, Funny)
I don't know if GTK or KDE are too complex but these names sure are:
Rayiner Hashem, Havoc Pennington, Eugenia Loli-QueruWhat ever happen to Dick and Jane?
Re:Naming too complex (Score:5, Funny)
Re:Naming too complex (Score:2)
What ever happen to Dick and Jane?
The world is both a lot bigger and a lot smaller since Dick and Jane were born.
Nove Hrady (Score:2)
Re:Nove Hrady (Score:2)
CB
Re:Naming too complex (Score:2)
What ever happen to Dick and Jane?
Oh crap! We let America hear about this 'rest of the world' thing. To the bunkers!
Lets shorten things a little.. (Score:5, Funny)
Linux fanboy: "When will the Longhorn fake-commandline-console look and behave like bash and therefore be ready for serious work?"
Re:Lets shorten things a little.. (Score:2, Insightful)
Hmmmm, doesn't this [xpde.com] count for something?
Re:Lets shorten things a little.. (Score:2)
Re:Lets shorten things a little.. (Score:2)
Cygwin [cygwin.com]
Implication (Score:4, Insightful)
You know what that means then....? (Score:5, Funny)
OK, that's it then. XFree86 is dying.
Loadsastuff (Score:2)
GNOME _still_ isn't integrated (Score:3, Interesting)
Most of a 'desktop environment' important details are underneath, not the pretty GUI. ( though the importance of having a CONSISTANT GUI shouldn't be dismissed. )
They should have had mechanisms in place from DAY ONE for shared information and intercommunications.. not something that was seemingly tacked-on later.. Integration of the desktop must be done on the fonctionnality level, not on the software level.
KDE is much closer to this, as they PLANNED ahead, and didn't just wing-it since it was 'pretty'. See here [kdedevelopers.org] for example.
The problem with GNOME is that they use GTK+ object-oriented style, but don't borrow the most important aspect of (early, anyhow) GTK... cleanliness and simplicity! Without that, the GTK-inspired GNOME macro, er object, system is COMPLETELY INCOHERENT and to put it completely blunt: SHIT.
Not to mention the fact that the numerous API libraries do not work well together and stability will _never_ be achieved since one package will _always_ depend on something that is considered beta or unstable.
Don't even get me started on the various ad-hoc configuration mechanisms and the nightmare that is CORBA and Bonobo.
Sorry to sound harsh, but it was a complaint of mine from day one of GNOME, it just wasn't professional.. They worried more about a smelly foot in the menu then making it solid and consistent.. Now they are finding out the price to be paid if they want to stick around and be more then a cute plaything...
But I'm not really sure what to think of it, honestly. That they'd have to involve money to have things that SHOULD be simple get done.
Re:GNOME _still_ isn't integrated (Score:4, Insightful)
KDE is so many worlds ahead of Gnome in terms of sensible technology that bringing it together and eventually utilizing Gnome-like human interface guidelines will really be a breeze when all is said and done.
Re:GNOME _still_ isn't integrated (Score:2)
Re:GNOME _still_ isn't integrated (Score:2)
I understand this is an unfair comparison, because RhythmBox is general
Re:GNOME _still_ isn't integrated (Score:4, Insightful)
I really don't like how even when it's not replacing a C, it's affixed to the beginning of the application name, as well. KDevelop, KWrite, KPaint, KWord, KSpread, et cetera. Just stop. You think this environment will be taken seriously by corporations while the applications all have ridiculous names? Give me Pan, Totem, Epiphany and Evolution anyday over that crap.
Re:GNOME _still_ isn't integrated (Score:2)
Re:GNOME _still_ isn't integrated (Score:2)
Sorry, but I am not running any cutting edge stuff such as a preemptive kernel or such. I use a stock 2.4 Slackware Kernel (not even recompiled as he time of writing), the terrible NVIDIA Drivers and Dropline-Gnome on Slack9.1.
My machine is a plain Athlon 1200 without overlocking and a measly 256MB SDRAM.
To tell you the truth: My machine is responsive as hell.
I am forced to use Win2k at work with a 2Ghz P4 and much more Ram and my box at home outper
'Nuff Said Already (Score:5, Funny)
But maybe I'm wrong. Maybe it will be:
FreeDesktop.org dreams about a better future (code release TBD)
FreeDesktop.org builds a better X (code release TBD)
FreeDesktop.org builds a better desktop (code release TBA)
FreeDesktop.org builds a better menu (code release TBD)
Uhhh... (Score:4, Funny)
Am I on the right website?
CB
An umbrella project for standards (Score:5, Insightful)
becoming an "umbrella" project for
all projects that require communication
I think this hits the nail on the head--
developers *do* need an umbrella here,
one group to push apps toward one goal.
Simple examples are needing copy and paste,
drag and drop, and consistent mime types,
all so apps can coordinate data content.
Havoc points this out, and I hope his team
can push hard for these kinds of consistency.
Cheers, Joel
UI environment becoming interdependent. (Score:3, Interesting)
My predication is that we will be spending the next 15 years reconciling this fundamental misstep.
Re:UI environment becoming interdependent. (Score:2)
But the KDE and Gnome developers are unifying in many ways. For example, the KDE folks are adopting the Gnome accessibility framework for Qt/KDE 4, and both sides are working on resolving the interoperability problems.
Re:UI environment becoming interdependent. (Score:2)
cu,
Lispy
GUI toolkit libraries (Score:2, Insightful)
Re:GUI toolkit libraries (Score:5, Interesting)
Bzzzt, wrong. Whether something is held in memory or not effects startup time more than responsiveness. The Win32 widget toolkit renders ridiculously fast because:
a) It's primitive and crude. For instance, it has NO layout management at all. Supporting internationalization is a pain in the arse. It uses UTF-16 rather than the somewhat more convenient (but more CPU intensive) UTF-8. Typically Windows desktops are not fully anti-aliased (yes yes, cleartype, not on by default) and when it is, Windows has better HW accel anyway.
b) Microsoft have a lot of people working on performance issues, and entire teams dedicated to optimization. We don't.
Only one GUI library would need to be loaded and everyone could use their favorite. It would certainly help for Windows ports as well. Thoughts?
No offence, but I think that's a bad idea. The thing to understand here is that wxWindows is a toolkit abstraction, and when you abstract things the differences between the underlying implementations are at the same time blurred but they also leak out. A wxWindows app doesn't feel integrated anywhere, and it struggles to hide the underlying differences between the real widget toolkits. Subtle details like focus semantics can break and cause wierd bugs in applications.
When you abstract something, you lose something. Unfortunately the quirks of history have meant we have lots of widget toolkits sitting on our desktop today. The real killer issues from this are integration, consistency and interoperability. Memory overhead is certainly not a big issue compared to these lot - I think you should perhaps do some profiling of applications and then you'd see that having 3/4 toolkits loaded at once is not the real problem, it's the performance quirks of those toolkits that are the issue.
Re:GUI toolkit libraries (Score:2)
Re:GUI toolkit libraries (Score:2)
Frankly, I just think that a lot of you like to bicker about stupid stuff that doesn't really matter. Besides... Like you are one to complain if you aren't coding anything.
If you are running KDE apps on GNOME, it will of course take longer, because as you mention - it needs to load the QT and KDE libraries to interpret the program. If all of our desktops utilized a
Re:GUI toolkit libraries (Score:2)
>>>>>>>>>>
If its unacceptable for KDE and GNOME, then its unacceptable for Windows too. Do you think the multiple toolkits on Windows (classic,
Re:GUI toolkit libraries (Score:2)
No, that's wrong. I've already posted analyses of why Word starts so much faster than OpenOffice, use Google power. If people want I can do so again, but Word is not preloaded. End of story.
If I run KWord from Gnome, it takes about over 10 seconds for the KDE backend theme/DB libraries and QT toolkit libraries to load and all the widgets to be arranged properly
This is entirely a problem w
Re:GUI toolkit libraries (Score:4, Informative)
Basically:
* OpenOffice really (ab)uses shared libraries heavily. It has over a hundred of them, all internal. Worse they are all C++ so there are lots of symbols. On a typical OpenOffice Writer startup, over 1.7 million string comparisons are performed in the dynamic linker alone.
* MS Word has been heavily optimized so that the minimum number of page faults necessary are used to get the user to the first screen. This involves some clever analysis tools, support from the toolchain etc - MS Visual C++ produces very compact and tight code, so fewer disk accesses are needed for the same amount of code. Modern application startup time is mostly a matter of disk IO once other factors (such as synchronous waits on servers starting up) have been removed.
* OpenOffice drags in an entire framework and object model, whereas MS Office reuses at least COM and the registry (though not the widget toolkit to some extent). Dragging the entire VCL and SAL into memory takes time.
* Microsofts employees have the issues related to startup time drummed into them, free software developers do not. They understand techniques like rearranging the layout of your code so commonly used objects and functions are grouped together, how to optimize the CPU working set and so on.
For OpenOffice the biggest issue is still fixup time. Red Hat and Ximian are looking into that, there are techniques you can use (symbol hiding in particular) that can speed up the time taken to load large C++ shared libraries like that. Prelink will also help.
Re:GUI toolkit libraries (Score:2, Interesting)
Re:GUI toolkit libraries (Score:2)
Do you realise how bigoted that sounds? Can you really back it up with concrete API examples? Can you seriously defend that point of view?
Re:GUI toolkit libraries (Score:2)
cu,
Lispy
Re:GUI toolkit libraries (Score:3, Insightful)
Personally I feel the principal reason for many of the problems with a lot of
Re:GUI toolkit libraries (Score:2)
I run OpenOffice Ximian, so it's based on the GTK toolset. It actually starts up pretty fast (9 seconds). Microsoft Word (XP) actually grinds to the computer to a halt when launching. I didn't have these problems with Word97, but maybe it's just me...
There
Plead (rant?) for (Score:5, Interesting)
Give me a site with polls and commented stories! I think as a group we've at least got some interesting rants and I'd love for some of that feedback to be collected in some type of organised manner. Just imagine the flame wars!
Re:Plead (rant?) for (Score:2)
We already have that; now we need to convince the rest of the Linux world that Slashdot is the end-all and be-all of Linux commentary.
Unfortunately, the next KDE version will ship with the goatse guy as the default wallpaper, but, you win some, you lose some...
Re:Plead (rant?) for (Score:2)
Yes.. (Score:2)
Thanks for the feedback.
Please, please, please don't loose X's best aspect (Score:5, Interesting)
My greatest fear is that network transpancy will be lost because because everybody just wants to make X render faster on local hardware. Network transparency is what made X really great in the first place; without that, any replacement is totally worthless to me.
The second thing that made traditional X great was that it did not confuse its primary job as a graphical interpreter as being the window manager and middle ware. Each piece should separate, distinct, and intermatchable just like the ISO networking layers. Otherwise jobs will become so intertangled that the stack will no longer be cleanly configurable outside of a heterogenous stack of software. This is much like the situation with GNOME and KDE vs everything else is now -- great within them selves but not operable between them. The X server has a particular job to do and its new features should not try to take over what should be down by other parts of the stack
Don't just throw out the X Resource Database. Before QT and GTK came along breaking all of X tradition, the XRD was a great tool for configuring everything to behave they way that you want it to. Since these rouge widget sets have entered the scene, a vast majority of people have forgotten about what great tools these once were. I am not totally blind that XRD could use some modification but be sure to keep it in the spirit in which these tools were originally created (idea -- maybe using a structure built on an external DB like MySQL wouldn't be out of the question.)
X may be a very old technology like the first poster stated. Like unix tradition many things were very well thought out when it was created. All to often people are throwing away years of hard thought unix design for the latest fad with not even the faintest thought as to what they might be throwing away. No unix does not walk and talk just like the newer fancer interfaces of today -- there are good reasons for this. Some of these new wiper snappers are turning about and starting to do things the old fashion way because they found out that they were not so bad in the first place. Many of the things which at first seem archaic are actually built on much better paradigms then the newest fads. Advances in technology should be made in consideration of what was done before them. They should extend and enhance what has been done. They should not just throw everything out the window calling it old.
There are many things that need to be revamp in a new X server but please keep the good things in along with all of the improvements.
Finally a real tech article and not opinion fluff (Score:4, Insightful)
DND functionality and file types (Score:5, Insightful)
Isn't this what the IANA media types registry is for? (http://www.iana.org/assignments/media-types/inde
Re:one new goal (Score:5, Interesting)
Re:one new goal (Score:2)
However, if you mean the uderlying performance, then ignore my comment, because I cannot honestly pass judgement on that.
Re:one new goal (Score:2)
Re:one new goal (Score:2)
Re:one new goal (Score:3, Interesting)
- DirectDraw is more complicated than SDL for simple things. Let's go through how to make a double-buffered surface that you can directly draw to.
In SDL:
- Call the SDL init function
- Set the video mode
- Lock the primary surface and draw!
In DirectDraw:
- Create the DirectDraw COM o
Re:one new goal (Score:3, Interesting)
What does clone() do? It creates a new thread, which is not obvious at all.
connect() connects a socket, which isn't too bad a name. But the problem is the name gives no indication of what you're connecting. You'd only know you're connecting a socket and not say a pipe by looking it up.
This becomes a problem when you're trying to learn how to do something new. You can't easily figure out what functions you need to do a t
Re:one new goal (Score:2)
Re:one new goal (Score:2)
1) Short names are easier to type. And when you have less than 200 functions in the API, its so easy to remember what each function does that the shortness is a net win. POSIX-style names would be annoying if POSIX had thousands of API calls like Win32, but it doesn't, so its not.
2) POSIX functions are incredibly generic. Take open(). What does it open? Everything! From a socket, to a hardware device, to a file, it doesn't matter. Or take mmap(). What does it map? Ag
Re:Opportunity? (Score:2)
a) whatever the toolkit, they end up using the same rendering engine and style on an Xserver with that extension
b) more sophisticated applications operate much smoother over the network. RDP, for example, exposes more useful primitives and really really flies as a result. The architecture isn't a