It truly amazes me how lazy developers are when it comes to supporting new things. They whine and bitch and drag their feet and blame MS, rather than just admitting they have to learn something new and doing it.
I'd expect that a lot of developers just don't see the significance, as long as they can get a product out that works in a reasonable number of real cases. That's where their bread comes from, after all.
2011 will be the year of DisplayPort on the desktop!
I just went on and put XP back on it though, I'm very seriously considering putting Ubuntu on it now.
I can heartily recommend it. The last release came into a bit of a weird spot as far as graphics drivers were concerned, but now everything runs a lot smoother again and the accelerated desktop is properly vsynced as well. Compared to XP, there seems to be less disk rattling and throttling of fans, though battery life is about equal.
Just do a bit of googling up front; there were a few minor issues with my Samsung NC10 too, but nothing people hadn't thought to pre-package fixes for.
So that means that about 200 days
That's okay, it's not like he has to stand there turning a crank while the bits are being moved. Even Windows has the possibility of scheduling scripted events, which most likely is the method applied here.
The sad thing is that I've met plenty of computer geeks who basically say that physics is useless. They then go back to their beloved computers without realizing the tragic irony of what they just said.
Still, you're making that remark using a web browser running on top of a software stack made up of at least a multi-tasking OS kernel, a dynamic linker and an assortment of userspace libraries, written in various high-level programming languages with optimising compilers. It's not as if the transistors came up with all that by themselves.
Physics in itself is important, there's just no need for most people to be physicists.
Right, because so many people have issues where Windows breaks on their hardware.
Only every time something in the driver APIs changes or the hardware vendor in question otherwise can't be bothered to do their part properly. Which, of course, is simply unheard of.
OS X reports disk space better than Windows, Finder reports a 2.5MB file as taking 2,572,834 bytes of disk space.
Which version of Windows are you talking about? There would seem to be a "Size on disk" field in the properties dialog of at least XP and 7, and I'm pretty sure it's been there in several older versions.
Yeah, I mean, wouldn't it be great if we had motherboards with connectors on them that you could use to stick in, say, more memory or like even a massively parallel stream processor for graphics, or an additional NIC or sound ca...
Oh, right.
Hey, if it's old-fashioned stuff you find t3h l33t, why not teach the kids Brainfuck? It's essentially the same language as P", devised by the man Böhm himself in 1964, way before all of this pish posh about how to conveniently build non-trivial programs, but also including the modern concepts of input and output. Make no mistake, however - with only eight operations to choose from, it's about as simple as you can get, and many a programmer will attest that it's fun to play with!
Technically true, if your program only processes a large chunk of stuff once and never has to wait for network activity, disk access, user input or some other kind of external event. NOPs aren't what the parent spoke of, however. These days, a program typically uses a blocking call or voluntarily yields execution when there's nothing for it to react to, so in the absence of active processes the OS can tell the processor to halt (possibly slowing down or turning off parts of itself until an interrupt comes by and wakes it up).
QBasic was written to be run as the sole program on an architecture which didn't have the benefit of such features, so it uses a different mechanism, which is a bad fit to modern power saving schemes.
Hope that helps.
It's possible that the drivers handling power management on one set of peripherals are better at their jobs than other ones, or play more nicely with some managerial component. With exceptionally crufty codebases there's lots of opportunities for unexpected effects; whether that has anything to do with this accusation of "bloat" depends on what is actually meant.
Somehow I doubt most people making it know either, nor have enough acquaintance with Windows's innards to make an expert judgment.
1 + 1 = 3, for large values of 1.
