Case in point; Many japanese doesn't have a PC nowadays, but they do have cellphones. I don't know how it looks like in other Asian countries like South Korea and Malaysia, but it wouldn't surprise me to see similar situations.
More like, past experiences.
It's happened every single time before, why should this time be different? I don't trust Microsoft for a reason. They've shown me time and time again that they're backstabbing lying bitches ever since the days of DOS, and been convicted of foul play atleast twice. So forgive me if I don't trust them. Because I really don't.
Silverlight might as well be. I for one don't trust Microsoft will keep up their cross-platform commitment in the slightest; As soon as it's beaten Flash to the ground, the Mac version will mysteriously disappear and the Linux version will be lacking any significant modules. And all other platforms are unable to play the content.
This way, only the sites which utilize a *full* doctype and are at the same time *nonstandard* are affected, and could possibly break. And if it breaks, it's an easy fix (just do a find/replace: s/<head>/<head><meta value="use-ie7-engine">/g)
Wait, doesn't this mean the developers of those legacy pages have to actually do some work???
Yes, it does. Indeed it does. But if those developers claiming standard-compliance by using the full doctype had done their job properly to begin with, this would be a non-issue. It's a simple fix for legacy code, doesn't break any sites in quirks mode, and more importantly doesn't break those sites people managed to get right. Why should I have to be punished for following the open standards of the web? Standards all browsers worth their salt claims they can handle?
Google has said that once the standard is more stable, they'll fix their implementation to match. Whether they'll keep to that promise or not remains to be seen.
Incidentally, Jingle is slated to go draft (e.g. "release") this month. Once it has gone draft, it's generally considered stable enough to implement. So, that's more or less what the whole Jabber community is hoping for.:)
I disagree that a closed approach is neccessarily a bad thing.
Regarding "Elephant's Dream", it is *supposed* to be a surreal story. I'd like to argue that these kind of movies are good simply because they aren't mainstream. Oh, sure, it doesn't make sense. But it's artistic value is interesting, nonetheless. Elephant's Dream isn't your standard run-of-the-mill Hollywood movie with good plot, likable characters and clichéd and overused plot conventions, simply because it's not a Hollywood movie and it was *never meant to be one*.
Now, some things lends itself well to cathedral building. For direct consumables that take a long time to create, such as novels, movies and single-player games, it's still the best model I've found. An open process is destined to become a watered-down mainstream soup. When it comes to script writing, it's far more beneficial to have one person write the Script, ask for input among some peers, revise as neccessary, clarify that which needs clarifying, and then send it off to production. You get a much more coherent vision. Just imagine what would've happened if the Lord of The Rings were written by a community. Not a pretty sight, I tell ya.
There's some value in an open model, but when it comes to script writing, just... No.
The users can modify the laptop's operating system, a special version of Red Hat Linux running the new Sugar graphical user interface and operating on top of LinuxBIOS and Open Firmware. The original system remains available in the background and can be restored.
So, it would appear MS do not have a choice in the matter, since the BIOS cannot be altered without substantial effort (requires a developer key) and that is what controls the fallback mechanism.
You may not be able to log in to your LJ Talk server with your gmail account - But there should be nothing stopping you from adding LJT users to your contact list on GMail, and vice versa.
Jabber isn't one network, true, but many networks working cooperating through open standards. Pretty much the same thing the World Wide Web, email and internet at large works.
IIRC Crossbows were actually created to penetrate breastplates. That's why we don't see any full-armor knights anymore - the crossbow (and later rifle) made them obsolete.
Teenage boy gets sued for trespassing on private property (or worse), mr pedo goes to jail. In this case *both* persons commited a crime (the Teenage boy was trespassing, the pedo was molesting a child), and one right does not equal one wrongdoing (although it might lead to an easier sentence).
However, what happened in the case of the OP is more akin to, say, the pedo going on vacation for two weeks, giving the keys to the teenager so he can feed the fish, and leaving a bunch of pictures under the sofa or in a drawer. They're out of sight, but, say the teenager wants to be a bit helpful and clean the aquarium, and these pictures are in the drawer directly underneath the aquarium? It's not too far-fetched to think that the teenager would look for aquarium-related stuff in that drawer underneath the aquarium. That's where I would put things like that atleast. Teenager walk free, pedo goes to jail, atleast in my perfect world.:p Of course, YMMV.
Maybe eventually we all will have to be there, but there always seems to be workarounds that work for everyone, minimal hassle, minimal pain.
This is not the case in my experience.
Actually, a lot of things are wrong with the current IPv4, but my biggest pet peeves are NAT and Multicasting. Multicasts won't happen until IPv6, simply because in IPv6 it's mandatory, IPv4 it's optional to implement, which leads to poor support for it. NAT sucks for anything that wants to establish a connection between two computers behind NATs. They require much more management than IPv6. Cross-site VPNs are a total pain in the butt when it comes to NAT handling. ICE, STUN and TURN are a hack upon a hack and makes applications much more complex than they need to be, etc.
I for one welcome our new IPv6 overlords.
Disclaimer: IAANGP (I Am A Networked Games Programmer)
Slashdot Mirror
Case in point; Many japanese doesn't have a PC nowadays, but they do have cellphones. I don't know how it looks like in other Asian countries like South Korea and Malaysia, but it wouldn't surprise me to see similar situations.
More like, past experiences. It's happened every single time before, why should this time be different? I don't trust Microsoft for a reason. They've shown me time and time again that they're backstabbing lying bitches ever since the days of DOS, and been convicted of foul play atleast twice. So forgive me if I don't trust them. Because I really don't.
Silverlight might as well be. I for one don't trust Microsoft will keep up their cross-platform commitment in the slightest; As soon as it's beaten Flash to the ground, the Mac version will mysteriously disappear and the Linux version will be lacking any significant modules. And all other platforms are unable to play the content.
You mean they had them in stock all the time before you told Slashdot where to get one?
They could, however, go the other way around;
This way, only the sites which utilize a *full* doctype and are at the same time *nonstandard* are affected, and could possibly break. And if it breaks, it's an easy fix (just do a find/replace: s/<head>/<head><meta value="use-ie7-engine">/g)
Wait, doesn't this mean the developers of those legacy pages have to actually do some work???
Yes, it does. Indeed it does. But if those developers claiming standard-compliance by using the full doctype had done their job properly to begin with, this would be a non-issue. It's a simple fix for legacy code, doesn't break any sites in quirks mode, and more importantly doesn't break those sites people managed to get right. Why should I have to be punished for following the open standards of the web? Standards all browsers worth their salt claims they can handle?
Google has said that once the standard is more stable, they'll fix their implementation to match. Whether they'll keep to that promise or not remains to be seen. Incidentally, Jingle is slated to go draft (e.g. "release") this month. Once it has gone draft, it's generally considered stable enough to implement. So, that's more or less what the whole Jabber community is hoping for. :)
I disagree that a closed approach is neccessarily a bad thing.
Regarding "Elephant's Dream", it is *supposed* to be a surreal story. I'd like to argue that these kind of movies are good simply because they aren't mainstream. Oh, sure, it doesn't make sense. But it's artistic value is interesting, nonetheless. Elephant's Dream isn't your standard run-of-the-mill Hollywood movie with good plot, likable characters and clichéd and overused plot conventions, simply because it's not a Hollywood movie and it was *never meant to be one*.
Now, some things lends itself well to cathedral building. For direct consumables that take a long time to create, such as novels, movies and single-player games, it's still the best model I've found. An open process is destined to become a watered-down mainstream soup. When it comes to script writing, it's far more beneficial to have one person write the Script, ask for input among some peers, revise as neccessary, clarify that which needs clarifying, and then send it off to production. You get a much more coherent vision. Just imagine what would've happened if the Lord of The Rings were written by a community. Not a pretty sight, I tell ya.
There's some value in an open model, but when it comes to script writing, just... No.
Taken from Wikipedia (emphasis mine):
So, it would appear MS do not have a choice in the matter, since the BIOS cannot be altered without substantial effort (requires a developer key) and that is what controls the fallback mechanism.
You may not be able to log in to your LJ Talk server with your gmail account - But there should be nothing stopping you from adding LJT users to your contact list on GMail, and vice versa.
Jabber isn't one network, true, but many networks working cooperating through open standards. Pretty much the same thing the World Wide Web, email and internet at large works.
And what exactly would prevent port blocking for the interfaces instead of the ip addresses? ip filter to eth0:0-65535 from eth1
Lua is used in many Game projects, atleast in my experience.
Seriously. ALSA is a mistake and should be treated as such. Get OSS4 instead.
Incorrect.
IIRC Crossbows were actually created to penetrate breastplates. That's why we don't see any full-armor knights anymore - the crossbow (and later rifle) made them obsolete.
I'm not the parent, but in this case;
:p Of course, YMMV.
Teenage boy gets sued for trespassing on private property (or worse), mr pedo goes to jail. In this case *both* persons commited a crime (the Teenage boy was trespassing, the pedo was molesting a child), and one right does not equal one wrongdoing (although it might lead to an easier sentence).
However, what happened in the case of the OP is more akin to, say, the pedo going on vacation for two weeks, giving the keys to the teenager so he can feed the fish, and leaving a bunch of pictures under the sofa or in a drawer. They're out of sight, but, say the teenager wants to be a bit helpful and clean the aquarium, and these pictures are in the drawer directly underneath the aquarium? It's not too far-fetched to think that the teenager would look for aquarium-related stuff in that drawer underneath the aquarium. That's where I would put things like that atleast. Teenager walk free, pedo goes to jail, atleast in my perfect world.
Disclaimer: I am not a lawyer
This is not the case in my experience.
Actually, a lot of things are wrong with the current IPv4, but my biggest pet peeves are NAT and Multicasting. Multicasts won't happen until IPv6, simply because in IPv6 it's mandatory, IPv4 it's optional to implement, which leads to poor support for it. NAT sucks for anything that wants to establish a connection between two computers behind NATs. They require much more management than IPv6. Cross-site VPNs are a total pain in the butt when it comes to NAT handling. ICE, STUN and TURN are a hack upon a hack and makes applications much more complex than they need to be, etc.
I for one welcome our new IPv6 overlords.
Disclaimer: IAANGP (I Am A Networked Games Programmer)