Digital Assistants Continue to Lose Ground
420808
Shipments of personal digital assistants declined for the third consecutive quarter as large vendors continued ceding the depressed market to smaller electronics makers, the research firm IDC said Wednesday.
631685
With the closure of IETF&#39;s MARID group a month ago, many of us have left Microsoft&#39;s Sender-ID standard for the dead. After being rejected by the Apache Foundation and the Debian Project over licensing issues
579074
Worker apathy about PDA security is putting corporate data in jeopardy. The storage of the names and addresses of corporate customers on PDAs is now common - but security practices are struggling to keep up with technology usage.
503621
Over the last 24 hours Twitter has been down as much as it's been up. As always this gives us a reason to think about what the world would be like without Twitter and then those of us who are engineers or would-be engineers, start thinking about ways to fix the problem, whatever it is. The Twitter folk say that the recent problems are related to an infrastructure overhaul. Of course I believe them, I take it at face-value. I think the MacWorld Expo outage was about traffic, I don't think last night's Republican debate took Twitter down. Anyway, I'd like to really understand what's going on behind the scenes at Twitter, Inc. They say they're confident the new infrastructure will hold up better, I'd like to understand why. Can we have a meeting, with a few people from the tech community who actively use Twitter and a few people from the company, to be briefed on what's going on. The same way the President briefs Congress when there's some kind of international crisis.  Twitter wouldn't exist without its users. Everyone wants to know what's going on. Let's have some real honest direct communication?
210482
Past attempts at a high-tech quill have ended up as expensive paperweights, but a new crop of start-ups has higher hopes.Photos: Pens get smarter
63955
Can CA reinvent itself? Computer Associates (CA) have had a pretty miserable time over the past few years. I guess they felt like the underpaid and overworked airport staff at New York's JFK airport as I came through on a flying visit to catch up on their latest news.â¦
415412
This scenario is all too familiar to office workers who collaborate electronically on projects: E-mails get passed around with differing versions of documents-in-progress attached. Instant messages whizz by. Web sites are cited, then lost. It's often a jumbled mess, with no central online location for shared data. There must be a better way.
470677
Apple computer users are frustrated by a lack of available online backup services for their systems.
610671
Also: Mobile office challenge finds monkeys are distracting. Read these stories and more from around the Web on News.com Extra.
715363
There simply isn't enough IT talent to go around, and the problem is only going to get worse. This generation is all about the application, and nothing about the infrastructure that supports it.
650846
Is the desktop dead?  Microsoft can't even make its updates sexy anymore.
309918
If you&#39;re a computer user, you may have several of them stacked on your desk. We&#39;re talking about floppy disks - and they are pretty much becoming extinct.
140465
Work on bridging the gap has stalled Movement on the digital divide has stalled with only marginally more people online today than three years ago.â¦
618613
Service Oriented Architecture isn't getting any easier despite the raft of acquisitions.
139397
Blog: Microsoft has screwed up yet another standards effort.  This is getting old.
89199
In this call center, all the PCs are configured identically. But one user's machine locks up several times a day, and new hardware and software don't help. ...
385505
When Amazon introduced S3 a couple of years ago I knew I would useit and I was sure a lot of other developers would. I saw it as a solution to a problem we all have -- storage that scales up when needed, and scales down when not. Otherwise we all have to buy as much bandwidth as we need in peak periods. With S3, you pay for what you use. It makes storage for Internet services more rational. Later they did the same for processors and queuing. And a couple of days ago they announced a lightweight scalable database, using the same on-demand philosophy and simple architecture and API. It's going to be a huge hit and forever change the way apps are developed for the Internet. I was explaining the significance of this to Scoble on the phone this morning. It's worth repeating here. When I developed Frontier in the late 80s and early 90s my target platform was a modern desktop computer, a few megabytes of RAM, a half-gig of disk, a few megahertz CPU. A system capable of running Quark XPress, Hypercard or Filemaker. It would be used to develop apps that would drive desktop publishing. Later, it was used to generate static websites, then a demonstration of democracy (a multi-author ultra-simple CMS), then news sites, which became weblogs, then blogs, and editthispage.com, Manila, weblogs.com, and that's when scaling became an issue. (Later we side-stepped the scaling issue by moving most of the processing to the desktop with Radio 8.) As we approached then cracked ease of use in web authoring, scaling became an issue, then the issue. A Manila server would work fine for a few thousand sites, but after that it would bog down because the architecture couldn't escape the confines of a single machine it was designed for in the 80s. (Before you say it's obsolete, there still are a lot of apps for single machines. Perl, Python, JavaScript and Java share the same design philosophy.) Same with weblogs.com. It worked great when there was a few thousand blogs. Once we hit 50K or so, we had to come up with a new design. Eventually we were tracking a couple million, and Frontier was hopelessy outclassed by the size of the problem. If only Amazon's database had been there, both Manila and weblogs.com could have been redesigned to keep up. It would have been a huge programming task, but it would have made it economically possible.  Today, when a company raises VC, it's probably because their app has achieved a certain amount of success and to get to the next level of users they need to spend serious money on infrastruture. There's a serious economic and human wall here. You need to buy hardware and find the people who know how to make a database scale. The latter is the hard problem, the people are scarce and the big companies are bidding up the price for their time. Now Amazon is willing to sell you that, to turn this scarce thing into a commodity, at what likely is a very reasonable price. (Haven't had time to analyze this yet, but the other services are.) Key point, the wall is gone, replaced with a ramp. If you coded your database in Amazon to begin with you will never see the wall. As you need more capacity you have to do nothing, other than pay your bill.  Further, the design of Amazon's database is remarkably like the internal data structures of modern programming languages. Very much like a hash or a dictionary (what Perl and Python call these structures) or Frontier's tables, but unlike them, you can have multiple values with the same name. In this way it's like XML. I imagine all languages have had to accomodate this feature of XML (we did in Frontier), so they should all map pretty well on Amazon's structure. This was gutsy, and I think smart.  They're going down a road we went down with XML-RPC and then SOAP. There may be some bumps along the way but there are no dead-ends, no deal-stoppers. All major environments can be adapted to work with this data structure, unless I'm missing something (standard disclaimers apply). Their move makes many things possible. As I said earlier, if it existed when we had to scale weblogs.com, we would certainly have used it. One could build an open identity system on it, probably in an afternoon, it would be perfect for that. A Twitter-like messaging system, again, would be easy. It's amazing that Microsoft and Google are sitting by and letting Amazon take all this ground in developer-land without even a hint of a response. It seems likely they have something in the works. Let's hope there's some compatibility.