I may be wrong - I'm only a regular trek viewer - but I don't remember any trek, even the most recent (Enterprise) or the farthest in the future (future federation timeships in Voyager and Enterprise) that clearly had multitouch interfaces. Touchscreen, yes, but not multitouch as in the typical picture-rotate-and-resize demos we get these days.
If those kinds of interfaces were pictured and imagined since back then, I think they'd have been implemented years back as well. Palo Alto et al were quite the innovators. No, the first occurence of that type of interface I remember seeing is in Minority Report.
- 94.999% of slashdotters will offer "advice" and "informed opinion" without reading the first page and be modded "insightful"
- 5% will post a 10.000 page "summary" and be modded "informative"
- 0.001% (ie. about 1 guy) will actually bother to read the thing and offer genuine insights, and will stanta pede be modded 'troll'.
And I'm not even mentioning the bandwidth issues, but I suppose they could stick it on The Pirate Bay for download...
On the one hand, MS is playing their know-how of flash-and-easy very well here. While we've come a long way in recent years, the Linux desktop is still not quite up to the standard of the Windows one. Too much inconsistency between apps, too many strange design and feature choices, too many simple tasks made unnecesarily complex.
On the other hand, the objective of the OLPC is for the children to LEARN. Their current situation is the best incentive their is for them to *want* to learn as much as possible. After they get done with the easy toys from MS, they'll be starting to want more. They'll drop back into Linux, and find that not only it is actually not quite that hard to learn, but that they are also free to modify it and add to it in whatever way they see fit, and that it allows them to learn a great deal more about computers than Windows.
Additionally, when you look at it objectively, a knowledge of both systems is going to make those children very attractive to the IT market when they come of age. I think, all in all, this is actually a good thing to happen.
>> Anyone with a true gift to become a kernel dev has probably engaged in flame wars with his/her professors already, regardless of what she/he teaches. > Piffle. You are equating software engineering talent with a propensity to participate in shouting (or its equivalent) matches. Those things are, to say the least, incommensurate.
Well... flamewar survival instinct *is* a basic skill on kerneldev:-)
If I understand the summary correctly, they're not saying that the file format is insecure, but that their competitor's application is crap. How is this an apology ?
I notice that the end graphic of 'Duke Nukem Forever' remained on the flag in the old trailer, while in the new one it explodes and takes the flag with it.
Development has been outsourced to Al-Quaeda, it seems.
A reply to all the people posting that it wasn't actually the original mainframe anymore because it had it's parts changed. Top-posting because there's too many of you:-)
Imagine that your grandfather has died, and left you his pocket watch. A beautiful, limited-edition piece, it's worth quite a lot of money, but it's emotional value to you is even greater.
You happily use it for several years, but at some point it shows it's age and stops working. You put it in at a good watchmaker, who replaces a number of parts, and it works again. It is, after all, an old watch, so this happens every so many years. Eventually, you, too, have a look at the daisies from below, and the watch goes to your son. He, too, takes great care of the watch, having it maintained and fixed as necessary.
Eventually, at some point, all parts of the watch, possibly even parts of the shell, will have been replaced.
Now, please tell me at which point it stopped being your grandfather's watch ? I say that your son, and his son, and all those after him will still think of it as the watch that they got from their father, and that once belonged to your grandfather, even though none of the original pieces are in there any more.
Additionally; suppose someone (maybe your brother, who thought he should have gotten the watch) has, over the years collected all the parts that were swapped out, and his descendants did the same; and when they got all the parts, they reassembled them into a watch that, while almost certainly non-functional, is composed of all the pieces that once made up your grandfather's watch. Do they, then, have your grandfather's watch ?
(No, the analogy isn't mine. I *think* I got it out of a Pratchett book, but I'm not entirely sure.)
Not exactly new - the latest incarnation of IBM's WebSphere application server already does this. I should know, we're currently looking into the upgrade:-)
Re:Bet there still isn't a decent "Stop!" button
on
HTML V5 and XHTML V2
·
· Score: 1
Ah, I hadn't seen that, thx.
In that case, I still have a more, well... ideological problem with it: the system is using non-enclosing tags to enclose content. It effectively renders the entire idea of markup by tagged enclosure useless.
This will be a bugger to implement in any standard tree parser, because the opening and closing tags don't match and as such don't actually *mark* the content.
Slashdot Mirror
I may be wrong - I'm only a regular trek viewer - but I don't remember any trek, even the most recent (Enterprise) or the farthest in the future (future federation timeships in Voyager and Enterprise) that clearly had multitouch interfaces. Touchscreen, yes, but not multitouch as in the typical picture-rotate-and-resize demos we get these days.
If those kinds of interfaces were pictured and imagined since back then, I think they'd have been implemented years back as well. Palo Alto et al were quite the innovators. No, the first occurence of that type of interface I remember seeing is in Minority Report.
So while in the "real" world the earth goes around the sun, in the "spiritual" world the sun's soul goes around the earth's soul ?
How strange.
Do I really *have* to delete any ?
Sun Query Language ?
Silicone-based batteries, eh ?
*clamps starter cables on wife's nipples*
Erm... Why does it suddenly say 'silicon' ? *starts running, HARD*
Ehh...
- 94.999% of slashdotters will offer "advice" and "informed opinion" without reading the first page and be modded "insightful"
- 5% will post a 10.000 page "summary" and be modded "informative"
- 0.001% (ie. about 1 guy) will actually bother to read the thing and offer genuine insights, and will stanta pede be modded 'troll'.
And I'm not even mentioning the bandwidth issues, but I suppose they could stick it on The Pirate Bay for download...
Yes, but you don't know you've found that chicken until you eat it, and once you've eaten it, you can't clone it...
> I guess it's a fault of the Unix people from way back.
> They shouldn't have written such reliable software
I knew it! We should have all just shut up and take it dry up the ass from the Gates kid, then none of this would have happened.
> "UKUSA Community"
Now why did I read that as Yakuza community ?
You could probably store pork futures in it, at least until they start solidifying.
So at some point in the future, the fridge and the airco will lower your electricity bill instead of blow it though the roof ? Cool.
On the one hand, MS is playing their know-how of flash-and-easy very well here. While we've come a long way in recent years, the Linux desktop is still not quite up to the standard of the Windows one. Too much inconsistency between apps, too many strange design and feature choices, too many simple tasks made unnecesarily complex.
On the other hand, the objective of the OLPC is for the children to LEARN. Their current situation is the best incentive their is for them to *want* to learn as much as possible. After they get done with the easy toys from MS, they'll be starting to want more. They'll drop back into Linux, and find that not only it is actually not quite that hard to learn, but that they are also free to modify it and add to it in whatever way they see fit, and that it allows them to learn a great deal more about computers than Windows.
Additionally, when you look at it objectively, a knowledge of both systems is going to make those children very attractive to the IT market when they come of age. I think, all in all, this is actually a good thing to happen.
> People who have carry permits are involved in less crimes by percent than sworn police officers...
Well, yes, obviously. Cops are *paid* to get themselves involved wherever crime is committed, aren't they ?
> we're talking about your PROFESSIONAL REPUTATION here. This guy's never gonna work in IT again.
:-)
Yeah, but only because he was sloppy
>> Anyone with a true gift to become a kernel dev has probably engaged in flame wars with his/her professors already, regardless of what she/he teaches.
:-)
> Piffle. You are equating software engineering talent with a propensity to participate in shouting (or its equivalent) matches. Those things are, to say the least, incommensurate.
Well... flamewar survival instinct *is* a basic skill on kerneldev
If I understand the summary correctly, they're not saying that the file format is insecure, but that their competitor's application is crap. How is this an apology ?
> Bugzilla blocks Slashdot referrers
I just (middle-)clicked your link, and it came up fine.
I notice that the end graphic of 'Duke Nukem Forever' remained on the flag in the old trailer, while in the new one it explodes and takes the flag with it.
Development has been outsourced to Al-Quaeda, it seems.
A reply to all the people posting that it wasn't actually the original mainframe anymore because it had it's parts changed. Top-posting because there's too many of you :-)
Imagine that your grandfather has died, and left you his pocket watch. A beautiful, limited-edition piece, it's worth quite a lot of money, but it's emotional value to you is even greater.
You happily use it for several years, but at some point it shows it's age and stops working. You put it in at a good watchmaker, who replaces a number of parts, and it works again. It is, after all, an old watch, so this happens every so many years. Eventually, you, too, have a look at the daisies from below, and the watch goes to your son. He, too, takes great care of the watch, having it maintained and fixed as necessary.
Eventually, at some point, all parts of the watch, possibly even parts of the shell, will have been replaced.
Now, please tell me at which point it stopped being your grandfather's watch ? I say that your son, and his son, and all those after him will still think of it as the watch that they got from their father, and that once belonged to your grandfather, even though none of the original pieces are in there any more.
Additionally; suppose someone (maybe your brother, who thought he should have gotten the watch) has, over the years collected all the parts that were swapped out, and his descendants did the same; and when they got all the parts, they reassembled them into a watch that, while almost certainly non-functional, is composed of all the pieces that once made up your grandfather's watch. Do they, then, have your grandfather's watch ?
(No, the analogy isn't mine. I *think* I got it out of a Pratchett book, but I'm not entirely sure.)
> larger, more complex brains
Why ? Most people already don't use the one they have.
I'm hoping they film The Magician's Nephew (Narnia 0), and get it right when Aslan sings the world into being. Now *that* would be awesome.
> you have to be of above-average capability.
Which, per definition, is approximately half of the population ? I'm sorry, but being 'above average' is nothing exceptional.
Considering how well ducks hide their gonads, I suppose you mean it's very hard to see any performance ?
Not exactly new - the latest incarnation of IBM's WebSphere application server already does this. I should know, we're currently looking into the upgrade
Ah, I hadn't seen that, thx.
In that case, I still have a more, well... ideological problem with it: the system is using non-enclosing tags to enclose content. It effectively renders the entire idea of markup by tagged enclosure useless.
This will be a bugger to implement in any standard tree parser, because the opening and closing tags don't match and as such don't actually *mark* the content.