11 ms·
Windows 1.0 and the Applications of Tomorrow (2005)
- bdcravens 12y agobut seemed much saner than trying to recreate an actual vintage 1985-era PC-AT. That was only a 20 year old computer at that point. I can play media from 50 years ago easily. I'd argue that software are more appliances (they do things) than media, and appliances from 20, 30, 40 years ago are still serviceable and working. Yet we are amazed when a Raspberry PI can serve web pages, despite the fact that it's many factors of more powerful than many circa-1998 web servers.
- jimktrains2 12y agoBut yet we have phones and computers that are arguably as (un) responsive as their counterparts in 1998. I really wish those issues would be addressed rather than making things flashier with sexy transition animations.
- fournm 12y agoBut they aren't. I'm pretty sure I've owned multiple machines that couldn't POST in the time it takes my current desktop to be at a usable state, and I have more on-die L2 cache than my first desktop had RAM. The past was full of a lot more paging to disk and it was awful. I mean, sure, things haven't progressed as much as they could I suppose, but I also don't know the last time I had to wait 5-10 minutes for a computer to shut down.
- jimktrains2 12y agoIt's not that we don't have the ability to be responsive, and somethings are. My desktop is still laggy at times, (though it's gotten a lot better when I switched to a lighter DE (for obvious reasons)) and my phone still has issues just loading text messages without me having to wait multiple seconds. That's the kind of stuff I'm talking about. A Text Messaging app shouldn't have perceivable load time. My phone shouldn't freeze doing a transition between desktops. Computer desktops shouldn't take time to open up a menu. We've come a long way, and have tons more raw performance, but I just feel that we squander it on things that don't add any value.
- danielweber 12y agoThe past was full of a lot more paging to disk and it was awful. Those sounds just went through my head. That noise hurts just to think about. but I also don't know the last time I had to wait 5-10 minutes for a computer to shut down. Windows 7 seems to take 5 minutes to shut down, even if I give it a head-start by explicitly closing all applications I can see or understand. There are 137 "processes" and over 200 "services" running right now on the Windows 7 machine I am at. I can't watch them go away when I shut down, because if I leave the task manager running, Windows 7 complains about the Task Manager still running when I want to shut down. There are many things that are much better today, but it seems that some things are getting worse.
- anonymfus 12y agoIn theory you could install Windows Performance Toolkit from Windows SDK and then trace shutdown with xbootmgr command, then try to analyse resulting .etl file (xbootmgr will save it to the current folder) with xperf. In practice that will probably take more time than you could save by optimizing shutdown.
- varkson 12y agoThat sounds painful. Ever since I went to Win 8 my shutdown has been instant. Startup is around 3 seconds.
- beagle3 12y agoMy first XT clone could would POST in less than 3 seconds if I skipped the memory test (all 640K of it), and I stayed with DOS 2 much longer than everyone else because it run almost all software at the time, and properly configured (big BUFFERS in CONFIG.SYS, for example), it would boot from floppy in 3 more. I've recently managed to get an ubuntu server to boot as quickly (with preconfigured network interfaces and a few other things), but for years I could find the magic combination that would boot a usable system that quickly. And I haven't seen a Windows machine that boots to usable state in less than 15 seconds (SSD, 30 seconds on magnetic hard drive) in a long time. "Usable" means you double click on something and it responds, btw - not that it shows the desktop.
- sdegutis 12y agoWho's amazed at that? I imagine you'd be hard-pressed to produce someone that is impressed that "a tiny computer can run real computer programs".
- smacktoward 12y agoYou can definitely play media from 50 years ago... but "easily" may be a reach too far. How many people have easy access to a player for eight-track tapes (circa 1964: http://en.wikipedia.org/wiki/8-track_tape http://en.wikipedia.org/wiki/8-track_tape), for instance? Or a way to play back old Super-8 (circa 1965: http://en.wikipedia.org/wiki/8_mm_film http://en.wikipedia.org/wiki/8_mm_film) home movies? These devices can be tracked down, but it's not like they're sitting at most peoples' fingertips.
- laumars 12y ago8-track was a big flop outside of the US so didn't really get the ubiquity that competing formats did. To look at things another way: how many people can play HD-DVDs? It's only a few years old but suffered the same commercial failure as 8-track did in Europe. Yet most people still have easy access to a VHS players, audio cassette players and record decks despite those all being old technologies too.
- astrodust 12y agoIf you have easy access to a flea market, you've got easy access to those.
- anigbrowl 12y agoAnd many of you are hesitant about using high-level languages like C because of the performance issues. Well, we seem to have overcome that worry. I think most programmers of that vintage must be horrified by the amount of bloat in modern computer systems. I gave up worrying about not knowing what every file in my operating system does several years ago, but I still feel bad about throwing in the towel.
- alex_duf 12y agoGarbage collection ? pff, it's never going to work.
- danielweber 12y agoHow do you feel when you run "top" or its equivalent on a modern OS? I feel like the barbarians have completely taken over, and if not I certainly couldn't stop them if they wanted to.
- anigbrowl 12y agoAnxious. I'm still good at dealing with process lists and so on, so I have a knack for things like malware removal or reversing. But whereas I used to know what was going on, these days I have to rely on intuition more than I used to, and it reminds me uncomfortably of youthful ignorant blundering. I guess it's like being someone that used fix their own care and tune the engine etc., only to have modern vehicles increasingly turn into black boxes that require more and more specialized equipment. I don't love such troubleshooting enough to want to make it my full-time occupation, so I suppose it's an inevitable one-way street.
- vezzy-fnord 12y agoYeah, I think there should be a middle ground. On one hand, having more resources that enable us to worry less about lower level minutiae is good. But on the other hand when I see a resident Android device take up well over 400MB from its UI and services alone, I can't help but think there's something a little wrong here.
- bluedino 12y ago>> Now, I know when some people see graphical environments they start whining and saying “But I don’t want to use a mouse. There’s no room on my desk for a mouse.” How small were desks back then, not having room for a mouse? >> Well, with Windows, for the most part the mouse is optional. I won’t be using a mouse at all during this demonstration. I remember feeling 'cool' that I could use a Windows machine from only the keyboard back in the 90's.
- hayksaakian 12y agoRemember that a large monitor occupied 80% of your desk space back then.
- justizin 12y agoKeep in mind also that today when we plan a desk space, we plan for a mouse or trackpad and a keyboard, and we don't do much else. People then still did lots of paperwork and needed space for other things. Of course they didn't have space for a mouse yet.
- michaelhoffman 12y agoDesks were smaller, the big desktop computer and big CRT took up more space, and one was more likely to have a bunch of paper, books, and other stuff taking up space on the desk too then than today.
- eddieroger 12y agoI wasn't doing too much computing in 1985, but I don't think the issue was so much about small desks as it was large computers. Likewise, mice were larger then, too. The whole "smaller computers" is still a really recent thing, despite the recentness of the whole "computer" thing in general.
- k__ 12y agoI remember people at my first job freaking out on how fast I could navigate complex GUIs with the mouse. It probably helped that I played RTS and FPS for years, lol.
- jra101 12y agoIt's amazing to me that cake.c with minor modifications can still compile and run on modern Windows. http://jcode.org/screenshots/cake.png http://jcode.org/screenshots/cake.png
- laydros 12y agoIt's amazing in some ways, but I'm concerned it held Windows back to maintain such a high level of reverse compatibility for so long.
- mwcampbell 12y agoOn the contrary, the Windows API has endured through some pretty big changes, e.g. from 16-bit to 32-bit and then 64-bit, and from a cooperative single-address-space system to preemptive multitasking with memory protection between processes. (I was surprised that each application had its own message pump even in the cooperative multitasking days.) In what ways do you think the Windows developers' hands were tied by the need for backward compatibility? Seeing how similar the Windows 1.0 API was to the current Windows APi for desktop apps, I'm actually sad that Microsoft decided to (mostly) abandon that legacy for the new "modern" Windows apps under Windows 8 and Windows Phone 8.1. There's no reason why the classic Windows API couldn't have been adapted for these new-style immersive apps running inside sandboxed containers. But I guess the Windows API gained too much of a reputation for being old, crufty, ugly, and unapproachable for new developers; that's certainly how I saw it when I got my first copy of Visual C++ in 1998. But now I wish Microsoft hadn't responded to that perception by abandoning that API, which has now evolved for decades.
- gecko 12y agoI doubt he meant that third-party developers' hands were tied. I think he means that Microsoft spent incredible resources on backwards compatibility at the expense of innovation. To take the most extreme example I can think of: going from OS 9 to OS X, Apple preserved a (comparatively) handful of APIs as-was, another pile as nearly-the-same-but-requires-modification, and regardless of which they temporarily preserved, made it very clear that you were going to completely rewrite your application if you intended to have a genuinely native OS X experience. By contrast, farking Microsoft OS/2 apps survived into Windows NT 4, and Windows 3.1 apps ran from 1993 through some forms of Windows XP without blinking. Even in the hated Windows 8, Microsoft went out of their way to make sure that they maintained very clear and well-spelled-out migration paths. It is theoretically possible (though you'd be insane) to write a WinRT app in C that mostly uses kernel32.dll, if you want to, because WinRT is unapologetically based on COM, which is in turn based on an old way that vtables happened to be laid out in VC++, which is in turn based on how C structs used to lay out function pointers. This hurts WinRT performance compared to what they could've accomplished with a Swift-like linker. Did this insane focus on backwards compatibility hurt Microsoft? I don't think you can conclusively say. Did it hurt me as a former Windows developer? Only at best tangentially; all the backwards compatibility crap is pretty abstracted from you if you hang out in .NET land. (Except when it isn't.[1]) And at any rate, I don't think the bleed-through is noticeably worse than e.g. POSIX intrinsics showing up in OS X. But I think the argument that the engineering required to ensure Windows maintained such a strong backwards compatible stance ate out of resources that could've kept Windows more up-to-date has a point. [1]: http://bitquabit.com/post/zombie-operating-systems-and-aspnet-mvc/ http://bitquabit.com/post/zombie-operating-systems-and-aspne...