Hobbes2099 wrote:Something I never understood was how Apple's OS managed to wake up instantly while Windows always took seconds, nearly a minute and even more so on old computers.
What exactly happens under the hood that Microsoft has never been able to replicate?
Unix vs. non-Unix?
Really? It's that simple? Wow.
I never knew. I mean, I heard something years ago, but it's been over 10 years or so (how old is OS X anyways?), I figured MS could aim for something similar.
Thanks!
I'm not saying that's the answer. Just guessing. I've run Linux/Unix for over 16 years and find it much more stable and efficient.
Apple has tighter control over its hardware, and OS X doesn't go into as deep a sleep as Windows does.
Usually, Windows hibernates when you close the lid, which basically takes all of RAM, dumps it to disk, and then shuts the computer down. When you open the lid, the computer reboots completely from scratch. Windows realizes it's resuming from a hibernate, loads RAM up from the file on disk, and then resumes where it left off. This is faster, usually, than a full boot, and brings you right back where you left off, but it's not terribly fast.
OS X goes into a 'suspend', low power state, where it continues to maintain energy to the RAM, and just barely tickles the processor once in awhile to check to see if the lid's open yet. So it slowly bleeds away power, where a true hibernation doesn't. But it's pretty efficient, and on my MBP, I only lose about 10% a day of charge, which I think is a pretty good tradeoff for an instant start. When the lid is opened, the system just picks up exactly where it left off, everything being all pre-loaded.
It does seem to do a scan for new hardware on restart, and some devices get re-initialized (like the wireless), but it's usually fast enough that by the time you actually need those resources, they're ready.
Windows has a standby mode, which works a lot like Apple's, but usually it's much more energy-consumptive; on a couple of laptops I've had, the power consumption is more like 10% per hour instead of per day. I think that's because Microsoft doesn't control the hardware, and most manufacturers don't maintain the combination of hardware and software expertise needed to make their standby modes work really well.
Oh, and no, I don't think it's Windows versus Unix. In most respects, Windows actually uses its hardware better than OS X does. But power management is in the 'finger pointing' area, where manufacturers think Microsoft should be doing it, and Microsoft thinks the manufacturers should be doing it.
I'm sure I read in one of the OSX Lion articles that on standby (or whatever mode) it takes a screenshot of running applications to use as placeholders until they're ready to go again.
That would explain the little interval during which the display is on but the computer doesn't respond to input, then. So it's a psychological trick to make the waking-up process seem even faster than it actually is.
Has anyone tried the developer preview yet? I may check it out just for fun.
I got to see it running in a VM at work today. The new interface is pretty slick. I'm very positive about how it looks right now.
Having installed the Win8 Dev Preview on my E6400 I can tell you Windows sleeps and resumes VERY fast.
The bootup time is also great.
Time to sleep is about 3-4 seconds.
Time to wake is less than 4 seconds.
This is a non UEFI bios on a low end corsair SSD, total cold boot time is 14 seconds including logon
(I estimate 5 seconds of that is Dell bios and intel disk controller.)
My only worries about the interface of Windows 8 is that it seems to have two versions of major applications that seems more severe the full-screen mode vs windowed mode in Mac OSX Lion. I haven't jumped into the deep end of how things work, so I have absolutely no idea what that requires from a developer.
I got to see it running in a VM at work today. The new interface is pretty slick. I'm very positive about how it looks right now.
I think I'll try to just run it as a VM. I've heard it's a bit rough, so I don't want to spend a lot of time on it.
SuperDave wrote:I got to see it running in a VM at work today. The new interface is pretty slick. I'm very positive about how it looks right now.
I think I'll try to just run it as a VM. I've heard it's a bit rough, so I don't want to spend a lot of time on it.
It should work in Hyper-V, but it probably won't work in Virtual PC.
tuffalobuffalo wrote:SuperDave wrote:I got to see it running in a VM at work today. The new interface is pretty slick. I'm very positive about how it looks right now.
I think I'll try to just run it as a VM. I've heard it's a bit rough, so I don't want to spend a lot of time on it.
It should work in Hyper-V, but it probably won't work in Virtual PC.
I've got virtual box installed, so I'll probably just use that. I saw a tutorial on how to set it up with VB, so I assume it works.
I suspect due to the interface changes in Win 8, a lot of enterprises might not upgrade for the sake of user training costs. They may skip it like they did Vista.
I suspect due to the interface changes in Win 8, a lot of enterprises might not upgrade for the sake of user training costs. They may skip it like they did Vista.
Training is usually the least of the concerns; licencing and breaches are the usual suspects. Companies who are serious about the safety of their information will wait for the initial security holes to be breached and patched. Once security firms are able to assess how Win8 compares to previous iterations, companies will take a look and see if there's any benefit.
My company has about 14,000 PCs and all still run WinXP. All our network security, drivers, configurations have been optimized for WinXP. Doing everything all over again for Windows 8 is just not worth it.
MannishBoy wrote:I suspect due to the interface changes in Win 8, a lot of enterprises might not upgrade for the sake of user training costs. They may skip it like they did Vista.
Training is usually the least of the concerns; licencing and breaches are the usual suspects. Companies who are serious about the safety of their information will wait for the initial security holes to be breached and patched. Once security firms are able to assess how Win8 compares to previous iterations, companies will take a look and see if there's any benefit.
My company has about 14,000 PCs and all still run WinXP. All our network security, drivers, configurations have been optimized for WinXP. Doing everything all over again for Windows 8 is just not worth it.
My company has 30-40K PCs, and we do think very seriously about training transitions. We're on XP looking at going to Win 7. The interface changes to 8 would require significantly more dollars to be spent in training. We also consider all the rest of the stuff you mentioned, but training to Windows 8 doesn't look trivial with our work force.
But we have a lot of people who have lower computer skills, although that's not the problem it was 10 years ago.
So anyways, since I'm actually at the build conference (and got the free tablet ) let me chime in on what I've learned in the sessions and additional info I've come across.
The metro interface is purely for tablets and consumers. All versions with a quick left side send you back to a traditional windows 7 style desktop.
Touch is in no way, shape, or form intended to be the interface used for data entry heavy/business apps/office, etc. They are embracing touch for media, sharing, browsing, and other common consumer tasks.
Everything that today runs on win 7 will continue to run just the same in win 8.
My Developer preview came loaded with some little games similar to the 99 cent titles you can get from the itunes store. Seems Microsoft (rightfully) wants a piece of that pie. Every other bullet point at the conference is encouraging developers to start apps for the store (since they're pretty far behind apple at this point in time).
The "windows 8 apps will be html 5 and javascript" FUD was exposed as FUD. They still plan on supporting XAML, Silverlight, WPF, and the entire .NET stack. .NET is getting some signficant upgrades and focus in the areas of parallel processing and socks communications. They have exposed some pretty rich hooks into the rendering engine of windows, and have made it easy for developers of all types to get hardware accelerated transitions, etc. There is very deep direct x integration and exposure through the new APIs, which should make life a lot easier.
Visual studio and blend are getting a lot of new features for pre-wiring the metro style interfaces (for consistency) and a lot of hooks for sharing between applications (highlight in IE, send to twitter app, email, whatever consumes that interface). This type of contract style hooking will allow a lot of your apps to interact without developers having to write any plumbing which should be very nice (though I worry about too many apps showing up as choices there).
Visual Studio and Blend are being leveraged with a lot of c++ features, direct x features, and basically should now be able to handle being first class game development engines (again, for the app store I'm guessing).
Microsoft is generally pretty good at providing good tools for developers, they're really going after the app store and the easier casual experience (metro). Hardcore/power users can stay in the windows 7 style desktop and be happy. Seems they're trying to satisfy both camps, not sure how it will work out but I'm encouraged. The free tablet will replace my ipad if the app store can ramp up like the itunes store did.
Speaking of Media, I know on the Win 8 blog they said they'd not include Media Center in this developer version, but that it would be in a later release. Any rumblings of what's going on there?
I'd actually like to see it get a Metro make over and a change from MCML to something more supported so that plug ins wouldn't be such a pain for people to produce.
Any word on 360 games running on Windows 8? I think I read that rumor a while back.
Any word on 360 games running on Windows 8? I think I read that rumor a while back.
I think it was more about this than running 360 games directly in Windows 8. That never made a lot of sense to me, as you'd have to do emulation or VM due to the different types of processors, which would have some pretty serious hardware requirements I'd think.
I hope it's possible. I would be pumped if Windows 8 could run the Xbox UI and XBLA games. Running 360 games and being able to add AA/AF would be a plus though.
I hope it's possible. I would be pumped if Windows 8 could run the Xbox UI and XBLA games. Running 360 games and being able to add AA/AF would be a plus though.
XBLA would be interesting, but I don't think native code would work. They just need to be compiled to run in Windows.
The problem I would see is that even if you ignore the technical issues, the licensing would be a minefield as a lot of these already have PC publishing deals.
Yeah, I simplified it a bit. You're right it's more than just getting it to run. But I think it's probably not nearly as difficult if they're developed on Windows hardware using a lot of the libraries MS makes available.
DirectX and XNA developed games should be considerably easier than, say, porting a PS3 exclusive I'd think.
Pages