Slashdot Mirror


GUIs From 1984 to the Present

alewar writes "This nice gallery shows the evolution in the appearance of Mac OS, Microsoft Windows and KDE through the years, from the first version to the last available. Not technical, but still interesting to recall some memories from the good old days."

263 comments

  1. Obligatory disgruntled sarcastic comment by suso · · Score: 4, Insightful

    There is only one thing I like more than desktop screenshot timelines, and that is when image links that are 320x240 pixel size take me to an image that is 400x300 pixels in size when I click on it.

    Oh yeah, and where is the fucking Amiga desktop screenshot assholes?

    1. Re:Obligatory disgruntled sarcastic comment by Anonymous Coward · · Score: 0

      Risc OS screenshots would have showed how far behind Microsoft were too...

    2. Re:Obligatory disgruntled sarcastic comment by Ant+P. · · Score: 2, Interesting

      Anyone else noticed the linked-to "blog" has no other content besides this and is one day old?

    3. Re:Obligatory disgruntled sarcastic comment by Handlarn · · Score: 1

      Yeah, smart job on posting thumbnail-sized pictures. How are you supposed to get anything from those pictures when you can't even see the buttons because there aren't such a thing as 1/10th of a pixel?

    4. Re:Obligatory disgruntled sarcastic comment by crayz · · Score: 1

      And is of course full of Google adwords... probably made a pretty penny getting this link posted

    5. Re:Obligatory disgruntled sarcastic comment by Schraegstrichpunkt · · Score: 1
      Oh yeah, and where is the fucking Amiga desktop screenshot assholes?

      Exactly. Or Xerox?

    6. Re:Obligatory disgruntled sarcastic comment by Dhalka226 · · Score: 3, Insightful

      Did you enjoy it or not?

      I personally couldn't care less why the blog was created, nor do I particularly care if people are posting things just to make money. I judge articles based on whether or not I enjoyed them and that's it.*

      * Acknowledging, of course, that some sites go so overboard with the 500 page articles (composed of 200 total words) filled with ads that even if it might be the greatest article ever I don't read it.

    7. Re:Obligatory disgruntled sarcastic comment by Ant+P. · · Score: 2, Insightful

      Considering there's other sites that cover the same topic, and do it a million times better... no, I didn't.

    8. Re:Obligatory disgruntled sarcastic comment by Yvan256 · · Score: 2, Insightful

      Or even OS/9 (CoCo2/CoCo3), or GEOS (for C64/C128)?

      These kids today... They think personnal computers started with the Macintosh, the IBM PC and.... hum... Linux, which is younger than anything else on the market ATM, AFAIK.

    9. Re:Obligatory disgruntled sarcastic comment by Pharmboy · · Score: 2, Insightful

      But the desktop wasn't Linux (Linux is just the kernel) They showed KDE, which I like, but Gnome is pretty much the default install for most Linux distributions, and does look different. Yes, there are many other Linux desktop's that don't have the mindshare to include, but to be remotely complete, it should have shown Gnome, Amiga, Zerox, to just name a few.

      --
      Tequila: It's not just for breakfast anymore!
    10. Re:Obligatory disgruntled sarcastic comment by iamhassi · · Score: 5, Informative

      "I judge articles based on whether or not I enjoyed them and that's it."

      Yeah... but considering all the guy did was rip every from google images it's a bit disheartening:
      Windows 1.0
      Macintosh System 1
      Macintosh System 3
      Microsoft Windows 2.0

      Or he stole them from Wikipedia: Macintosh System 7

      He didn't even dig far either, he just ripped them from the first page of images that popped up.

      --
      my karma will be here long after I'm gone
    11. Re:Obligatory disgruntled sarcastic comment by ottothecow · · Score: 1
      That is something I noticed when I read them...there was no attempt to have similar shots.

      You get garish picture backgrounds and different suites of applications (or the windows 3.1 pic which isnt the full screen, only the program manager portion). The KDE ones are the worst offenders...they are heavily modded to look one way or another...might as well replace the windows98 one with my litestep desktop that I used at the time.

      --
      Bottles.
    12. Re:Obligatory disgruntled sarcastic comment by morcego · · Score: 1

      Also missing:
      - MWM: the default window manager for plenty of Unix systems
      - CDE: the default window manager for plenty of Unix systems in the end of the 90s, in an attempt at standarization
      - FVWM: the first multiplatform window manager [from what I remember]
      - Enlightenment: which eventually was merged into Gnome
      - OVWM (sic?): anyone who used SunOS remember this one

      Just to name 5 important ones. Well, maybe not Enlightenment, but this one was pretty important for Gnome.

      --
      morcego
    13. Re:Obligatory disgruntled sarcastic comment by Johnny+O · · Score: 1

      OMG - so much more missing. This was totally not enjoyable at all.. I was hoping to see so much more that meant something.

      OS/2? The first and only Object oriented desktop. Nothing has come close...

      SCO's Open Desktop - based on mtif, but I did a lot otdesk scripting which made it the bomb for me back then.

      Not to mention all the others missing that you mentioned. This page was a joke.

    14. Re:Obligatory disgruntled sarcastic comment by Alioth · · Score: 1

      Fvwm was not the first multi-platform WM by far. Both OLWM (Open Look Window Manager) and olvwm (Open Look Virtual Window Manager) from Sun ran on Linux before fvwm was even released. Most of us used to run olvwm prior to 1995.

      And that's not even counting twm (Tom's Window Manager), the first really usable X11 window manager which has always been multi platform (although I don't think twm really counts as a gui - it's more a way of getting lots of X terms up :-))

    15. Re:Obligatory disgruntled sarcastic comment by morcego · · Score: 1

      Fvwm was not the first multi-platform WM by far. Both OLWM (Open Look Window Manager) and olvwm (Open Look Virtual Window Manager) from Sun ran on Linux before fvwm was even released. Most of us used to run olvwm prior to 1995.


      Since I was using FVWM on AIX in 1993, I still think that is older than OLWM.


      And that's not even counting twm (Tom's Window Manager), the first really usable X11 window manager which has always been multi platform (although I don't think twm really counts as a gui - it's more a way of getting lots of X terms up :-))


      That is a good candidate.
      --
      morcego
    16. Re:Obligatory disgruntled sarcastic comment by kkiller · · Score: 1

      GUI Gallery is much better.

  2. Better timeline by zubernerd · · Score: 5, Informative

    Man, must be a slowwwww news day...
    Here is a link to a better timeline:

    http://toastytech.com/guis/guitimeline.html Toasty Tech has some spiffy screenshots of various GUIs.
    Ah, the memories...

    --
    Accentuate the positive, don't waste your mod points on the negative.
    1. Re:Better timeline by alerante · · Score: 5, Informative

      The GUIdebook also has tables showing the progression of specific interface elements (for example, icons).

    2. Re:Better timeline by cheezus_es_lard · · Score: 0

      Slashdotted already. What a travesty. Lots of bored geeks on Sundays, I guess...

    3. Re:Better timeline by Tatsh · · Score: 1

      Mac OS XP
      Arabicness Don't you love Unicode?!
      Arabic Windows XP I bet a lot of people don't know that everything is reversed on right-left XP's, like Arabic. This includes the back and forward button on IE, the back is forward and the forward is back ( back). More Mac OS XP Having a Mac theme, after using OS X for a bit, makes me rely on Windows more. It seriously makes Windows seem more reliable then it is. I really have no serious problems with it, but when you think of how much configuring you can do, and there isn't that much on Mac OS X (in the GUI section), it seems extremely complicated after all.

    4. Re:Better timeline by MadJo · · Score: 1

      too bad of the glaring typo on page 4.. "Lunix"?

    5. Re:Better timeline by Fordiman · · Score: 1

      Um...

      FlyaKiteOSX.

      One package. No configuring needed.

      --
      110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
    6. Re:Better timeline by samkass · · Score: 1

      The ToastyTech one is a little sparse on the mainstream screenshots and heavy on the obscure ones. At the same time, the Room 101 one is almost exclusively focused on the Windows vs. MacOS comparison. (Wow, did pre-Windows 95 really look THAT ugly? It didn't seem quite so bad at the time, although back then Apple clearly had a dramatic GUI lead.)

      --
      E pluribus unum
    7. Re:Better timeline by macostech · · Score: 1

      That's a quite comprehensive one!

    8. Re:Better timeline by ant9821 · · Score: 1

      1983 Microsoft announces their new "Windows" program for the IBM PC but does not release it until 1985. Haha. Even back then MS couldn't release anything on time.

    9. Re:Better timeline by kwerle · · Score: 1

      Wow. Not just a little better - much better.

      Thanks for shaming the editors and supplying something useful.

  3. They missed the most memorable by truckaxle · · Score: 3, Funny

    And just where is the blue screen of death

  4. Well then by Stephen+Tennant · · Score: 0, Troll

    OSX 10.1 looks better than Vista!

    --
    I spend most of my time in bed, darling.
    1. Re:Well then by TheNetAvenger · · Score: 2, Interesting

      OSX 10.1 looks better than Vista!

      I so wish I didn't have an NDA...

      Truly to say that the Graphic Engine in OSX and Vista are the same shows a complete lack of understanding. OSX graphics = WindowsXP with GDI+. The only exception is the Offscreen Bitmap Compose that OSX uses.

      Vista has a full round trip Vector based Composer than does things OSX couldn't dream of like real, from Vector acceleration techniques (round trip) to GPU sharing and GPU RAM virtualization, stuff that has pushed NVidia and ATI to rethink the multi-tasking and Memory aspects of the GPU market. Yet MS is pulling this off with the current generation of Video cards.

      That is why I can run Halo, WoW, SWG, and Half-Life ALL on screen at once and not lose framerates in any of the games. I can even Flip 3D them, and they run in that view without any FPS loss. (See normally, each of these applicaitons would want 'full' access to the GPU and the GPU's RAM.)

      I know it is cool to compare OSX to Vista, but really, we need to get everyone educated, if not, then people with see the technology in OSX as 'good enough' and we won't get Apple to move into the next generation of Video Composers and Rendering.

      When I say that OSX is WindowsXP/GDI+ with only the addition of a Bitmap Composer, I am being serious. OSX has no further graphic abilities than WindowsXP, where Vista has new engine and also a new paradigm for Video Cards and GPUs as well.

    2. Re:Well then by MSFanBoi2 · · Score: 1

      Maybe if you are blind, a bit dumb and not so intelligent.

    3. Re:Well then by Anonymous Coward · · Score: 0
      where Vista has new engine and also a new paradigm for Video Cards and GPUs as well.

      You completely forgot about the most important Vista video-related feature--its baked-in support for Digital Restrictions Management.

      ~~~

    4. Re:Well then by Overly+Critical+Guy · · Score: 5, Informative
      Truly to say that the Graphic Engine in OSX and Vista are the same shows a complete lack of understanding. OSX graphics = WindowsXP with GDI+. The only exception is the Offscreen Bitmap Compose that OSX uses.


      100% wrong. OS X uses a technology called Quartz, which is a totally different world above Windows XP's GDI+. It's vector-based and resolution-independent, and has been since its introduction six years ago. The same instructions used to draw to a printer are used to draw to the screen.

      Vista has a full round trip Vector based Composer than does things OSX couldn't dream of like real, from Vector acceleration techniques (round trip) to GPU sharing and GPU RAM virtualization, stuff that has pushed NVidia and ATI to rethink the multi-tasking and Memory aspects of the GPU market. Yet MS is pulling this off with the current generation of Video cards.


      Quartz is a vector-based layer, and Quartz 2D Extreme in Tiger/Leopard accelerates all GUI drawing operations via the GPU.

      When I say that OSX is WindowsXP/GDI+ with only the addition of a Bitmap Composer, I am being serious.


      No, you're being ignorant. Quartz is not Windows XP/GDI+ with "only the addition of a Bitmap Composer." You seem to know little about the Quartz Compositor layer in OS X.

      OSX has no further graphic abilities than WindowsXP


      Wow, so all those anti-aliased Quartz vector operations I've been doing are available in Windows XP? I can print the contents of any view to a printer automatically like I can with Quartz?

      Please put down the MSDN marketing brochure before posting.
      --
      "Sufferin' succotash."
    5. Re:Well then by iamacat · · Score: 1

      Dude, it's not so much what you have, it's how you use it. Sure, both XP and OSX already have their DirectX and OpenGL respectively. But at the end of the day, even XP start button has jagged edges. With all the thousands of engineers Billy Gates doesn't know how to draw a straight line. As for full-round trip vector based composer - do you mean something like this?

      http://www.apple.com/macosx/leopard/coreanimation. html

    6. Re:Well then by Overly+Critical+Guy · · Score: 1

      Quiet! He's "under NDA," remember? ;-) Just another Microsoft shill who didn't read up on OS X's graphics technologies, past and future.

      --
      "Sufferin' succotash."
    7. Re:Well then by bigbigbison · · Score: 1

      You're under NDA about software that is out as a beta that supposedly 2 million people have downlaoded? That must be some NDA...

      --
      http://www.popularculturegaming.com -- my blog about the culture of videogame players
    8. Re:Well then by westlake · · Score: 1
      You completely forgot about the most important Vista video-related feature--its baked-in support for Digital Restrictions Management.

      DRN is in Vista for two reasons:

      1 Business wants it for documents. Internal controls, legal requirements, whattever.

      2 The major content providers demand it for media. Books, music and video. Your neighbors aren't ahelling out the big bucks for home theater gear to feed the P2P nets. They are buying it to watch the movies.

      No one will be jumping through hoops to get what Dell and Apple can delicer out of the box.

    9. Re:Well then by Anonymous Coward · · Score: 0

      You keep claiming that GDI+ is somehow up to the level of Quartz. This is simply not the case. GDI+ is, from an imaging model point of view, much more like DisplayPostscript (around 1989). GDI+ certainly makes it easier to implement vector subsystems like SVG or Flash, but Quartz easily surpasses it in flexibility and applicability and is much more pervasive in the OS X interface. Quartz uses a device independent imaging model that makes it so the same drawing operations are passed to the screen, to a printer, to a PDF file, etc. Apple is officially adding a scaling factor to take advantage of Quartz's inherent resolution independence. OS X's GUI has simply not taken advantage of that yet, though you can enter Quartz Debug and enable it in Tiger (see here).

      While Vista's imaging model is certainly an exciting improvement over XP's, there's nothing in it that Apple couldn't match with some additions to the Quartz layer in Leopard (and based on the directions they've been heading, that would appear to be the case). For starters will be the enabling of Quartz 2D Extreme by default, which will offload the entire drawing process to the GPU instead of just the compositing layer. This exists in Tiger already but is disabled due to graphics driver bugs.

      Frankly, GDI+ is so slow as to be useless. Any improvement Microsoft offers over the API I loathe will be a good thing. Last I checked, you can't even composite over an OpenGL/DirectX layer.

    10. Re:Well then by jiushao · · Score: 2, Informative

      100% wrong. OS X uses a technology called Quartz, which is a totally different world above Windows XP's GDI+. It's vector-based and resolution-independent, and has been since its introduction six years ago. The same instructions used to draw to a printer are used to draw to the screen.

      This is a nonsensical argument, just GDI+ operations are also resolution-independent, based on vectors (of course, lines and fonts and such are after all vector-based) and does map directly to printers. As it happens, so did the stuff in MacOS 9 and GDI prior to Windows 2000, which makes both sides of the argument quite invalid. These are simply long-known features.

      Quartz is a vector-based layer, and Quartz 2D Extreme in Tiger/Leopard accelerates all GUI drawing operations via the GPU.

      Quartz 2D Extreme is however extremely unrealiable and thus disabled in both.

      No, you're being ignorant. Quartz is not Windows XP/GDI+ with "only the addition of a Bitmap Composer." You seem to know little about the Quartz Compositor layer in OS X.

      Feel free to point out where the difference lies, as far as I can see the composition layer in GDI+ is indeed a pretty straight match to the one in Quartz.

      Wow, so all those anti-aliased Quartz vector operations I've been doing are available in Windows XP? I can print the contents of any view to a printer automatically like I can with Quartz?

      Well, yes and yes.

      In the end the arguments here are simply too simplistic, with a simple checkbox approach to evaluating technology GDI+ indeed does well against Quartz, in reality Quartz is a much more modern and at the same time mature approach. On the other hand it seems equally clear that Vista graphics does leapfrog Quartz, unless Quartz 2D Extreme manages to prove itself in the future (the problem is that there is a bit of a mismatch between GPU functionality and the classic Quartz rendering, whereas the Windows Presentation Foundation have been very much designed with GPU implementation in mind, giving it a bit of an edge).

      Whether this is relevant or not is highly arguable however, Quartz software is extremely speedy, and Quartz Extreme (the compositor part that actually works that is) does offload the most performance-critical step. Microsoft should have some kudos for the great design of the Windows Presentation Foundation, but Apple may actually be better served keeping the small rendering operations in software where it is easy and flexible to maintain the best possible predictable quality of graphics. The performance difference is most likely small in practice.

    11. Re:Well then by andrewman327 · · Score: 1

      I get the feeling that this site has an anti-Microsoft slant and the screenshots reflect this. I also believe that Windows Vista will have limited capabilities that are better then the teasers that we have seen.

      --
      Information wants a fueled airplane waiting at the hangar and no one gets hurt.
    12. Re:Well then by timmyf2371 · · Score: 1

      That is why I can run Halo, WoW, SWG, and Half-Life ALL on screen at once and not lose framerates in any of the games. I can even Flip 3D them, and they run in that view without any FPS loss. (See normally, each of these applicaitons would want 'full' access to the GPU and the GPU's RAM.)

      Very nice. Does Vista also provide you with enough hands and peripherals so you can play them all at the same time?

      --

      Backup not found: (A)bort (R)etry (P)anic
    13. Re:Well then by Anonymous Coward · · Score: 0

      "DRN is in Vista for two reasons"

      Regardless of the reasons. It's still there! I noticed none of the two reason are what users want. An OS made for the "industry" in lieu of the consumer. Sweet! Don't sign me up for a version of that OS. The "industry" can buy it. I'll look for more consumer-friendly OS, thank you.

    14. Re:Well then by miyako · · Score: 5, Funny

      No, actually he's under an NDA from Apple, which is why he couldn't post anything that described how Quartz actually works.

      --
      Famous Last Words: "hmm...wikipedia says it's edible"
    15. Re:Well then by Tim+Browse · · Score: 1

      That is why I can run Halo, WoW, SWG, and Half-Life ALL on screen at once and not lose framerates in any of the games

      Given most people can't run just one of those games without losing framerate at some point, I was wondering why you thought anyone would believe something so made up?

    16. Re:Well then by LinuxIsRetarded · · Score: 0

      I noticed none of the two reason are what users want.

      Oh my gosh! Do you mean that users don't want a technology that prevents them from stealing? I'm shocked!

      It's unfortunate that we need DRM, but there are quite a few dishonest people that simply don't feel convicted to actually purchase media.

    17. Re:Well then by poofyhairguy82 · · Score: 1
      Oh my gosh! Do you mean that users don't want a technology that prevents them from stealing? I'm shocked!

      Or makes it harder too use things they have bought in legal ways (how do I backup my Blue Ray disks like I do my DVDs?- I don't yet because of DRM).

      It's unfortunate that we need DRM, but there are quite a few dishonest people that simply don't feel convicted to actually purchase media.

      I don't need DRM. I intend to avoid the media "products" that require DRM in the hardware and the OS. I can find other ways to entertain myself.....

    18. Re:Well then by LinuxIsRetarded · · Score: 0

      Or makes it harder too use things they have bought in legal ways (how do I backup my Blue Ray disks like I do my DVDs?- I don't yet because of DRM).

      Yes, that is an unfortunate side effect. DRM seems to be necessary, however, due to the ever increasing piracy problem. In a capitalistic society, people produce products to be sold- that's how we live. When people choose to steal said products, those who produce are adversely affected. It's not such an obvious problem for wealthier, more mass-marketed media, but it is a serious problem for less widely distributed and marketed media.

      I don't need DRM. I intend to avoid the media "products" that require DRM in the hardware and the OS. I can find other ways to entertain myself..... And that's the beauty of it- no one is forcing you. The trend seems to be to digitally protect media, though, and you may find yourself running out of unprotected material as time goes on.

      I much rather prefer that people follow the laws (and simple morality) with respect to copyrights than deal with the increased costs and side effects of DRM, but unfortunately many people simply have no conscience when it comes to theft.

    19. Re:Well then by Anonymous Coward · · Score: 0

      OSX is not resolution independant. It will be with Leopard.

      Vista will come out before leopard and will be resolution independant.

    20. Re:Well then by Anonymous Coward · · Score: 0

      Actually OS X has been resolution independent since Tiger:

      http://www.interact-sw.co.uk/iangblog/2005/05/20/t igerresolution

      One page among others explaining how to turn it on.

      Granted it wasn't enabled out of the box but it was there ready for developers to test their applications in preparation for when it was enabled (which now appears to be in Leopard rather than a 10.4.x update).

    21. Re:Well then by spongman · · Score: 1

      err, Windows has had device-independant vector-based rendering (GDI) since version 1.0 (1985)

  5. Interesting, but... by FlipmodePlaya · · Score: 4, Insightful

    A lot of the screenshots show highly customized desktops (look at the KDE 3.5 shot), which makes a comparison difficult. They're also all in low-resoultion JPEG format, which seems an odd choice...

    1. Re:Interesting, but... by Anonymous Coward · · Score: 0

      Perhaps to show some desktops are highly customizable? And others aren't. Yes, that was a snarky way of commenting how far behind the curve the desktops from the world's largest software company are year after year.

    2. Re:Interesting, but... by Anonymous Coward · · Score: 0

      I just posted the above comment and, now having seen this, stand corrected. Surely the likes of this will never be matched again:

      http://toastytech.com/guis/bob.html

    3. Re:Interesting, but... by Anonymous Coward · · Score: 0

      yeah. i lol'd at the KDE entry, lookin like a mascara wearin, anti conformin, angsty goth kid.

    4. Re:Interesting, but... by Ant+P. · · Score: 1

      It's not an odd choice at all. It gets them extra page clicks (read: ad $), as more people will click the entire series of images to try and find a working link.

  6. Some corrections. by Saven+Marek · · Score: 5, Informative

    The picture shown for System 5 is not a Mac system, rather it's a version of the Apple IIGS desktop.

    The picture labelled as System 6 is a version of System 7, not System 6.

    1. Re:Some corrections. by Indras · · Score: 2, Funny

      And the picture for Mac System 7 clearly says "7.5.3" in the screenshot (while 7.5 is supposed to be a couple pictures down).

      --
      The speed of time is one second per second.
  7. Another excellent source for this bit of history by Zzyzygy · · Score: 2, Informative

    Another good site to look at for GUI history is Nathan Whitehorn's "GUI Gallery" here: The GUI Gallery. I like it because Nathan is actively developing it. He actually loads and runs these various environments before writing about them.

    Either that, or that boy has way too much time on his hands :-)

    -Scott
    --
    My other sig is a Glock
  8. Gnome by Heidistein · · Score: 1

    Verry nice gallery to see, look at the difference between MS and apple too see that apple was far further developed earlier... But I miss gnome!! :)

    1. Re:Gnome by Anonymous Coward · · Score: 0

      Yeah, I was going to comment on how GNOME was missing, then I realized they included Microsoft Windows, so all you need to do is add five years to the Windows releases and you have the corresponding GNOME release!

    2. Re:Gnome by Elektroschock · · Score: 0

      I miss Amiga and Geoworks.

    3. Re:Gnome by KillerBob · · Score: 2

      Once you go XFCE, you never go back...

      --
      If you believe everything you read, you'd better not read. - Japanese proverb
    4. Re:Gnome by CarpetShark · · Score: 2, Interesting

      I went back to KDE after about half an hour ;)

    5. Re:Gnome by Anonymous Coward · · Score: 0

      apple was far further developed earlier

      DISCLAIMER: I am NOT a M$ fan boy, but...

      I couldn't help but notice that it appears Windows had color graphics in the GUI before the Mac? Unless this is yet another glaring example of how that GUI history page sucks ass. They didn't include any Gnome (now default Fedora desktop NOT KDE), Windows NT 3/4, or Windows 2000 screen shots! Very incomplete... How ever if that part of the time line is accurate then it looks like Windows beat Mac to the color GUI.

      Screw it, they're all Xerox PARC wannabees any way! ;)

    6. Re:Gnome by mobby_6kl · · Score: 1

      Is that how long it takes to emerge kde on your system?

    7. Re:Gnome by Muramasa · · Score: 1

      Amen to that brother.

  9. that's not Macintosh System 5... by Anonymous Coward · · Score: 0

    It's GS/OS on an Apple IIGS. What a noob. :)

  10. xerox workstation by porky_pig_jr · · Score: 1

    funny, the very first apple GUI looks just like Xerox workstation. Anyone remembers those? With Xerox network protocol (was it XNS?).

    1. Re:xerox workstation by Anonymous Coward · · Score: 0

      XNS was the protocol that IPX/SPX morphed into.

      Ahh the good old days of Netware servers. :) And spyware didn't exist. Yet.

    2. Re:xerox workstation by AnarchoAl · · Score: 1

      But of course- the early Apple interface was a clone of Xerox Lab's prototypes.

      http://en.wikipedia.org/wiki/History_of_Apple_Comp uter#Xerox_PARC_and_the_Lisa

  11. microsoft by Anonymous Coward · · Score: 2, Funny

    The 'O' in the MS logo from 1985 kinda looks like a goatse..

  12. "GUIs"??? by 50000BTU_barbecue · · Score: 4, Insightful

    An inclusive statement like that should include GUIs from the early 60s (SKETCHPAD) through the Englebart demo through Xerox Star, GEOS on the C64, the Amiga Workbench, Atari GEM, etc... Why only show the PC and Mac?

    --
    Mostly random stuff.
    1. Re:"GUIs"??? by dosius · · Score: 1

      And what's more GEM is a PC GUI too, has been since the beginning. Plus it's still under active development (check the desktop build date on this image, for example).

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    2. Re:"GUIs"??? by Anonymous Coward · · Score: 0

      > And what's more GEM is a PC GUI too, has been since the beginning.
      > Plus it's still under active development (check the desktop build date on this image, for example).

      Wow, it looks like the graphic style has been under "active stagnation" for 20 years!

      Yeah baby!!!!

    3. Re:"GUIs"??? by dosius · · Score: 1

      That's not what GEM looked like prior to 1999.

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
    4. Re:"GUIs"??? by Pigeon451 · · Score: 1

      Bitch much? Maybe the author is only familiar with PC and Mac. As the summary states, it is Microsoft, Mac and KDE GUIs over the years. If you want a more thorough look at desktop screenshots over the years, there are other sites...

    5. Re:"GUIs"??? by CrazyJim1 · · Score: 1

      I was all psyched to see a GEOS flashback, but nothin. The funniest thing about GEOS is that it took longer to load GEOS then your program than it did to simply use the LOAD"*",8,1 tactic.

  13. What? No Amiga GUIs? by rubberbando · · Score: 4, Interesting

    It would have been nice to see some pics of the Amiga GUIs, year by year to show how much nicer they were at the time compared to Apple's and Microsoft's.

    --
    DEAD DEAD DEAD DELETE ME
    1. Re:What? No Amiga GUIs? by swillden · · Score: 3, Insightful

      It would have been nice to see some pics of the Amiga GUIs, year by year to show how much nicer they were at the time compared to Apple's and Microsoft's.

      And NeXTstep. The NeXTstep GUI circa 1992 looked a great deal like Mac OS X circa 2001 -- it was amazingly better than its contemporaries.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    2. Re:What? No Amiga GUIs? by Anonymous Coward · · Score: 0

      The Atari STE whupped it's ass anyways....

    3. Re:What? No Amiga GUIs? by eyewhin · · Score: 2, Interesting

      I agree. Amiga blew them all away. Too bad that Commodore so totally sucked at marketing :-( Ironically, the thing that did the Amiga in back then was that people believed it was a gaming computer. Today, the only thing that is keeping MS ahead is the lack of game ports to other OS's. I miss my Amiga.

    4. Re:What? No Amiga GUIs? by misleb · · Score: 2, Interesting

      Did the AmigaOS provide much in the way of APIs and hardware abstraction? I was under the impression that most amiga programs worked directly with the hardware much of the time. That could have been a significant hurdle for general software development.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    5. Re:What? No Amiga GUIs? by LeftOfCentre · · Score: 2, Informative

      Games often did work directly with the hardware, but software did not. The AmigaOS API was extensive -- especially with AmigaOS 2.04 and above which offered a really good standard widget library (gadtools.library), object oriented GUI extensions (BOOPSI) translation services (locale.library), graphics (intuition.library), spoken speech and much, much more. I particularly liked how GUIs would continue working even when apps locked up or crashed (in the sense that windows and widgets could refresh and react when clicked on).

    6. Re:What? No Amiga GUIs? by nickos · · Score: 1

      A lot of games "hit the metal" to take advantage of the amazing custom chips, but if you were writing an application there was a complete API to use. I played with coding using Intuiition (the GUI API) as a kid and was later amazed to find out how badly Win32 compared with it when I had to work with that on a professional basis many years later.

      The Amiga was a brilliant machine which is why it was the home computer of the late 80s/early 90s in Europe, despite Commodore's complete ineptitude. Sigh.

  14. My desktop snapshot collection by digitalhermit · · Score: 5, Funny


    1994:

    > ls -a .profile

    1997:

    ~ ls -a .profile .sh_history

    1998:
    tardis ~ ls -a .profile .sh_history .bash_profile

    2001:
    [kll@apocalypse] ls -a .profile .sh_history .gnurc

    2004:
    [kll@helios] ssh apocalypse hostname
    apocalypse

    2006:
    [kll@xm-fc5-001] ssh localhost
    password:

    Virtual Machine - FC5 - Image 001
    Be nice!

  15. Crap by John+Nowak · · Score: 2

    Small pictures, no captions, HUGE omissions, screenshots of OSes not even out yet... why was this posted again?

    1. Re:Crap by trash+eighty · · Score: 1

      to gain the blog's author a load of ad revenue?

    2. Re:Crap by hesiod · · Score: 1

      Advertisement traffic whoring

    3. Re:Crap by SpectreHiro · · Score: 1

      why was this posted again?

      Happy sunday.

      --
      You can't win, Darth. If you mod me down, I shall become more powerful than you could possibly imagine.
  16. Hard comparison by pembo13 · · Score: 2, Insightful

    when comes to KDE at least. Since with enough effort, KDE can look like any of those. Not a Gnome user myself, but some screenshots of it would have been nice for comparison at least.

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
  17. Not exactly in depth by also-rr · · Score: 3, Insightful
    And a bit odd in it's selections. It shows Vista (not yet released) but it doesn't show Compiz (under KDE), which is here today and puts Linux well over the top in terms of eye candy.

    I might add that there is a distinct lack of console love as well. I demand equal treatment for bash! Show me the ~$

    Before you were born:
    root@localhost:~$

    After you are dead:
    root@localhost:~$
    1. Re:Not exactly in depth by Vo0k · · Score: 1
      Noooo :)

      Before you were born:
      $_

      Now:

      root@localhost:~$_


      All in bright colors, syntax highlighting, autocomplete and autocorrect, and whatnot.

      Sure it "could have been" done before. But only now it is actually in use.
      --
      Anagram("United States of America") == "Dine out, taste a Mac, fries"
    2. Re:Not exactly in depth by ABoerma · · Score: 1

      The root account gets a hash for a prompt where I live. =P

    3. Re:Not exactly in depth by chasingporsches · · Score: 1

      also, the mac os x gui has changed quite a bit with each release between 10.1 and 10.4, moreso than the changes between system 1 and system 2, so 10.2 and 10.3 should be shown as well as 10.0. 10.5 shouldn't be shown, because it isn't guaranteed that that's what the desktop will look like, and neither is it that way for vista.

    4. Re:Not exactly in depth by VGPowerlord · · Score: 1

      I know most people don't log in as root that much, but I would have at least hoped that you'd remember that root's prompt ends with # not $.

      root@localhost:~#

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
  18. DESQview? by Wonko+the+Sane · · Score: 3, Insightful

    They forgot DESQview, the preferred environment for running your BBS software

    1. Re:DESQview? by DerekLyons · · Score: 1
      They forgot DESQview, the preferred environment for running your BBS software

      IIRC DESQview was controlled via the keyboard - while it was a windowing enviroment, it wasn't really a GUI.
    2. Re:DESQview? by misleb · · Score: 1

      Hardly a GUI. All it did was multitask DOS programs. ALthough there was something called DESQview/X. Never used it, personally.

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    3. Re:DESQview? by MikeBabcock · · Score: 1

      GUI != mouse-user-interface, just graphical-user-interface

      I used Desqview/X for several months and quite enjoyed the experience.

      PS, it also worked with a mouse.

      --
      - Michael T. Babcock (Yes, I blog)
    4. Re:DESQview? by DerekLyons · · Score: 1
      GUI != mouse-user-interface, just graphical-user-interface

      DESQview was a windowing system - not a graphical system. Windowing != GUI. (Frameworks used a windowing system in the mid 80's - and nobody would call it a GUI.)
       
       
      I used Desqview/X for several months and quite enjoyed the experience.
       
      PS, it also worked with a mouse.

      DESQview/X != DESQview. The two were considerably different despite sharing a name.
  19. nice, nice, but where is X,, BeOs, Os2 by dindi · · Score: 1

    Would be interesting to see os2, beos, and maybe even pda screens, X (xfree and others) side by side as well :)

    but nice anyway ..

  20. slashdot appearance by Anonymous Coward · · Score: 0

    Where's the timeline for Slashdot appearanced? I've already forgot the previous style.

    1. Re:slashdot appearance by hesiod · · Score: 1

      > Where's the timeline for Slashdot appearanced?

      http://web.archive.org/web/*/http://www.slashdot.o rg

  21. It goes to show you.... by dduardo · · Score: 1

    If you stick a monochrome screen on a modern computer you'll basically have an 80's desktop.

    Question: Why does it feel like everything "new" in software is a rewrite of stuff that has already been done in UNIX?

    1. Re:It goes to show you.... by NineNine · · Score: 1

      Question: Why does it feel like everything "new" in software is a rewrite of stuff that has already been done in UNIX?

      Because it is. Unix did it, but in a way that regular people couldn't figure out. It's still being re-written, except this time, it's being done in a much more useable way. The DVD is a re-write of VHS. The both do the same thing, but DVD does it better. Same thing.

    2. Re:It goes to show you.... by v1z · · Score: 1
      The DVD is a re-write of VHS. The both do the same thing, but DVD does it better. Same thing.

      Not really. VHS was "brilliant" in that it was a cheap, self-degrading, self-protecting distribution medium. DVDs are easier to pirate, and while they do self-destruct during normal use (scratches, anyone), they don't do it nearly as "well" as VHS did.

      Ironically DVD are also worse than (digi)Beta, as a medium for high quality professional use, except for cost.

      VHS "leveraged" all the "benefits" of analog media distribution, while DVDs are specifically (but somewhat poorly) designed to prevent the benefits of digital distribution.

  22. This is always fun by wjcofkc · · Score: 3, Informative
    I really enjoy this sort of stuff, here is an article discussing the history of the GUI from the very begining:

    http://arstechnica.com/articles/paedia/gui.ars

    --
    Brought to you by Carl's Junior.
  23. Re:Why KDE? by Anonymous Coward · · Score: 0

    Desktop Environments vs Window Managers...

  24. It sure does. by FatSean · · Score: 1, Troll

    And Old Navy clothing looks better than Carthart and Dickies.

    --
    Blar.
  25. Error: GS OS is not System 5 by techmuse · · Score: 1

    The web site has a significant error. They present the Mac-like GUI for The Apple II GS as System 5, which it is not.

  26. gnome! by slack_prad · · Score: 1

    where's gnome you insensitive clod ?!!1

    --
    Sent from my desktop computer
  27. What, no DOSSHELL? by srothroc · · Score: 1

    I remember the days when I played the Space Quest and King's Quest series; the days when the hardest part of using a computer for me was remembering the esoteric string of letters that would let me into the mouse-driven directory/file view: DOSSHELL. I mean, as primitive as it might have been, it's still very easy to see in it the precursor of today's Window's Explorer with the Folder Explorer Bar enabled -- especially with 20/20 hindsight.

    It's a bit disappointing not to see it listed there -- I would have thought it an integral part in Microsoft's GUI development. I mean, come on, it even let you change the colors! Primitive theming!

    1. Re:What, no DOSSHELL? by dosius · · Score: 1

      Here you go (from IBM DOS 5.02)

      -uso.

      --
      What you hear in the ear, preach from the rooftop Matthew 10.27b
  28. Re:Another excellent source for this bit of histor by ModernGeek · · Score: 1

    It's Nathan Lineback. You had me questioning my sanity for a moment there.

    --
    Sig: I stole this sig.
  29. Good Enough by DumbSwede · · Score: 3, Insightful

    Maybe it's just me, but the look of GUIs seemed to devolve from the initial Mac 1984 system 1 version, until about 1995. The look just got uglier and more cluttered, and color when it was introduced had no real aesthetic, this was probably due in part to display limitations. In 1995 both Mac and Windows finally arrive at reasonably attractive, colorful, and functional versions. KDE sets the bar a little higher in 1998 then stagnates, Mac catches up with X 10.5 and Windows should catch up with Vista.

    Rail against GUIs if you must, but without some vastly improved display system they have converged a stable solution that will probably stay mostly unchanged much like QWERTY typewriters, not because there isn't anything better possible, but because they are good enough, and are what everyone knows.

    1. Re:Good Enough by Anonymous Coward · · Score: 0
      Rail against GUIs if you must, but without some vastly improved display system they have converged a stable solution that will probably stay mostly unchanged much like QWERTY typewriters, not because there isn't anything better possible, but because they are good enough, and are what everyone knows.

      Just like the TTY?

    2. Re:Good Enough by DumbSwede · · Score: 1

      That would have been covered by the "without some vastly improved display sytstem" qualifier.
      Though it isn't so much the display holding things back now, but the input interfaces.
      Precise, cheap, unencumbering 3D entry that easily tracks all your hand, finger and arm motions, or reliable, speaker independent, speech recognition would bring about a new round of change.

    3. Re:Good Enough by White+Shade · · Score: 1

      I would tend to agree with you..

      It actually seems to me that the macintosh gui remained stagnant and pretty horrifically uninspired for a number of years, whereas windows changed a lot and got to its 95ish style pretty quick.

      things did change pretty quickly though after that; apple completely blew away the competition whereas windows stayed the same for three or four version (95, 98, 2k)... now it seems like vista may have caught up again a bit. hard to say though..

      --
      ìì!
    4. Re:Good Enough by Anonymous Coward · · Score: 0

      That would have been covered by the "without some vastly improved display sytstem" qualifier.

      Surely that's a matter of opinion? I work (as in paid work) almost exclusively using ssh or local console, even in X I still do file management using an xterm.

    5. Re:Good Enough by Morky · · Score: 1

      The 1987 System V screenshot is not a Mac OS, but and Apple ][ GUI.

  30. Re:Why KDE? by Anonymous Coward · · Score: 0

    Desktop enviroments are for wusses Vs I don't use one...

    Why KDE (which is relatively new) over Motif or CDE (which have been around for years)?

  31. Cool by Short+Circuit · · Score: 1
    The Work In Progress window is a kind of task manager that shows which programs are running, which programs have finished running and shows any console output that the program may have generated.


    Am I the only one who things that storing console output would still be a useful feature? It would make batch processing jobs a great deal easier.
  32. Windows ME? by EnsilZah · · Score: 4, Funny

    What, no mention of Windows ME?
    It's almost as if someone doesn't want to acknowledge it ever existed.

    1. Re:Windows ME? by EnsilZah · · Score: 1

      Ah, sorry, just realized anyone capable of capturing a screenshot would not be caught dead running it.

    2. Re:Windows ME? by Eideewt · · Score: 1

      You're assuming that it would run long enough to actually capture a screenshot.

    3. Re:Windows ME? by Anonymous Coward · · Score: 0

      Go away! There aint no Windows ME and there never was.

  33. Oops by Cygfrydd · · Score: 1

    The Mac System 5 screenshoot appears to actually be an Apple IIGS... not System 5 at all. :-(

  34. Apple copies Microsoft.... by GoulDuck · · Score: 4, Funny

    If these screenshots are corret, we now have proff that Apple copied Microsofts idea about using colors!

  35. No GEOS by edmicman · · Score: 1

    Where's GEOS?

  36. Apple and MS implementation by fermion · · Score: 1
    I am sure there will be many MS copied Apple, which in a way is true, and Apple copies others, which is true but is not as most people think, so I want to add this beforehand.

    Having seen and used most of these interfaces, the driving force seems to be the hardware to run them and then an API to make them cheap enough to implement for consumer applications. System 1 was a basic GUI built run on a relatively simple hardware and in a small footprint. The innovation was in fact in the separate GPU, something that was not widely used. This allowed the complex graphics. The big software innovation was WYSIWYG. Despite what people say about Xerox, the concept existed, but the bundle did not. Furthermore, the problem MS had was that it had no control over the hardware, and therefor could a tight OS, much less an OS built with specialized processors that no one had, so MS Windows 1.0 was the best it could do for the given hardware.

    Once the initial concept of the GUI was developed, and the methodology developed, the software itself became rather simple. Over time hardware has been the biggest constraint on MS. MS software must run on cheap hardware, so the OS has been necessarily inferior. For instance, it was 10 years before excel on the PC was as good as the Mac. Conversely, companies like SGI had much more powerful hardware to play with, so the X-Windows experience blew System 7, 8, 9, and everything else, out of the water.

    It is unclear what vista is going to look like. Mac OS X has some incredible high quality hardware at the base, hardware the sells for at least 1K, so apple has fewer constraints that MS that has to run on $300 junk. This might explain the fork in MS Vista. The point is that the comparison between MS and Apple makes as much since as comparing Apple and SGI. No one has ever said that Apple should run like a SGI. Likewise, MS cannot really run an Apple, even if they both use x86. Mac OS is basically being optimized for Intel dual core chips, and how long until the GPC is going be standard dual core?

    Of course, even though Apple is "closed", the documentation and developer tools always seem more open to me. I recall the old Apple MAC bookd and the details, and compare that to the third party MS development books, and all the asterisks warning the user that MS did not support use of the hook or API. It did not make the Mac and easier to develop with, and it still seems easier to throw something together on the PC, but that is only if one is willing to use questionable strategies.

    --
    "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    1. Re:Apple and MS implementation by hesiod · · Score: 1

      > how long until the GPC is going be standard dual core?

      Excuse my ignoramicousness, but what's GPC? Was the G a typo, or does that mean something else?

  37. "Nice" Gallery? by Predictor · · Score: 2, Insightful

    The author of this blurb terms this gallery "nice", and the author of the Web page itself titles it " The Evolution of Desktops". Huh? At best, it is a collection of Windows and Macintosh screenshots. What's missing? The XEROX object-oriented (old sense) GUI, any version of GEM, TopView, X-Windows, Lisa, the Mach interface, the various commercial non-X-Windows UNIX interfaces and whatever the Amiga used.

    1. Re:"Nice" Gallery? by hesiod · · Score: 1

      > whatever the Amiga used

      Oh, like a dagger in the heart! :) Workbench was the graphical part of the Amiga system.

      I too was disappointed by the incompleteness (and inaccuracy) of the page. Oh well...

    2. Re:"Nice" Gallery? by Bambi+Dee · · Score: 1
      Oh, like a dagger in the heart! :) Workbench was the graphical part of the Amiga system.
      Was it? This keeps confusing me. I thought the Amiga GUI was part of the AmigaOS ROMs, as the "Intuition" libraries or whatever they were - with "Workbench" as an optional desktop, comparable perhaps to explorer.exe or the KDE kicker/konqueror combo. After all, you'd always get a full windowing environment even when you booted off an empty floppy/harddisk. And you could quit Workbench, but not the GUI.
    3. Re:"Nice" Gallery? by hesiod · · Score: 1

      Well... OK, yeah, it had a GUI without Workbench, but it had no icons, menus, etc. Pretty much a single window with a command prompt, although you could launch other graphical programs from AmigaDOS (CLI).

  38. Sad state of GUI development by grumbel · · Score: 5, Insightful

    Looking at those 20 year old GUIs always makes me sad, since it shows how basically nothing has changed since then. We got more colors, higher resolutions and a few more mouse buttons, but the basic user interaction is still very much the same as back then and still flawed in many ways. For example no mainstream GUI today manages to properly merge the power of the command line with the ease of use of a mouse driven interface, instead both act side by side, where the most 'integration' you get is lausy copy&paste support of filenames from GUI to CLI, however not the other way around. But thats really just the tip of the iceberg, computer interfaces could do so much more, but most of them don't even try. Don't get me wrong, some transparency, drop shadows and other effects can help, but they are really just polishing of something that is broken at a much deeper level.

    As another drastic example of the lack of GUI progress one can look at this NeXTSTEP presentation from 1992, even today that video still shows plenty of features which a normal Linux or Windows still can't compete with and with MacOSX it doesn't really look that much better, while it is actually based on NeXTSTEP, it has allocated a whole bunch of cruft from old MacOS, which doesn't really make the overall experince all that good.

    1. Re:Sad state of GUI development by ucblockhead · · Score: 2, Funny

      You're so right! You want to know what else pisses me off? Cars. Cars still use the dated "Steering wheel/Accelerator/Brake" paradigm. Where's the originality!?

      --
      The cake is a pie
    2. Re:Sad state of GUI development by grumbel · · Score: 1
      You're so right! You want to know what else pisses me off? Cars. Cars still use the dated "Steering wheel/Accelerator/Brake" paradigm.

      There are actually some experimental cars with joysticks and a autopilot for cars is also already quite doable, at least on some roads.

      The throuble with GUIs is however very different, the reason why GUIs need improvements isn't because of originality, but because they simply don't work the way they are now. There are tons of tasks that you can do very easily CLI, but not at all via GUI, even so all the functionality is available in the GUI. Simple example would be batch conversion of images, in command line its simply, I have a tool to do the conversion and bash has looping constructs, I combine both and job is done. On the GUI side I have Gimp and no looping constructs, end of story, I have to click myself a thousand times through the load/save dialogs to get the job done.

      The solution that todays GUI application offer is that each application that might be used in batch jobs comes with their very own tools to do a batch job, very non-generic, very inflexible and many application simply don't come with one to begin with. Chaining multiple batch jobs together is also impossible when that job would cross application boundaries. Why can't I simply use the file dialog, mark the files and apply the actions from there? It would be simple, easy to use and very powerfull, it however would require applications to actually export their functionality and that is something that many applications simply don't even try and the OSs don't really help them accomplishing that either, so everything stays monolitic, interaction between applications in GUI is almost non existant.

      CLI on the other side is build on the very principle that one tool should do one job and do that well, complete oposite of todays GUI, where one tool tries to reimplement half an OS. The flexibility and ease of use arrises from the reuse of the same tools for different jobs. A 'sort' programm can sort whatever I feed into it, 'gawk' gives me access to data organised in columns and so on. Now CLIs are far from perfect, unstructured text data is good for some things, but completly unsuitable for others, complete lack of graphics doesn't make it very easy to do a lot of things, mouse support is primitive or non-existant, learning it is much harder then necessary and launching a new process for each command can waste a lot of resources and many other problems, but thats kind of the point. CLIs aren't perfect, but neither are GUIs, both however provide many of concept that are very good and successfull and there is nothing that would stop you from combining the power of the two to get something far better then what we have now.

    3. Re:Sad state of GUI development by flooey · · Score: 1

      where the most 'integration' you get is lausy copy&paste support of filenames from GUI to CLI, however not the other way around.

      In some cases it's better than that. In Mac OS X, for instance, if you drag a file from the Finder to a Terminal window, it inserts the filename of that file on the command line, and if you select an absolute filename in the Terminal and drag it to an application in the Dock, it tries to open that file in that application. If you select some text in the Terminal and drag it to TextEdit, it will create a new untitled file with that text in it. If you select some text in the Terminal and drag it to a Finder window, it creates a text clipping there with that text in it.

      It's not great (for instance, dragging just the a filename from an ls to an application won't work, because it doesn't know what directory it's in), but it's better than just copy and paste.

    4. Re:Sad state of GUI development by eldepeche · · Score: 1

      Apple's Automator software tries to do this. For programs that support it and provide actions, you can pick a group of files and apply actions in order. I haven't used it much since most 3rd-party applications haven't implemented it enough to make it useful.

    5. Re:Sad state of GUI development by tippy2k · · Score: 1

      I can't believe I have never seen or heard of NeXTSTEP before today. That is an enviornment that would be very useful to me right now 14 years later. Based on the feature set it provides out of the box, I would argue that was the most powerful and productive interface available at the time. No wonder Jobs left Apple to pursue his own OS and animation software/studio.

    6. Re:Sad state of GUI development by starseeker · · Score: 1

      You probably want something like the environment provided by the old LISP machines, but with better graphics. The McCLIM Listener is a hint of what might be accomplished, but the problem with environments like that is all the legacy software that exists today and does essential work. There is simply no way old software can be simply migrated to a new environment with a radically different paradigm without substantial work - the fundamental design decisions make it difficult.

      --
      "I object to doing things that computers can do." -- Olin Shivers, lispers.org
    7. Re:Sad state of GUI development by intrico · · Score: 1

      I believe this is logical and to-be-expected when you look at the fact that a lot of these companies have built their multi-billion dollar businesses around the majority of these operating systems, and companies at that level generally do not like to take risks. One thing that defines "usability" of software is how easily people are able to pick it up without a learning curve. Keeping things the same ( a "tried & true" formula) is one way to ensure that the mass market of non-power users (the ones who usually provide the bulk of revenue $$$) will be comfortable with the software on their dektops. It's human nature to be comfortable with things that they are "used to", and to reject things that they are not comfortable with, even if the new "awkward feature" or "awkward interface" has proven to be a vast improvement over what it replaced.

    8. Re:Sad state of GUI development by maynard · · Score: 1

      Then go buy yourself a mac. It's essentially the same system today as it was seventeen odd years back - warts (need I say netinfo) and all...

    9. Re:Sad state of GUI development by master_p · · Score: 1

      That's exactly what I indented to post!

      Besides agreeing with you 100%, I would also like to point out that GUIs also have not become easier for the programmers. GUI programming is almost the same as it was 20 years ago. No one has come up with a GUI programming model that actually makes sense. Programming a GUI-driven app is sill very difficult.

    10. Re:Sad state of GUI development by Blakey+Rat · · Score: 1

      Uh, visual programming languages didn't exist 20 years ago. Visual Basic, Real Basic, Objective-C/Cocoa have changed GUI programming a LOT. In fact, I'm kind of curious what the heck you're talking about.

    11. Re:Sad state of GUI development by master_p · · Score: 1

      Obviously you do not have enough experience with GUI programming.

      The visual IDEs are only for the trivial GUI cases. In order to do anything advanced, you have to manually program the GUI.

      And there is no 'standard' algorithms for geometry management, window updating etc as they are in other domains.

      And of course there is no quality distributed GUI that works over WANs, forcing us to use HTML.

    12. Re:Sad state of GUI development by Blakey+Rat · · Score: 1

      Your last point is valid, but:

      The visual IDEs are only for the trivial GUI cases. In order to do anything advanced, you have to manually program the GUI.

      I call BS. What "advanced" thing are you trying to do that visual development environments won't handle? Cite a specific example, please.

      And there is no 'standard' algorithms for geometry management, window updating etc as they are in other domains.

      What "standard" algorithm are you looking for? I don't even know what "geometry management" means, really.

    13. Re:Sad state of GUI development by Tab+is+on+Slashdot · · Score: 1

      Man, NeXT really was way ahead of the game. It's a shame it was marketed almost exclusively for research and business -- think of how much nicer the personal computing landscape would be today if we had all been running NeXTSTEP instead of Windows throughout the nineties.

    14. Re:Sad state of GUI development by master_p · · Score: 1

      "I call BS. What "advanced" thing are you trying to do that visual development environments won't handle? Cite a specific example, please."

      many examples:

      1) internationalization.
      2) the model-view pattern.
      3) worker threads that affect the GUI.
      4) custom file dialogs.
      5) data-driven guis (beyond DB, that is).

      "What "standard" algorithm are you looking for? I don't even know what "geometry management" means, really."

      It shows.

      Geometry management is the process of automating the positioning of user-interface elements according to their contents. Each GUI library has its own way to manage geometry, but they are all different, while the end result is the same.

    15. Re:Sad state of GUI development by Blakey+Rat · · Score: 1

      RealBasic and Cocoa can do all of those things easily.

      Except "geometry management" (I've only heard that term from you, so I'm thinking it can't be the most popular term used to describe it). If I understand what you mean by geometry management... if you mean automatically scaling controls when the window changes size, then yes RealBasic and Cocoa can do that. If you mean automatically making buttons longer based on how long the caption is, then you have to write a bit of code.

      But I think the real problem here is that you're still thinking in terms of "GUI libraries." I think you've been programming the old fashioned way too long and you're not having an easy time adjusting to GUI development. From my experience, people in this situation usually produce horrible GUIs anyway because they think too much like programmers and not enough like users.

    16. Re:Sad state of GUI development by master_p · · Score: 1

      "RealBasic and Cocoa can do all of those things easily."

      Other frameworks can do all those things "easily". But when you get down to implement them, they are not so easy. Trust me, I have worked either professionally or studied for hobby all major toolkits.

      "Except "geometry management" (I've only heard that term from you, so I'm thinking it can't be the most popular term used to describe it)."

      Consider the fact that the term is established by Motif (20 years ago!)...

      "if you mean automatically scaling controls when the window changes size, then yes RealBasic and Cocoa can do that. If you mean automatically making buttons longer based on how long the caption is, then you have to write a bit of code."

      I mean both, and a whole lot more. Check out lesstif, for a free motif implementation. You may find an explanation of geometry management there.

      "But I think the real problem here is that you're still thinking in terms of "GUI libraries." I think you've been programming the old fashioned way too long and you're not having an easy time adjusting to GUI development. From my experience, people in this situation usually produce horrible GUIs anyway because they think too much like programmers and not enough like users."

      Non-sensical bla bla.

    17. Re:Sad state of GUI development by Anonymous Coward · · Score: 0

      Are you actually a programmer? Doesn't sound like it to me. All you do is complain that linux sucks and how no one loves the xbox 360. I'm impressed that your trolls were highly moderated at some point in the past.

      Great job, buddy!

  39. Re:They missed the most memorable by TheNetAvenger · · Score: 5, Funny

    And just where is the blue screen of death


    They are all in the same gallery as the Kernel Panic screens, the Apple System Bomb Messages, and the OSX Spontaneous Restart Screenshots.

  40. Interesting.... by _Griphin_ · · Score: 1

    He fergot about Windows 2000?!?

  41. Missing the really early ones.. by The+Creator · · Score: 1
    --

    FRA: STFU GTFO
  42. BOB? by awesomo2001 · · Score: 5, Funny

    You managed to forget Microsoft's BOB. What's your secret?

    1. Re:BOB? by Anonymous Coward · · Score: 0

      Microsoft Bob! http://www.dans20thcenturyabandonware.com/ms-bob-l ives.html The best O/S ever out of Redmond. Oh wait, never mind, I've had too much to drink.

    2. Re:BOB? by Hillgiant · · Score: 1

      Prefontal lobotomy, shock treatment, heavy medication. The usual.

      --
      -
  43. Re:Better timeline GUIedbook, Mod up by zubernerd · · Score: 1

    Mod up the parent (alerante), I forgot about that site. Thanks. It's pretty datailed.

    --
    Accentuate the positive, don't waste your mod points on the negative.
  44. Re:Fa1lzorsD! by hesiod · · Score: 1

    Is that supposed to make sense?

  45. It goes to show you....Youth. by Anonymous Coward · · Score: 1, Insightful

    "Question: Why does it feel like everything "new" in software is a rewrite of stuff that has already been done in UNIX?"

    Since when is VMS, "UNIX"?

    1. Re:It goes to show you....Youth. by Anonymous Coward · · Score: 0

      Since when is VMS, "UNIX"?

      Since the company that gave us VMS grow up and gave us the worlds best UNIX implmantation...

      --

      I like Linux and I do use Linux... but I love Tru64

  46. Too narrow by ucblockhead · · Score: 2, Informative

    Where's Amiga? Where's Atari? Where's OS/2? Where's Gnome? Where's BeOS?

    --
    The cake is a pie
    1. Re:Too narrow by NeuroManson · · Score: 1

      Maybe because it involves computer systems still in everyday use today?

      I mean, where's OS/2, where's the SGI Irix? Where's the-

      Just drop it. Those OSes live on today, from the three groups who lifted ideas and details from failed OSes which had great ideas, but were doomed to failure by obsolescence and mismanagement (sure, there's some who still use OS/2, but that's besides the point).

      --
      Just because you can mod me down, doesn't mean you're right. Shoes for industry!
    2. Re:Too narrow by peterloyd2000 · · Score: 1

      It was a lousy flashback on the evolution of desktops anyway. I also can not see why we need to use anything above Microsoft Windows 3.1. Its been working for me for years now.

  47. Re:They missed the most memorable by Overly+Critical+Guy · · Score: 1

    Thanks! I've never seen an OS X kernel panic or "Spontaneous Restart" in five years, so I was wanting to go to that site and check it out.

    --
    "Sufferin' succotash."
  48. GNome, Window Maker and other leaders. by twitter · · Score: 3, Interesting
    All should show up pre 1999. They look just as good as Windows 98 did and were widely deployed and easy to get. They might also have included a screen shot of TWM to show how things progressed.
    • TWM, 1987
    • FVWM, 1993 (Enlightenment puts it at 1992)
    • Next Step publishes Open Step which is quickly followed by
    • AfterStep, Window Maker and others much nicer than Windows 95. Most are still available and usable with the latest and greatest free software.
    • Enlightenment, released 1996, still a leader.
    • Gnome used Enlightenment until they moved to Sawfish. The history has just begun

    Of course, everyone should see the first web browser from 1990 (actually a screen shot from 1993, but much the same) running on a Next.

    It might be hard to dig up screenshots all of desktops, but not much harder than the ones they found. It's nice to see someone including KDE in the line up so people can see a little of what they have been missing, like Virtual desktops, since the early 90's.

    --

    Friends don't help friends install M$ junk.

    1. Re:GNome, Window Maker and other leaders. by iced_773 · · Score: 1

      I dunno...the screenshots in Wikipedia make the desktops look a bit bulky compared to Win9x. (although KDE aesthetics will pwn XP anytime!)

      And btw, KDE got started in 1996, which I'd hardly call "early" '90s.

    2. Re:GNome, Window Maker and other leaders. by jb.hl.com · · Score: 1

      No offence here, your post is good, but saying something looks just as good as Windows 98 is like saying something smells just as good as fresh dog shit. Win98 looked terrible, WindowMaker still does (doesn't have to though) and TWM isn't even up to Win98s low standards. Enlightenment is great for eye candy though :)

      --
      By summer it was all gone...now shesmovedon. --
    3. Re:GNome, Window Maker and other leaders. by Solosoft · · Score: 1

      Windowmaker looked amazing no matter how you set it up. Nothing is bad about simple and working. Why do people need all these colours and flash bang things. I setup my own theme in windowmaker and it was solid black ... with white text.

      Ive saved every screenshot ive ever made and put it on my gallery (you can see as my skills progressed how customized my desktop got). Most of them are windowmaker but some of them are other desktops I tried out over the years (and always made it back to windowmaker). Once you learn how to use it being able to dock ANY app with a right click on that minimize button was extreamly handy. I would just whizz by everything on that window manager.

      This Snapshot was one of my later ones and as you can see wmaker looks pretty darn slick. I used nautilus and made the "desktop" window take the entire screen and "always on bottom" so it keept outa my way. Having desktop icons is kinda usefull and I found it extreamly handy. (why waste all that space on your screen somthing mas well be happening there).

      Although my new desktop has a ATI AIW card and I want to use it for TV if I didn't have such a media pointed setup ... I would prolly still be using it today.

      Why not ... let the ole P3 450MHz burn

      152 snapshots for your enjoyment

  49. Incomplete and Inaccurate by fairytale · · Score: 1
    This represents maybe 1/100th of the timeline of the evolution of GUI's for desktop PC's. This person obviously never used anything more powerful than a Dell.

    Some of the GUI's off the top of my head that were SIGNIFICANT advances during the 80s and 90s include:
    * Tandy Deskmate (once the #1 computer seller in America)
    * Apple IIgs interface (precursor to the Macintosh)
    * Xerox
    * OS/2
    * Amiga

    1. Re:Incomplete and Inaccurate by osu-neko · · Score: 1
      Apple IIgs interface (precursor to the Macintosh)


      Huh? Precursor? The Macintosh was introduced in January 1984. The Apple IIgs was introduced in September 1986 (and did not include GS/OS right off the bat -- that came later).

      --
      "Convictions are more dangerous enemies of truth than lies."
    2. Re:Incomplete and Inaccurate by digitalcowboy · · Score: 1

      Some of the GUI's off the top of my head that were SIGNIFICANT advances during the 80s and 90s include:
      * Tandy Deskmate (once the #1 computer seller in America)
      * Apple IIgs interface (precursor to the Macintosh)...


      Not quite. The Macintosh and the IIgs were developed and marketed in parallel. The IIgs was architecturally more akin to Windows/DOS. Meaning: the IIgs implemented a (rather nice) GUI layer on top of the existing Apple II ProDOS system. You were thinking of the Lisa maybe?

  50. OK, but where is... by silverdr · · Score: 2, Informative

    ... GEOS, GEM, The Amiga, The Atari ST and other very important GUIs of the era??! The title should rather be something else than what it is.

    --
    Now, mod me down freely. My karma can't get any worse...
  51. Where's GNOME? by ABoerma · · Score: 3, Informative

    ...or NeXTSTEP, or Amiga, et cetera.

  52. OS/2 by reporter · · Score: 4, Informative
    The link at Toasty Tech is much better than the original link. The original link seems to be focused on the GUIs of operating systems (OSes) targeted at consumers, but the Toasty-Tech link presents the GUIs for all major OSes.

    The original link notably omits OS/2.

    Whereas Windows 3.1 was a cooperatively multitasked OS, OS/2 was a pre-emptively multitasked OS just like UNIX. OS/2 was rock solid. In opinion, it had only 2 problems. It was released just slightly ahead of its time: OS/2 needed, at least, an 80486 to be adequately fast even though most consumers were running computers that had an 80386, an 80286, or even an 8088.

    The second problem was that IBM did not give it away for free. Windows 3.1 was, in general, inferior to OS/2 although Windows 3.1 was perfectly matched to the underpowered processors at the time. Windows 3.1 often crashed. Even when Windows did not crash, it often froze when an application neglected to cooperatively relinquish the processor. Windows 3.1 main advantage was that it had the Microsoft name on it. If IBM had open-sourced OS/2 or given it away for free, then IBM could have wrestled the entire OS market from Microsoft. Most consumers would have chosen a free, rock-solid OS over a more expensive, crappy OS. Being free is important since most consumers are cheapskates.

    Also, Windows 3.1 was actually based on the core code on which IBM and Microsoft had collaborated. After they terminated the joint project, IBM continued development on the core code and turned it into OS/2. Meanwhile Microsoft gutted the parts (e.g., preemptive multitasking) that, in its opinion, the consumer would not value and morphed the result into Windows 3.1.

    When you look at the APIs for both OS/2 and Windows 3.1, you can see the common heritage of both products. More than half of the APIs have identical or nearly identical names and arguments.

    If the common ancestor of both products were called "Homo Erectus", then OS/2 is Cro-Magnon man, and Windows 3.1 is the chimp that preceded Homo Erectus.

    1. Re:OS/2 by misleb · · Score: 2, Interesting
      Also, Windows 3.1 was actually based on the core code on which IBM and Microsoft had collaborated. After they terminated the joint project, IBM continued development on the core code and turned it into OS/2. Meanwhile Microsoft gutted the parts (e.g., preemptive multitasking) that, in its opinion, the consumer would not value and morphed the result into Windows 3.1.


      Hmm, I'm pretty sure that the technology from the combined MS/IBM effort went into Windows NT, not Windows 3.1. (unless, of course, you meant Windows NT 3.1).

      It always puzzled me as to why Microsoft would think that consumers would want to use a crappy version of Windows and not NT. Was it just because NT didn't have good (or any) DOS support?

      -matthew
      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    2. Re:OS/2 by hypnotik · · Score: 2, Interesting

      Actually, Microsoft wanted to use the NT for consumers. As you said, it didn't have good DOS support. However, NT needed a mamoth machine at the time to run. That's why it got released for "servers" in the anticipation that they would be a bit beefier hardware.

      --
      (I was only an egg, but then I cracked)
    3. Re:OS/2 by LWATCDR · · Score: 2, Informative

      Hell it also missed Amiga OS, Geo, and GEM.
      Like OS/2 the Amiga had preemptive multitasking and a GUI but in 1985.
      Also left off the list was Visi0n, Topview, NextStep, and News. All in all a pretty crappy list.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    4. Re:OS/2 by lemonboy · · Score: 1

      IBM was still receiving code drops of Chicago( Windows 95). OS/2 v4.xx was out. This is def an incomplete list.

    5. Re:OS/2 by Dragonlord_Warlock · · Score: 1

      Indeed where is OS/2.... It was light years ahead of windows....

      --
      - Dragonlord Warlock (aka Dion) "So many computers.... so little time...."
    6. Re:OS/2 by poot_rootbeer · · Score: 1

      If IBM had open-sourced OS/2 or given it away for free, then IBM could have wrestled the entire OS market from Microsoft.

      Just like [Ff]ree Linux distributions have since wrested the entire OS market away from Microsoft?

      No, computer buyers in the late 1980's were just like computer buyers today: they used whatever OS came preinstalled on their machine, and whatever OS ran their preferred applications. And if that combination was DOS 5.0 with Windows 3.1 and WordPerfect for Windows, that was what they dealt with, crashes and all.

  53. Re:They missed the most memorable by neus · · Score: 1

    Well i never saw a BSOD since Windows 2000; just because you don't see them doesn't mean they don't exist!
    Just like trolls i guess ...

  54. Re:Another excellent source for this bit of histor by Easy2RememberNick · · Score: 1

    "...Xfree86 has been started and has launched the FVWM95 window manager..."

      Bah! I remember that! Wow, when I first tried Linux and didn't know what the hell was going on and that virtual desktop confused teh hell out of me.

  55. Note to moderators by Anonymous Coward · · Score: 0

    The parent post is a known Microsoft shill and Apple-hater. OS X doesn't "spontaneously restart." However, Windows XP does by default when it hits a BSOD.

    Elsewhere in the comments, you will notice that the parent poster actually attempts to argue that OS X has no better graphics options than Windows XP. Clearly unaware of the vector-based Quartz and its technologies dating back to Display Postscript in NeXTStep, TheNetAvenger actually believes GDI+ is on the level of Quartz and that Vista is creating some new paradigm just because Microsoft is desperately trying to catch up to Quartz/Quartz 2D Extreme by squeezing out WPF in Vista sometime in 2007.

    The ignorance is amusing and laughable, but please don't encourage his behavior with "Funny" upmods. These kind of MSDN-subscribing fanboys always pop into Apple discussions now and then, trying desperately to defend the sinking ship of Windows technologies--technologies so bloated and complex that Windows' own developers refer to it as "broken" and "overly complicated." Hell, let's not even get into the Win32 scatter attack that Vista is still vulnerable to, given that it's still based on the same old single-user APIs developed in the 80s for the original Windows 1.0.

    So as Apple continues to leapfrog Microsoft's obsolete technologies, expect more FUD from these MSDN agents, especially in discussions on Slashdot where Microsoft employees will mod them up. In their world, Windows XP's graphics are on the same level as Quartz. Not only is it the most hilarious claim ever heard in comparisons between the two operating systems, but it illustrates the level of misinformation Microsoft's marketing brochures have unleashed upon hapless individuals still running the six-year-old Windows XP, waiting fervently for a minor update sometime next year that will barely give them some level of feature parity with OS X Tiger from April of 2005.

    1. Re:Note to moderators by Anonymous Coward · · Score: 0

      Lay off the cock, man.

  56. merging command line and gui by maynard · · Score: 3, Insightful

    "For example no mainstream GUI today manages to properly merge the power of the command line with the ease of use of a mouse driven interface, instead both act side by side,[...]"

    How would you do this? A GUI is intended to provide simplicity by limiting choice to only those options relevant within a given context. Further, it uses visual metaphor to classify objects and data. CLIs use symbolic representation and grammar to organize files and actions, and as such are closer to reading, writing, and speech than a visual interpretation of system state. It's the difference between looking at a graph vs. a table of numbers - both portray the same information, but require different regions of the brain to interpret. Perhaps the problem you lament is not the computer interface, but limitations and differences between how people manipulate visual compared to manipulating the system with symbols and words. These are two distict areas in the brain - why should they work alike?

    1. Re:merging command line and gui by grumbel · · Score: 1
      A GUI is intended to provide simplicity by limiting choice to only those options relevant within a given context.

      There is nothing wrong with that, in fact a proper command line completion script for bash will do exactly the same and limit tab completion to what makes sense in the current context (complete only to files matching *.mp3 when using a mp3 tool, complete to options when cursor is at a '--', etc.). But why does a GUI actually limit the amount of action it can perform? Not just in the "don't clutter the screen with it" sense, but in the "don't provide them at all" sense? If I want to rotate a bunch of images, why can't the GUI offer me a way to accomplish that? I have a file manager there that lets me select the files, I have a graphical tool there that can open them and actions to rotate them, but combining those is a no-go, just doesn't work. Now it migth be questionable if image filters should go into the right click menu or accessible via a sidebar or a command line (not the classic XTerm/Bash, but something that I can call from within the filemanager itself), I have see absolutly no reason why a GUI shouldn't offer that functionality. If an application offers a function, it should be available everywhere where I work with items that, that function supports and there is no reason why that should be limited.

      The Humane Interface from Jef Raskins provides a lot of more details into what is wrong today and how it could be fixed, but *both* making the system easier to learn as well as far more powerfull.

    2. Re:merging command line and gui by maynard · · Score: 1

      Yeah. In a functional system that's exactly what you would get. Data type issues go away and all objects are registered and available to all other objects within the system. The Newton is a good example of a system like this, as is smalltalk and the old lisp machines from the eighties. Squeak would be the modern equivalent.

      Developing in those systems would resolve the complaint you make pretty easily. But it would be s-l-o-w. And dumping procedural for a functional system still wouldn't resolve the core issue (IMO) which is that symbolic representation is inherently linear (one dimensional) while graphical systems represent objects and data in a two-dimensional area. So why hasn't programming by flowchart become the norm? Perhaps because one can't reasonably represent all the options available within a CLI grammar-space that one would need within a visual-area.

      IOW: A picture is worth a thousand words, but a photo of a dying Ethiopian isn't an actuarial table and can't present deep second and third order information about life in Ethiopia.

    3. Re:merging command line and gui by grumbel · · Score: 1
      But it would be s-l-o-w.
      How many orders of magnitude is a current PC faster then a NeXTStation from anno 1992? I don't know, but I bet a fucking lot. Objective-C with which NeXTSTEP was written, was already pretty fast back in that day, so I very much doubt that it would be a problem today. In fact I believe that when done properly it would be quite a bit faster than todays OSs, since code duplication, memory waste and other issues that naturally arise from todays way to write application would disappear.
      So why hasn't programming by flowchart become the norm?
      Because most flowchart stuff isn't any more high level then a piece of C code, just replacing text with fluffy graphics doesn't fix a thing, it simply replaces one flawed representation with another one that is even worse. That doesn't mean that graphical representations aren't usefull, doing GUI design in Glade or other application is easier, more powerfull and flexible then anything that hard coded GUIs in C can ever do, but one has of cause to be carefull to not throw colorfull icons at all problems that one ever encounters.
    4. Re:merging command line and gui by aussersterne · · Score: 1

      There are simple things that are obvious. For example, just by assuming and output format appropriate to the data type, a new object-aware 'icat' command (improved cat) and graphical command line terminal could do:

      [myaccount@mybox]$ icat mypic.jpg

      (image is displayed, not in window, but simply in terminal, scrolling with rest of text)

      [myaccount@mybox]$ icat mysound.wav

      (sound is played out speakers)

      [myaccount@mybox]$ icat *.jpg > myanimation.mpg
      [myaccount@mybox]$ icat myanimation.mpg

      (animation is played, not in window, but simply in terminal, scrolling with rest of text)

      [myaccount@mybox]$ ls --thumbnails *.jpg

      (thumbnails for all jpg images in dir are shown above filenames, like normal ls output only rows of imgs)
      (now, user begins mv command:)

      [myaccount@mybox]$ mv

      (then, at this point, user begins clicking on thumbnails in the ls output from the previous command, and as he clicks on each one, their names are automatically appended to the command being entered at the text cursor... finally once all desired thumbs are selected, the user types the destintaion folder in by hand)

      [myaccount@mybox]$ mv myimg1.jpg lastnight.jpg thursday.jpg myfolder

      (voila! a command half typed, half clicked. And now the user wants to mail them...)

      [myaccount@mybox]$ icat myfolder/*.jpg | imail -s "My pictures are attached."

      curses-based object-aware mail application is opened, with jpg files already attached

      And so on, and so on. I could have sworn that about five years ago I stumbled across a Linux project like this, but I didn't download it or bookmark it, and I never found it again.

      --
      STOP . AMERICA . NOW
    5. Re:merging command line and gui by maynard · · Score: 1

      A NeXT slab would typically have a 25Mhz 68040. The older cubes had a slower 030, but included an expansion backplane and a dsp chip on the motherboard. Realize though that NeXTSTEP and its development tools are not a functional system, but harken to older procedural standards. Objective C is much closer to C than it is to LISP, for example. The development and runtime environments are completely different. MacOS X (derived from NeXTSTEP) is much closer to Windows (or RSX, VMS, PRIMEOS, OS/390 - you name it) because all have procedural roots. Data types must be explicit and declared, data and processes are separate and in their own memory space - requiring message passing for interprocess communication, blah blah blah. A functional environment would throw all that away.

      The question is not: how much faster is an intel mac to a NeXT slab, but how fast is a modern PC compared to an old Symbolics machine? The answer: way the fuck faster. But we're still twenty years behind since little research has gone into functional environments in the interim. We've spent the time reimplementing old ideas on new platforms again and again and again. Weeeeeee!

    6. Re:merging command line and gui by Bullet-Dodger · · Score: 1

      I think the OS X Services Menu can do just what you describe. It seems underused though.

    7. Re:merging command line and gui by Blakey+Rat · · Score: 1

      That still doesn't really answer how it would work. Let's take your image rotation example.

      So we add this functionality into a contextual menu, which seems a logical place. But when you think about it... shouldn't we also add contrast to it? And maybe brightness? How about inverting the colors?

      Now you have a contextual menu that's 450 items long... how have you improved anything or made anybody more effective?

    8. Re:merging command line and gui by grumbel · · Score: 1
      Now you have a contextual menu that's 450 items long... how have you improved anything or made anybody more effective?

      The improvment is that you now actually can do a task that was completly impossible before, sounds like enough of improvement to justify a context menu that is a little clobbered. However the main point is that all functions that an applications offers must be accessible to other application and by the user interface and not just by the application itself as today. Sticking them into a context menu is just one way to deal with the situation, other alternatives would be to simply make them available to the standard command line, as today for example done by KDE with dcop to some extend or by providing a command line build into the file browser, similar to what Rox-Filer offers, yet another way is the services menu of NeXTSTEP. Anyway, even if you stick it into your standard context menu clobbering is really almost no issue, I mean, how do you reach the function today in Gimp? Via the menu. If you make the same functions available via context menu you would still reach them via menu, all just the same, menu simply happens to be in a different locations and probally a little bit deeper, but nothing that dramatic.

      Of course the real issue goes much deeper and doesn't end with making functions available across applications, but starts with getting rid of applications in the first place. The thing that today comes closed is probally Emacs, which really isn't just a text editor, but more like a Lisp based operating system with its own share of applications like a webbrowser, mail client, tetris game and stuff. In Emacs however there aren't really hard boundaries between applications, everything happens in the same context and can access the very same functions, so if there is some function to manipulate text, its instantly accessible in the mailreader as well as the webbrowser with no extra work. Now Emacs isn't what tomorrows GUIs should look like, since it only focuses on text and provides almost no graphical interface tools, buts its definitvly hinting in an interesting direction.

    9. Re:merging command line and gui by grumbel · · Score: 1
      I could have sworn that about five years ago I stumbled across a Linux project like this, but I didn't download it or bookmark it, and I never found it again.

      I think you are searching for XMLTerm.

    10. Re:merging command line and gui by Blakey+Rat · · Score: 1

      You can already do that with applications like GraphicConverter almost as quickly. But having every possible image manipulation command in a contextual menu isn't "a bit cluttered", it would make finding anything in there impossible. Especially since contextual menus are hard to use for the majority of users, and you're making them even harder... kind of defeats the purpose.

    11. Re:merging command line and gui by grumbel · · Score: 1
      You can already do that with applications like GraphicConverter almost as quickly.

      Can that run Gimp filters? Imagemagick filters? Photoshop filters? My custom created filter? No? Well, see the problem? Of course I can hack together a monolithic app that solves some of my problems, that is however neither effective nor flexible. I want a tool/OS that allows me solves all my computing problems in a way that is as easy and efficent as possible and that is simply not possible by a single application, but only by combining functions of all applications.

      But having every possible image manipulation command in a contextual menu isn't "a bit cluttered", it would make finding anything in there impossible.

      In addition to "Open with..." you have an entry "Apply function...", I fail to see how a single additional entry makes finding anything impossible. Anyway, back to start, this is not about how to access all the function, but about making them available in the first place, todays OSs simply don't do that (well, MacOSX does to a small extent). They don't allow me to get the job done, end of story. Even the most crude hackish ugly way to make applications functions available would be *FAR* superiour to that.

  57. Re:They missed the most memorable by gatzke · · Score: 1


    Right, I have not seen XP blue screen, but it sure does hang, become unresponsive, not respond to input, and require a nice hard reset on occasion. Death but no blue screen is just as bad.

    I worked on a dual AMD athlon 1800+ running linux for the last four years. Recently I switched to a dual Xeon running XP at 3.4 or so. The linux system was more responsive, able to actually multitask (switch between appliations smoothly) and never exhibited obvious slowdowns (adding mail to a folder takes seconds on XP for some reason). Over xmas I hope to rebuild my desktop without XP...

  58. Re:They missed the most memorable by Overly+Critical+Guy · · Score: 1

    Hell, the ATMs in my city running embedded versions of Windows bluescreen all the time. Even Microsoft's X-Box crashed at the 2005 CES. This isn't a company known for its stable platform.

    --
    "Sufferin' succotash."
  59. Apple vs Microsoft by kahrytan · · Score: 1

    Anyone notice that Apple was first to have a usable GUI?
      Anyone remember when Apple sued Microsoft over the GUI?

      Ever notice that Microsoft is always one step behind Apple when it comes to it's operating system? Whose the true copy cat?

    --
    \
    1. Re:Apple vs Microsoft by Anonymous Coward · · Score: 0

      And what of X and KDE?

  60. All fairly similar! by extra+the+woos · · Score: 3, Insightful

    The cool thing about all this is that any one of us that was familiar with one desktop could definately sit down at any of the other desktops, even from 20yrs ago (or 20yr ago if we somehow got into a time machine and came to today), and be perfectly comfortable.

    The basic premises of all these UIs is the same. This leads me to believe that in another 20yrs we will still be using the same folder/file idea that we have today. This is, I think, a good thing. It means that our damn grandkids won't be able to make fun of us for not being able to use the computer! But we can still tell them to get off our damn lawns!

    --
    replacing it with NEW Folger's Crystals! (lets see if they notice the difference)
    1. Re:All fairly similar! by Toba82 · · Score: 1

      You're quite correct. The people who buy computers are the ones who already use and like them - and they're not going to buy some crazy thing that doesn't use folders and icons and windows. To throw away everything that your users understand and like to use is to go out of business.

      Get off my lawn, you damn kids.

      --
      I pretend to know more than I really do by mooching off google and wikipedia.
  61. Only Mac, Windows, and KDE?? by Anonymous Coward · · Score: 0

    I was looking forward to seeing screenshots of GeOS, early X, the Xerox Alto, NeXT, AmigaOS...

  62. Apple IIGS not precursor by butlerm · · Score: 1

    The Apple IIgs was not a precursor to the Macintosh. It was released almost three years after the Macintosh was, an upgrade of the Apple IIe, but virtual cripple compared to the Macintosh. A 2.8 Mhz 65816 is a 8/16 bit CPU only a couple of times faster than the original Apple II released in 1977. Where the Macintosh had an 8 Mhz 16/32 bit 68000, probably a dozen times faster.

    Programming the Apple IIgs in assembly (to get any speed out of it at all) was a complete nightmare compared to the Mac. In fact the Apple IIgs was probably the most underpowered computer Apple ever made, relative to what it was trying to accomplish. As far as I can tell the sole reason for its existence was to upsell to the elementary education market, which had a *large* installed base of Apple IIs, so compatbility was at a premium.

    The Macintosh was pretty nice, but as a home computer it paled in comparison to the Amiga and Atari ST, which were released about the same time as the Apple IIgs. Both had similar 68000 processors, but much better graphics. Macintosh was 512x342 black and white (no grey), the original Amiga did 640x400 in 16 selectable colors, and up to 4096 in some modes. The Atari ST was in between. And of course the Amiga had preemptible multitasking, something that Windows didn't get until 1995, along with a whole host of other features that made it more pleasant to use than most computers today. One could run dozens of small programs (e.g. shells) in 512 KB(!) of ram, with interactivity far exceeding most modern computers with 1,000 times that much memory. Virtual memory is a curse for a desktop.

    Of course most PCs circa 1986 are hardly worth mentioning, at least as far as graphics are concerned. Better than a Mac minus the UI, but a pale shadow of the Amiga and Atari ST. The one bit sound wasn't much to speak of either. Amiga/Mac/Atari ST all had 8 bit sampled sound, 4 channels / stereo, with additional 6 bit volume modulation in the Amiga's case, making for a 14 bit dynamic range.

    1. Re:Apple IIGS not precursor by NuShrike · · Score: 1

      And yet the Mac's 68000 had double to quadruple the amount of bus-wait states (for the 16-bit buses) whereas the 65816 on the GS had none. That effectively made the 65816 equivalent to a 4MHz 286 and the 8MHz 68000.

      You obviously didn't write much 6502/65816 assembly to notice how simple and easy it is that it inspired the creation of the ARM, as well as continuing to live on in various Nintendo devices for a while. I give you the 68000 was the most beautiful and orthogonal 32-bit processor around at the time though.

      The IIGS was underpowered, but in many cases equivalent to the Atari ST and Amiga of the day:
      o 3200 colors on screen (16 per line) and outdating EGA before it came out
      o GNO/ME: a SysV/BSD multitasking underlayer that predates yet operates much like your current command-line+X in FreeBSD/Linux
      o 8-bit dedicated wavetable 32-channels (15 for stereo) in '86 predating all wavetable sound on PCs by at least 5 years (and then of course the Beatles sued, and again, and again, up to the iTunes/iPod today)

      By the time of '92, up to 16MHz cpu accelerator cars with 64K! of L2 cpu caching was available. Again, predating PCs.

      So the IIGS was not too shabby, and could've been quite a contender if Apple didn't just give up on it.

  63. Most Mac screenshots are incorrect by diamondsw · · Score: 2, Informative

    Rather useless little thing. System 5 is mistakenly called System 4 (there was no 4), and a IIgs screenshot becomes "System 5". System 7 shows up here as "System 6", and System 7.5 (it's even in the damn screenshot!) is now "System 7"

    This asshat has no clue what he's posting. Check out the other links people have posted for real GUI histories.

    --
    I don't know what kind of crack I was on, but I suspect it was decaf.
  64. You got your command line in my gui... by Anonymous Coward · · Score: 0
    GUI D&D

    ====================

    [Icon 1] [Icon 2] [Icon 3]

    {Trash}

    ====================

    CL: Icon [1...3]>[Trash]

  65. Disk Doubler! by payndz · · Score: 1

    Seeing the little 'DD' lurking in the menu bar of one of the Mac screenshots brought back memories. None of them good, admittedly, but still memories. How the hell did we get anything done when we were limited to 20Mb hard drives and (gak!) floppies?

    Judging from TFA, my first exposure to a Mac (after using an Atari 520ST for a couple of years) was an already antiquated Mac Plus running System 3 - I remember that ugly-ass diamond desktop pattern. Even the hardly cutting-edge eMac I'm typing on now would look like HAL 9000 by comparison to my 1990 self. Yet ironically, for all the advances in presentation and power, my 1990 self could probably get the hang of using Tiger in a couple of hours, since all the basic operating principles are the same.

    --
    You must think in Russian.
  66. Sloppy workmanship by Vidar+Leathershod · · Score: 1

    This "gallery" is extremely misleading, full of gaps and errors, and doesn't take the effort to point out the actual differences. The System 5.0 screenshot appears to be taken from an Apple IIGS running GS/OS, which while similar in appearance to the MacOS, was a different operating system. The System 7.0 screenshot actually has the "About this Macintosh" window open, showing us that it was actually running System 7.5.3R2 (which is skipped in this presentation, which is funny, as most clones shipped with 7.5). I used System 7.0* (--that's supposed to be a "bullet") for 6 years, and it looks nothing like System 7.5, and according to my memory, it was far less fancy, not featuring submenus on the Apple menu, or a control strip (which I never got used to, and it got in the way! :)). Also, 7.5 introduced a more grayscale appearance in both icons and interface (not platinum yet, but the Trash Can is a good example in the picture - compare 7.1 (which was very similar to 7.0) to 7.5.3 (which is erroneously placed in the System 7.0 screenshot.)

    He completely skips Windows NT 4, which while it looked only marginally different from 95, had lots of different control panels (like SCSI, for when you want to add an IDE CD-ROM, how maddening was that!). I'm pretty sure background images were a capability of Windows 95, at the least after ActiveX was installed, and I know that 98 had the capability. But he shows it in Mac OS 8, and skips Windows 2000 altogether (and Windows ME, which had some graphical variances in explorer from 98)

    These are just the things I noticed from personal experience. Who knows what else is wrong. It would have been better for him to ask for screenshots from people who actually have the stuff. I'm sure this seems overly critical, but I can't believe the lack of quality in a gallery mentioned on Slashdot.

    Vidar

    --
    The brains of a chicken, coupled with the claws of two eagles, may well hatch the eggs of our destruction.
  67. Re:Better timeline, Missing olwm, olvwm by cyber_rigger · · Score: 1

    Sun had a powerful window manager (for its time), Open Look Window Manager and Open Look Virtual Window Manager.
    These were introduced about 1989ish.

    http://xwinman.org/olvwm.php

  68. Re:Better timeline Full of FUD by jrmcferren · · Score: 1

    I call fud on two of the pictures. The GEOS picture showed a date of 1995, but GEOS on the C64 only went to 1993. The Windows 1.0 on both the TFA and your link show the desktop in COLOR!!! Windows 1.0 displayed 640 Pixels by 200(?) pixels in B&W on CGA and had no other modes.

    --
    sudo mod me up
  69. Apple IIGS by NuShrike · · Score: 1

    It is the Apple IIGS desktop, the FIRST APPLE color desktop! with QuickDraw II (first color API), first usage of ADB, adb keyboard, adb mouse, etc etc. Not only that, it's a very old version of the GUI. Give these guy some credit!

    This is a much better gallery of Apple GUIs.

    GEM seems to be left out, as well as all the other "desktops" that predate MacOS, and were just as significant in contributions.

    I do miss the multi-colored Apple menu as well as the a taking a byte out of the multi-colored Apple logo that made so much sense. Damn Beatles!

    1. Re:Apple IIGS by rbanffy · · Score: 1

      I am not sure how Apple DOS 3.3 qualifies as a GUI ;-)

  70. How very informative by dreamlax · · Score: 1

    But where does Compiz/XGL fit into the equation?

    1. Re:How very informative by Anonymous Coward · · Score: 0

      In the same place unix always is: first in technical merit and implementation, last in user recognition.

  71. Memories! by rspress · · Score: 1

    I remember the lady at our local computer store, where we used to buy Commodore 64 programs, was always trying to get me to buy Windows 1. I had been using a Mac since the first week they released it but she kept saying "Look it has a calculator, you can get a mouse for it, it has a clock". I just laughed because that was nothing new to me....and the Mac looked better as well. I was happy using DOS and I had a Commodore running the brains of an Amateur radio repeater for testing before I moved up to the real deal.

    How times have changed. I have a PC running XP, A PC running Linux and KDE and a Mac that runs Windows 2000, KDE and OS X all at the same time. I could run my Commodore programs as well but I have not wanted to go that far back ;-)

    1. Re:Memories! by rapidweather · · Score: 1

      What, no ADAM screenshots?

      I had the ADAMCALC program, a spreadsheet, that actually had "Windows" that could be positioned throughout the spreadsheet.

      One could write machine language programs to play music on the ADAM, such as jingle bells, etc.
      I wrote a small program called a "one note tester" so a keyboard could be used to sound out a note, then
      a try was done on the ADAM, to see if it matched. Soon, it was matched, according to the user's ear, and the code would be available for use in the program. Eventually, the entire song was done, and could be played.
      I had the disk drive, so the work could be saved. There was no hard drive.

    2. Re:Memories! by rspress · · Score: 1

      A disk drive. That was styling! With the TRS Model 1 in 1978 I was saving to tape, cassette tape. Same with the Vic-20 and Commodore64. I do remember the Adam and just about every other computer that was made back then. Remember the VALDOCS from Epson? I even had a pre-laptop days transluggable DOS machine. Keyboard, monitor and two floppy drives at just under 50 pounds! Running the mighty 8088!

  72. The gallery lacks movies... by kosmosik · · Score: 1

    The gallery lacks movies. At least when it comes to current desktops - each (OSX, Linux via Xgl, Vista) has nice 3D effects. For me it is quite a move forward. I don't mean eyecandy - screw that. I use OSX on regular basics and recently Xgl on Linux - on one workstation (my media center pc running Linux) I recently installed XFCE with compiz-quinn instead of ratpoison I and don't look back. Especially window switching with miniaturized windows (scale module) is great.

  73. Re:Why KDE? by Eideewt · · Score: 1

    Why would you use such a bloated WM? It's over a megabyte in size!

  74. Incomplete by therealking · · Score: 1

    Where is GEM, Geos and Star Desktop?

    This is a hacks job of things.

    --
    Gadget News at Gizmo.com
  75. Amiga timeline by GURU+Meditation+8000 · · Score: 1

    theres a quick overview of the Amiga GUI timeline over at http://www.guidebookgallery.org/guis/amigaos - though I wouldnt want to slashdot any particular site...if you use a decent search engine you can easily see a multitude of screenshots that show each incarnation...there are sites dedicated to showcasing the best setups in AmigaOS desktops - usually using a multitude of eye-candy addons (doing the sort of stuff OSX and WinXP have only just got now....). I remember having an OS3.1 desktop that used an MPEG animation as my desktop background back in 1994... OS4 now has all the transparent windows/frames/icons etc built in rather than depending on the 3rd party addin hooks and API hacks.

  76. Re:Better timeline Full of FUD by Anonymous Coward · · Score: 0

    > The Windows 1.0 on both the TFA and your link show the desktop in COLOR!!!
    > Windows 1.0 displayed 640 Pixels by 200(?) pixels in B&W on CGA and had no other modes.

    Oh, so I guess Microsoft faked their color too, huh? Take a look at that product box with the PC color screen on it.

  77. OOPS! Same thing, formatting fixed: by aussersterne · · Score: 1

    There are simple things that are obvious. For example, just by assuming and output format appropriate to the data type, a new object-aware 'icat' command (improved cat) and graphical command line terminal could do:

    [myaccount@mybox]$ icat mypic.jpg

    (image is displayed, not in window, but simply in terminal, scrolling with rest of text)

    [myaccount@mybox]$ icat mysound.wav

    (sound is played out speakers)

    [myaccount@mybox]$ icat *.jpg > myanimation.mpg
    [myaccount@mybox]$ icat myanimation.mpg

    (animation is played, not in window, but simply in terminal, scrolling with rest of text)

    [myaccount@mybox]$ ls --thumbnails *.jpg

    (thumbnails for all jpg images in dir are shown above filenames, like normal ls output only rows of imgs)
    (now, user begins mv command:)

    [myaccount@mybox]$ mv

    (then, at this point, user begins clicking on thumbnails in the ls output from the previous command, and as he clicks on each one, their names are automatically appended to the command being entered at the text cursor... finally once all desired thumbs are selected, the user types the destintaion folder in by hand)

    [myaccount@mybox]$ mv myimg1.jpg lastnight.jpg thursday.jpg myfolder

    (voila! a command half typed, half clicked. And now the user wants to mail them...)

    [myaccount@mybox]$ icat myfolder/*.jpg | imail -s "My pictures are attached."

    (curses-based object-aware mail application is opened, with jpg files already attached)

    And so on, and so on. I could have sworn that about five years ago I stumbled across a Linux project like this, but I didn't download it or bookmark it, and I never found it again.

    --
    STOP . AMERICA . NOW
  78. Re:Another excellent source for this bit of histor by Zzyzygy · · Score: 1

    Nope, it's my sanity that should be put into question. I have a close friend named Nathan Whitehorn, got the names all confuzzled.

    -Scott
    --
    My other sig is a Glock
  79. Re:Better timeline Full of FUD by jrmcferren · · Score: 1

    Alright, I think I can still call FUD on the GEOS unless the Apple II version supported dates up to and including 1995.

    --
    sudo mod me up
  80. How about adding some blank screens for Linux? by LinuxIsRetarded · · Score: 0, Troll

    I have seen one blue screen on Windows XP due to a faulty sound card driver.

    Now, I've also seen blank screens on several Linux distributions on many different modern hardware configurations because either
    (1) there are no appropriate drivers for modern video cards or
    (2) whatever hacked-together drivers are available are faulty.

    1. Re:How about adding some blank screens for Linux? by gatzke · · Score: 1


      I am not too worried about BSOD or kernel panics. At this point, these are really due to bad hardware or bad driver, both of which are relatively rare.

      I want a responsive system and XP does not provide it. I want to switch applications. I want to save files. I want to start applications And I don't want to wait seconds (5-10) to do these things.

  81. Re:They missed the most memorable by Anonymous Coward · · Score: 0

    You should destroy your XP CD. That way, when you rebuild your desktop, it won't get on there by mistake.

  82. Ahh memories by nusuni · · Score: 1

    Ahhhh what good memories. *tears up* err.... I am a bit curious though, there isnt any Mac OS 10.0, 10.2, 10.3, or 10.4 screenshots on there. The GUIs did change slightly in them, especially 10.0->10.1 and 10.3->10.4. Ah well.

  83. stupid by idlake · · Score: 1

    That page ignores most of the important GUI history: Alto, Smalltalk, Lisa, Blit, W, X10, X11, OS2, Amiga, Atari, GEOS, Garnet, NeXT, to name just a few. It just reinforces the same old misconceptions about Apple, Microsoft, and UNIX. Stupid.

  84. Incomplete to the point of being useless by nurb432 · · Score: 1

    How can you even pretend to say this is a valid timeline, when you represent only windows and macOS? ( oh, and KDE thrown in to appear like you are being thorough )..

    If you start including GEM, Workbench, GEOS, BEOS, OS/2, etc. you might be getting close.

    Hell, they even left out GNOME..

    --
    ---- Booth was a patriot ----
  85. Re:Cue old joke by Anonymous Coward · · Score: 0

    DOSSHELL? Why, of course Dos is hell! Everyone knows that!

  86. no Warp! screenshots... by Hamsterdan · · Score: 1

    Only Macs & Win/Linux

    --
    I've got better things to do tonight than die.
  87. Re:Better timeline Full of FUD by Anonymous Coward · · Score: 0

    > Alright, I think I can still call FUD on the GEOS unless the Apple II version supported dates up to and including 1995.

    Which pic are you looking at? You are talking about this timeline, aren't you? I don't see any GEOS in the 1995 section, only BeOS (and Windows 95).

  88. biased against Windows? by krunk4ever · · Score: 1

    comparing the XP/Vista and OSX screenshots, it's obvious the article is biased against Windows. Just look at the windows that are opened in Windows vs the windows that are opened in OSX. OSX gets the pretty images/photos on the screen while Windows gets the start menu and some random folders and an About dialog. I mean if you're going to compare screenshots, then compare the same things. Not just have random things pop open on the desktop where OSX gets the pretty pictures and Windows just get to display default icons.

  89. Re:They missed the most memorable by StikyPad · · Score: 1

    Not to mention the [blink]Guru Meditations[/blink].

  90. In the days of win2k and ME by Deliveranc3 · · Score: 2, Insightful

    There was Enlightenment, that sucker WAS SEXY!

    Still one of the sexiest in existence, people with 2 button mice suffered and they never really fixed that but it's a pretty pretty baby.

    It's also one of the smallest and quickest GUI's around.

    Wish it shipped standard :(

    1. Re:In the days of win2k and ME by Tab+is+on+Slashdot · · Score: 1

      Even going up against Compiz, the completely non-accelerated, non-3D Enlightenment DR17 manages to be vastly more beautiful. And it's fast and incredibly light-weight, too. Nothing else delivers eye-candy and performance like Enlightenment.

  91. Re:They missed the most memorable by neus · · Score: 1

    Windows: - BSoD ( Black - Win 3.x - or Blue ( Wix 9x onwards ) - RSoD ( early builds of Vista ) - GSoD ( XBox 360 ) Unixes and alike: - Kernel Panic Mac: - Kernel Panic ( Mac OS X ) - Sad Mac - Bomb and the venerable Row of Bombs ( nothing better than seeing a screen full of tine litle bombs ) So you see, neither of them is the Ultimate OS. Linux can also become stagnated, become unresponsive, start sending random noises to the PC Speaker and reboot with no apparent reason. U can try to only use the most stable software, the most stable kernel, the most stable shared libs, but you'll always find some bad written driver, application, lib, whatever that will take you beloved os to shreds. You cant install it on a laptop without having to tinker with some obscure switch, compile and patch some driver ( or having to write one yourself), i even had to write my own DSDT table and patch the kernel to have decent ACPI support for my Acer. If you're a noob the only help you'll probably get is RTFM or STFG, and so on. Everyone will complain about something or someone. I bet the are a lot of happy Mac users out there, but i had to sell my mac mini as it constantly hanged and was more slow than molasses in March. Conclusion, Windows is the captain of the football team, everyone wants to be like him but dislikes him at the same time for being such an asshole and the nerds hate him for being such a bully. Unix is the President of the Computer Club, the Alpha ( pun intended ) Nerd, it has his share of nerdy followers but doesn't get laid and Windows keeps getting his lunch money. Mac is the cheerleader, always cheerfull, hip, has a fashion sense and everyone drools over her but is dumb like a doorknob. Since she's no smarter than a peanut, she secretly dates Unix and uses her sexual attributes to make him do all the work.

  92. Bad Screenshots by TheoMurpse · · Score: 1

    Is it just me, or did the screenshots make Windows 3.0 look nicer than any other Windows version except XP? Of course, Windows ME and Windows 2000 and all Windows NT versions are missing from the blog, but still...3.0 definitely looked nicer than 3.1.

  93. Re: by stilgar59 · · Score: 1

    Damn,
    I was thinking the exact same thing. Where are the Amiga screenshots. IMHO the desktop has just about everything beat until windows 95 where of course when the 1200 came out it should have had an 030 and 24 bit color at least and could have lasted a lot longer except for the owners... All I wanted to say was thank you for at least mentioning the Amiga.

  94. Where is CDE? by sanyam_y · · Score: 1

    There is no snapshot of the Unix standard proprietary desktop CDE. Either the author of the page did not consider CDE as a desktop (quite true) or probably he didn't know how to take a snapshot in CDE :).

  95. Re:Better timeline Full of FUD by jrmcferren · · Score: 1

    No, look at the picture of GEOS in the upper right hand corner it shows 12/16/95 05:18 PM The copy of GEOS I had only went to 1993 and I know this because I tried to use it in 1999.

    --
    sudo mod me up
  96. GEOS? by Terminus32 · · Score: 0

    Where's the GEOS (for the CBM64) & Amiga screenshots?

    --
    http://nathanlindsell.blogspot.com/
  97. what a maroon by Anonymous Coward · · Score: 0

    his "Macintosh System 5" is ACTUALLY GS/OS running on an Apple IIgs(or emulator), likely 5 or 6...
    http://en.wikipedia.org/wiki/Image:AppleIIGSOS.png

    snicker. chortle. ROFLMAO.

    The control panel items SHOULD have been a dead giveaway! Slots?! control panel on a Mac?! WTF?!

  98. Re:Better timeline Full of FUD by Anonymous Coward · · Score: 0

    I see you're talking about the desktop clock showing the current date and time when the screenshot was taken. That's not a release date. It could be any date the computer clock is set to.

    What a waste of time this has been. Thanks for not doing your homework.

  99. Re:Better timeline Full of FUD by jrmcferren · · Score: 1

    The GEOS Desktop Clock cannnot go beyond 1993 it runs from 1983 to 1993. There is no Real Time Clock in the Commadore 64. You have to set the RTC from GEOS every time you load it. The C64 has an internal timer in 1/100 seconds starting from 0 at every startup. If you want to see how long you C64 has been on since last boot type PRINT TIME with no quotes around the time part. Time is a system variable. I had a C64 back in 1999 and I know how to use the damn thing. I also had GEOS with the C64.

    --
    sudo mod me up
  100. Re:Better timeline Full of FUD by Anonymous Coward · · Score: 0

    Didn't you click on the screenshot? It goes to a page about GEOS for the Apple II. Why do you think the Apple II version can't go beyond 1993?

    I don't know for a fact that it can, but it's a pretty obvious alternative explanation. Why not do some research before crying 'FUD'?

  101. Re:Better timeline Full of FUD by jrmcferren · · Score: 1

    The web page refers to the C64 version which does not, I don't know about the Apple II version.

    --
    sudo mod me up
  102. still alive anyways :) by hurfy · · Score: 1

    hehe my old forms program still runs under gem 3 (1988) of course running it all under win98 brings it back to speed it was on the 386 but hey it feels more real that way ;)

    Now if only my old database (DOS) ran as fast under XP as on my 386 :(

    Anyway, article not that impressive :(

  103. Re:They missed the most memorable by TheNetAvenger · · Score: 1

    Even Microsoft's X-Box crashed at the 2005 CES.

    Ok, you do realize the XBox 360 hardware wasn't even ready at the 2005 CES, right? Even at E3 the demonstrations were not on XBox 360 hardware. The Hardware being used were dual G5 Macs, with an emulation layer for the non-existent GPU features and the tri-core.

    WindowsXP hasn't crashed in years for a lot of people, it is nothing like Windows98 or Apple System 7-9 where both OSes had stability issues.

    Also, I doubt your ATM is running 'embedded' Windows, or even an NT core version of Windows if it Blue Screens and doesn't recover with a restart at the very least.

    There is NO OS that has not crashed and burned on someones hardware at sometime.

  104. Screenshots aren't the best way to measure by Ed+Avis · · Score: 1

    Screenshots are a bit pointless. In 'look and feel', feel is by far the more important. You can keep your transparent xterms and zooming window effects. Give me something ugly, solid and functional any day.

    --
    -- Ed Avis ed@membled.com
  105. Re:They missed the most memorable by Anonymous Coward · · Score: 0

    > There is NO OS that has not crashed and burned on someones hardware at sometime.

    Qantas never crashed.

  106. Re:They missed the most memorable by TheNetAvenger · · Score: 1

    >>Qantas never crashed.

    "Famously, Qantas quote that they have never had a fatal jet airliner accident. While this is true, the Australian national airline suffered several losses in its early days, before the widespread adoption of the jet engine in civilian aviation. "

    (Sorry, couldn't resist...) :)