More people are living in urban areas, and urban zones that don't currently warrant a rail system one day will. We may not be retro-fitting current cities, but it doesn't mean that we shouldn't explore new transportation items for developing cities.

Like it or not, the states are not independent. From agriculture to technology, California (really, the whole west coast) and its resources are important to the whole nation. As long as interstate commerce exists, it's in the country's best interest to what it can to safeguard every state and its citizens against natural disaster. Not to mention the fact that the US has federal installations all over (such as military bases), so monitoring programs really are a national concern.

So many libraries exist to help with flaws/lack of functionality in vanilla JS. Perhaps the libraries that come out-of-the-box with Dart get rid of the need for such libraries (though it will probably have its own issues, thus resulting in Dart-specific libraries). And again, the libraries won't suddenly become unusable, as Javascript engines will still exist to utilize them.

The whole point of the "type" attribute in the script tag is that a browser can support multiple scripting languages. The introduction of Dart wouldn't necessitate dropping JS for the browser, but if other browsers implemented it (or Google created extensions for other browsers), it would provide an alternative.

I must have skipped Bible class the day they covered the passages with those events.

PLoS ONE has a high impact factor, and it's gotten there very quickly. In one year it jumped from #25 to #12 in biology journals. And some people publish there because they prefer its business model and want to support openness.

Much of the excitement in football (as in all sports) comes from watching humans with tremendous talent who spend a huge amount of time developing that talent. Like any other sport, strategy is important. But the strategy is partially built around the strengths and weaknesses of the actual humans who make up the team, as well as those of the members of the opposing team. I'm not a huge football fan, but I recognize the difference between multiplying a fairly arbitrary number representing "will" or "skill" by the random roll of a die and a team of people who are fatigued, injured, and withstanding adverse weather conditions, pushing themselves to the utmost limit not only for themselves, but for their team and the millions of people cheering them on towards victory.

When I'm designing a solution, I don't ask if it works, I was if it works well. Is it secure? Is it scalable? What are the risks associated with it? Is it full of kludges that make bad implementations easy? What do I do if a user decides she doesn't trust that functionality and turns it off? And the point of the article wasn't to say that people shouldn't use cookies when developing web site or applications. Rather, it's an examination of how a sub-optimal solution came to be so that perhaps other people can avoid similar pitfalls in the future.

That's not exactly true. While modern printer touchpads have helped out with the situation, push-button systems, generally speaking, aren't as efficient for creating a UI control systems for complex machines. Every time I use one it feels like a kludge, overextending the button interface. On the other hand, a rich widget toolkit (if you have a good UI designer) really can make the overall experience quicker and easier. Not to mention the fact that it would be fairly trivial to set up multiple levels of interfaces exposing on the necessary commands to different classes of users. I consider this more of an evolution of the current printer touch interface than a revolution in printing, but I at least like the concept (can't comment on the implementation since I haven't seen it).

Or perhaps we shouldn't just rely on reciting a litany of facts in hope of winning an argument. Rather, engage in a debate using questions that guide the other person into applying their own logic to the dicussion so that they reach their own reasonably sound conclusion. Don't try to win an argument, let the other person win your argument for you.

I think you're conflating a solitary nature with social ineptitude. It sounds like you do fine in social situations but prefer alone time. When I think of social ineptitude, I picture people who can't recognize social cues, respond appropriately to a social situation, lack of ability to help defuse a potentially volatile situation, etc. This is what can be a problem. Simply liking activities that are more solo or preferring large amounts of alone time aren't in the same category, in my opinion.

My first thought was that this is totally unnecessary and sensationalist use of technology. My second thought was that CNN is going to love this.

1) While it's nice that it has a keyboard dock, it appears that the dock may only support the iPad in portrait mode (they placement of the connector on the long side of the iPad made it seem a bit precarious for putting in a docked mode).

2) Nothing said about mouse support. Seriously, if I'm going to be using it for any type of document creation (and they seem to think people will, as they're providing iWorks in the app store), I don't want to have to use the screen for copy and paste. Lack of mouse support would be a killer for me.

3) Main screen is nothing but icons to get into applications. With more screen real estate there should be support for widgets on the home screen (as I understand it, iPhones and iPod touches don't allow that--one must jailbreak a phone and do it manually).

I'm sure there are more, but those are some things that pop right out at me. As others have said, it really looks like the worst of both worlds. Not as portable as a smartphone, not as good at document creation as a netbook or notebook. eBooks, papers, and mags seem to be the only things to gain from this device.

It depends on how the Exchange server is set up. For industries that demand security, such as healthcare, Exchange servers tend to require that mobile devices support things like encryption and remote wipe. In order for the device to connect, it has to tell the server that it supports any of these capabilities required by the server. Android's default email client doesn't. The Touchdown app does report capabilities back, but it's basically fudging the truth in order to connect (that's my understanding, anyway). Some admins have glommed on to this trick and are refusing to let Android devices connect at all.

So no, Android isn't ready for the enterprise. I have the HTC Eris and love it. I work at a research/teaching hospital, though, and probably wouldn't be able to use it for work. That's fine by me, but anyone who got the phone in order to keep up with work is going to be quite disappointed.