Linked by Thom Holwerda on Mon 20th Sep 2010 20:13 UTC, submitted by diegocg
Qt Jesse Barnes has posted a screenshot showing two clocks implemented in Qt, drawn natively in Wayland, the next-generation display server.
Thread beginning with comment 441957
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Comment by kaiwai
by mtzmtulivu on Tue 21st Sep 2010 17:39 UTC in reply to "RE[2]: Comment by kaiwai"
mtzmtulivu
Member since:
2006-11-14

i read your post, couple of times and your post was a bit fuzzy on where things sit on a stack and i think i did a service to a reader who doesnt know where things sit by specifically mentioning them and where they sit on a stack.

This is a technical forum and use of appropriate technical terms should be advised where ever applicable. We all know or should know what a *nix OS is, we all know or should know where desktop environments exist in *nix systems and we all know or should what toolkits those desktop environments use. To be of service to those who are new and dont know, why not being specific to what pieces we are talking about and where they sit on a system stack?

Being fuzzy on our terms will only cause confusion to those who are in the know and will prolong the ignorance of those who want to know.

Reply Parent Score: 2

RE[4]: Comment by kaiwai
by Bill Shooter of Bul on Tue 21st Sep 2010 18:25 in reply to "RE[3]: Comment by kaiwai"
Bill Shooter of Bul Member since:
2006-07-14

I figured a direct reply would be more helpful than a moderation.

There was absolutely nothing ambiguous about kaiwai's post. Stop trying to defend yourself as an educator to the masses. You misinterpreted his first post and blew it up as if it were a life or death issue. Its not. No one was misled.

Although If you really feel strongly about the education of the masses, feel free to write a very comprehensive article about the different functions of an operating system ( with selected source code / flow charted examples from various system designs) as well as all of the layers on top that create a user interface. I'm certain such an article would be very welcome here.

Reply Parent Score: 3

RE[5]: Comment by kaiwai
by Tuishimi on Tue 21st Sep 2010 21:39 in reply to "RE[4]: Comment by kaiwai"
Tuishimi Member since:
2005-07-06

You mean like kaiwai saying xorg when he meant xserver? People sometimes confuse the underlying framework/api with the components that sit on top of it.

Reply Parent Score: 2

RE[4]: Comment by kaiwai
by kaiwai on Wed 22nd Sep 2010 01:50 in reply to "RE[3]: Comment by kaiwai"
kaiwai Member since:
2005-07-06

i read your post, couple of times and your post was a bit fuzzy on where things sit on a stack and i think i did a service to a reader who doesnt know where things sit by specifically mentioning them and where they sit on a stack.

This is a technical forum and use of appropriate technical terms should be advised where ever applicable. We all know or should know what a *nix OS is, we all know or should know where desktop environments exist in *nix systems and we all know or should what toolkits those desktop environments use. To be of service to those who are new and dont know, why not being specific to what pieces we are talking about and where they sit on a system stack?

Being fuzzy on our terms will only cause confusion to those who are in the know and will prolong the ignorance of those who want to know.


I agree but when I refer to an 'operating system' I am looking at it from a holistic end users perspective and not zooming down into the nitty gritty of the operating system itself. We can sit around and talk about the technical merits of the low level parts of the operating system but they alone do not dictate how 'good' or 'bad' an operating system. The first thing the end user will see will be the graphic user interface, then they will experience how well the integration is between the user interface and the underlying operating system by how well it can handle automounting a thumb drive and so on.

Xorg provides the layer on which the the desktop resides, to the end user if Xorg fails to provide a good experience then the end user will evaluate that the whole operating system is faulty because of that one component. We have people who do the exact same thing when it comes to Windows - they write it off because of Internet Explorer or because of a dodgy third party driver yet we never see the rush to defence as you've done in the above post - why is that?

The experience at the top leads the end user to come to conclusions about how well the over all operating system functions - they aren't going to sit back and go, "well, XOrg really sucks with the desktop residing on top really being held back but the underlying operating system is really awesome" - it just simply isn't going to happen. If the first impressions are bad then it isn't going to matter how good the low level parts of the operating system are, its evaluated as bad by the end user.

Microsoft did a whole video series at their hardware conference before Windows 7 came out about 'spit and polish' and actually getting third parties to give a crap about how their product performs on Windows. It isn't going to matter if the hardware or software is provided by a third party - if the 'computer isn't doing what I want it' (in layman's terms) then they will come to the conclusion that Windows sucks. The same can be said when evaluating any operating system - end users do not differentiate between the different layers, the different suppliers, the different companies and so forth - if the computer isn't doing what they want then it is the fault of the operating system.

Edited 2010-09-22 01:51 UTC

Reply Parent Score: 3