"I wonder if they could combine the keyboard with the touch surface. Not by having the surface be the keyboard, but by overlaying a traditional keyboard with touch sensitive key-sized tiles that together make a touch-sensitive area. Keys should still be pressable, but when you treat it like a touch surface it should behave so. If the gaps between keys are snall enough it should work for fingers. (not styluses though)"
- alexandros marinos
"First Microsoft/Danger/Sidekick, then Apple, now this. We need a computing paradigm that does not suffer from single points of failire, or at least fails more gracefully."
- alexandros marinos
"disclaimer: I am an author of the paper (but not the blog post). The title is a bit dramatic but the content conveys the idea relatively clearly. If you need more information, the paper is linked to at the bottom of the article."
- alexandros marinos
"Thanks for the report, Anonymous. I would have thought that they would deactivate the folder as you said as well. Maybe this protection kicks in after a certain amount of traffic?"
- alexandros marinos
"I have immense respect for those working under google's shadow to create a better/different search experience. The article clearly shows that their entire product development strategy is built around what google does and does not. Although as history has shown, when these companies accomplish anything they usually get acquired rather than becoming individually successful. But I guess history can only take you so far and Google was once a search underdog. So good luck duckduckgo!"
- alexandros marinos
"I suspect the author is lead astray by his comparison of codeplex to google code or sourceforge. The better comparison is the Apache Foundation, the Eclipse Foundation, the FSF or perhaps MySQL. The latter two also request copyright assignment. While I think that Microsoft should have erred on the side of more freedom, things are not nearly as bad as the author makes them out to be."
- alexandros marinos
"anyone know why there is 'loading' activity whenever I select text on the page? I noticed the same effect on yesterday's esquire articles as well."
- alexandros marinos
"transactions are unnecessary, unless you are looking for 100% consistency between cache and database at all times. Usually this is not the case and if it is, you will have extremely serious problems scaling. All i'm saying is: If you have an update that you know will invalidate some cached pages, why invalidate them and then rerender them from the database once the update is commited instead of updating them directly. and lazy queueing the update, taking the load of the database (less pressure to commit instantly, and less reads). In the facebook inbox example, you know that a new message to the user will increase their message count by one. Just update the cache directly with this new info. When/if it explodes, by all means, rerender everything."
- alexandros marinos
"Intresting read.. It seems it never did make it to the PC/AT line though. "The 80186 would have been a natural successor to the 8086 in personal computers. However, because its integrated hardware was incompatible with the hardware used in the original IBM PC, the 80286 was used as the successor instead in the IBM PC/AT.""
- alexandros marinos
"I wonder if anyone's gone the next step and written updates to the caches directly, leaving out the database write from the critical path."
- alexandros marinos
"The article mentions that the explicit unsubscription of PuSH is an advantage over the implicit approach of rssCloud. With garbage collection being a major problem of publish/subscribe in distributed systems, the author needs to mention how PuSH deals with it in order to assert superiority. Without acknowledging it, the credibility of the article is limited"
- alexandros marinos
"I was hoping it would be google that would step up to the plate, not facebook to be honest. The friendfeed team is a serious weapon for facebook to wield against google and I don't know why the FF guys would enter this war, on this side. Maybe Google did something to piss them off? On the plus side, the FF guys will now get paid for the FB dev work they have been doing anyways. If I recall correctly buchheit was also involved in adsense, another pain point for facebook. Also the real-time search assets that fb would get from ff may fill the goals that facebook had with the attempted twitter acquisition. The plot thickens..."
- alexandros marinos
"Well, Roy has a way of describing things from a Systems Engineering perspective. that can confuse when read from people with a different context. I think where HTTP digest etc. comes in is the 'successful mapping' bit. While the abstract API should not specify HTTP digest, the materialised API that people actually use (the mapping of the API onto HTTP) should."
- alexandros marinos
"First author of HTTP 1.1 is Roy Fielding, same guy who defined REST. In fact, http 1.1 was designed largely to make HTTP restful. As such, you'd be surprise how far HTTP goes towards RESTfulness. For instance the spec defines idempotency and satfety of methods. Ergo, servers may produce valid requests and responses but still fail when it comes to being valid http if their internal operation does not conform to the operation semantics. Look up the google web accelerator fiasco to see how things can go terribly wrong."
- alexandros marinos
"Most APIs are not restful because their designers had more important issues - Would you say the same for most web pages breaking web stanards or is that another matter entirely?"
- alexandros marinos
"RESTful interfaces should NOT be ptotocol independent. While REST can be implemented over multiple protocols, a RESTful interface is by definition tightly coupled to the protocol it goes through. For instance REST specifies that we should use a uniform interface, but HTTP tells us what that interface is, and a REST over HTTP interface (the most common RESTful interface) has to respect that. I would be interested in where you read this fielding quote as this 'protocol inependence' and its problems is a common charge he makes agains WS-* if anything."
- alexandros marinos