Hard to say. I'm pretty sure the 3 second time had a lot of "typical" linux components stripped out, but note that you won't get a shell until everything's finished loading, while X can be started in parallel with other things and be usable while other components start. I believe some work was done that got it under 5 seconds from init to usable. There's still the bios time (0 with a tricked-out coreboot setup) and the time while the kernel starts up before init (this takes 2-3 seconds for me, no idea what "normal" or "fast" is). That adds up to ~7-8 seconds.
One thing to note is that storing the kernel directly in EEPROM lets you skip the bootloader entirely. Bootloaders are usually pretty fast, but they usually have a programmed delay of a few seconds to let you choose a kernel or whatever.
It's not really all that fast. With coreboot there's an option to flash a kernel directly to your bios chip, and skip bios and bootloader entirely. Makes kernel upgrades a pain, of course, but they got wall time from poweron to a working linux shell down to three seconds.
Huh. I dropped my OLPC from about 4 feet (a little less, maybe 3.5 with some forward momentum too) just a week ago. It bounced to about 1.5-2 feet, then landed again. Outdoors, hard asphalt. No damage except a tiny depression in the plastic on one corner.
Not the first time I've dropped it, either. Only thing I've broken from a drop is a tiny chunk of plastic off the headphone jack--in a ~6 foot drop onto a tile floor that hit the wall and my leg and thus didn't get the full force, but did manage to bend the 1/8th inch headphone connector.
A book that I liked when I was younger was To Infinity and Beyond by Eli Maor. It's a sort of advanced layman's look at infinity and the closely-related zero. It includes mathematical topics your students probably haven't seen before (and won't, unless they become math majors), in enough depth to be interesting but not overwhelming (not enough to really be useful mathematically, either just to make them interested and perhaps help them be more comfortable if/when they get to higher math). It also has a lot of history.
It seems to be mostly available on google book search (a bunch of random pages missing, but mostly there) so you can check it out without leaving your computer!
I definitely agree. The vast majority of the music I own is from independent labels, and most of it I often listen to an album at a time. I understand that certain formats (where you don't have the listener's attention for long) work better for singles, but music that's meant to be good, and meant to be really listened to, still can and does work better as an album.
I've dropped my 89 down numerous flights of stairs, and several feet to the ground more times than I can count (the little plastic bits that hold the cover to the calculator are mostly worn away, so if I pick it up by the cover in the wrong direction it falls out). It still works wonderfully, and I've had it for 6 years.
The worst that happened to it is I think one of the times I dropped it down the stairs the memory reset (probably jarred the batteries and the backup battery at the same time), but only the non-archived memory, so I didn't lose anything important.
No. Cross-domain xmlhttprequests are blocked by firefox at least, and I'd suspect by other browsers as well. The point is that you don't have to do a cross-domain xmlhttprequest here, since google conveniently stores it in a separate javascript file, and that is embeddable in other pages.
Uh, I would hope a light was being shone on them. Fluorescence only happens while a UV light is actually shining on the object. Phosphorescence is the one that lasts after the light stops. If there were no light being shone, that would mean the pigs aren't fluorescent.
I think I remember reading about this either on firefox dev blogs or mailinglists or IRC. IIRC, the upshot was that verisign should be doing "extended validation" type things on all their clients. The validation they have now is really pretty shoddy, shoddy enough that they'd be risking getting kicked out if they weren't so big and so many websites would break. But that's just my memory, which could be bad, you'd have to look into it yourself.
And after viewing it we find... it wasn't worth it. Just a bunch of "This didn't work. This didn't either. Nor this. And that didn't either. HAIR GEL! THAT WORKED!". No discussion on why or other things to try or anything.
In the interest of accuracy, canvas was actually implemented by Safari before it was specced. IIRC (I participate in WHATWG but haven't followed canvas closely) a few changes were made between the spec and safari's version, but not many.
Session storage was specced before being implemented, although there was (and still is) editing done based on feedback from the people implementing it.
Slashdot Mirror
Who was the retailer? We need to know, so we can avoid them.
Beats me, you'd have to ask on the coreboot mailing list.
My best guess, though, is yes. (Excluding, of course, Windows startup.)
Hard to say. I'm pretty sure the 3 second time had a lot of "typical" linux components stripped out, but note that you won't get a shell until everything's finished loading, while X can be started in parallel with other things and be usable while other components start. I believe some work was done that got it under 5 seconds from init to usable. There's still the bios time (0 with a tricked-out coreboot setup) and the time while the kernel starts up before init (this takes 2-3 seconds for me, no idea what "normal" or "fast" is). That adds up to ~7-8 seconds.
One thing to note is that storing the kernel directly in EEPROM lets you skip the bootloader entirely. Bootloaders are usually pretty fast, but they usually have a programmed delay of a few seconds to let you choose a kernel or whatever.
It's not really all that fast. With coreboot there's an option to flash a kernel directly to your bios chip, and skip bios and bootloader entirely. Makes kernel upgrades a pain, of course, but they got wall time from poweron to a working linux shell down to three seconds.
I don't live in a city, you insensitive clod. (And yes, that matters quite a bit in the context)
1600 FLOPs per Hz? That's actually rather impressive.
Huh. I dropped my OLPC from about 4 feet (a little less, maybe 3.5 with some forward momentum too) just a week ago. It bounced to about 1.5-2 feet, then landed again. Outdoors, hard asphalt. No damage except a tiny depression in the plastic on one corner.
Not the first time I've dropped it, either. Only thing I've broken from a drop is a tiny chunk of plastic off the headphone jack--in a ~6 foot drop onto a tile floor that hit the wall and my leg and thus didn't get the full force, but did manage to bend the 1/8th inch headphone connector.
Sounds like Dell has some catching up to do.
A book that I liked when I was younger was To Infinity and Beyond by Eli Maor. It's a sort of advanced layman's look at infinity and the closely-related zero. It includes mathematical topics your students probably haven't seen before (and won't, unless they become math majors), in enough depth to be interesting but not overwhelming (not enough to really be useful mathematically, either just to make them interested and perhaps help them be more comfortable if/when they get to higher math). It also has a lot of history. It seems to be mostly available on google book search (a bunch of random pages missing, but mostly there) so you can check it out without leaving your computer!
"Could spell big trouble for the industry"? Perhaps you mean "could spell big trouble for companies that try to keep using outdated methods"?
Not if you have do download it over a per-megabyte connection.
I'll bludgeon you to death with that exoskeleton's user person!
..."User person"? Seriously, who writes these things?
Actually, I think more important would be that a leopard can climb trees...
I definitely agree. The vast majority of the music I own is from independent labels, and most of it I often listen to an album at a time. I understand that certain formats (where you don't have the listener's attention for long) work better for singles, but music that's meant to be good, and meant to be really listened to, still can and does work better as an album.
Your markup is invalid. Any element or attribute name beginning with the string "xml" is reserved by the spec.
(This is actually a simplification of the truth, see http://www.w3.org/TR/REC-xml/#dt-name for details.)
I've dropped my 89 down numerous flights of stairs, and several feet to the ground more times than I can count (the little plastic bits that hold the cover to the calculator are mostly worn away, so if I pick it up by the cover in the wrong direction it falls out). It still works wonderfully, and I've had it for 6 years.
The worst that happened to it is I think one of the times I dropped it down the stairs the memory reset (probably jarred the batteries and the backup battery at the same time), but only the non-archived memory, so I didn't lose anything important.
Not one that makes sound! (Assuming the sound escapes the building.)
No. Cross-domain xmlhttprequests are blocked by firefox at least, and I'd suspect by other browsers as well. The point is that you don't have to do a cross-domain xmlhttprequest here, since google conveniently stores it in a separate javascript file, and that is embeddable in other pages.
Yeah, it's powerpoint that makes you dumb.
Though I bet they share some code, coming from the same company and all...
Depends on your definition of "flying". I say the pig has to be in the pilot's seat for it to qualify (and I'd hope it's not sedated at that point!)
Uh, I would hope a light was being shone on them. Fluorescence only happens while a UV light is actually shining on the object. Phosphorescence is the one that lasts after the light stops. If there were no light being shone, that would mean the pigs aren't fluorescent.
There can be only one logical reason for this: The straps are filled with explosives!
BOOM!
I think I remember reading about this either on firefox dev blogs or mailinglists or IRC. IIRC, the upshot was that verisign should be doing "extended validation" type things on all their clients. The validation they have now is really pretty shoddy, shoddy enough that they'd be risking getting kicked out if they weren't so big and so many websites would break. But that's just my memory, which could be bad, you'd have to look into it yourself.
Wheee, I'll put my root account on my ipod and then I can take over any box I want! Woohoo!
Except wait. I don't run OSX. I run Linux. And I don't have an ipod.
Oh well.
And after viewing it we find... it wasn't worth it. Just a bunch of "This didn't work. This didn't either. Nor this. And that didn't either. HAIR GEL! THAT WORKED!". No discussion on why or other things to try or anything.
At least it was short.
In the interest of accuracy, canvas was actually implemented by Safari before it was specced. IIRC (I participate in WHATWG but haven't followed canvas closely) a few changes were made between the spec and safari's version, but not many.
Session storage was specced before being implemented, although there was (and still is) editing done based on feedback from the people implementing it.