There used to be a site that you browse to in mobile Safari, and it would jailbreak the phone. A potential vulnerability in the app itself is probably what he meant.
333 karma · joined May 13, 2009
There used to be a site that you browse to in mobile Safari, and it would jailbreak the phone. A potential vulnerability in the app itself is probably what he meant.
And that proves my point. The NY Times redesign dedicates lots of space to a new feature that relies on a feature that no one uses. Craigslist is designed specifically to be anonymous to the point where you don't require an account. Putting something that personalizes an account goes against one of the things that made them popular in the first place.
This reply shows that you are posting on the redesign without doing any research. I don't use the events feature, but if you bothered to do any research before commenting then you would see that it is quite popular.
The most cursory research on what the posts are will tell you that most people use the site to get/get rid of something (e.g., jobs, items, sex), or for the community features.
A design that requires marginalizes one of these things to the least visible location is a disaster.
I'm not married to the bad design, and I don't think that a better design would inherently decrease usability; but these specific ones do, and the current design is usable. Uglyness doesn't necessarily mean poor usability.
The designs that change the layout make it less usable by preventing you from seeing everything it has to offer on one spectacularly ugly, usable page.
The design that kept mostly everything the same but modernized the colors, fonts and spacing is still worse that the current site: the current site has an effect of the design dissappearing behind the content, and the redesign has the colors and highlights push past the links and draw my attention away.
What do you suggest in order to deter an innocent man from committing the crime that he never committed?
That doesn't make the definition incorrect; there are many types of polymorphism.
Function overloading is an example of ad-hoc polymorphism; generics is an example of parametric polymorphism; and inheritance is an example of inclusion polymorphism.
Getting random people even benefits the leaders. If the population knows that bad things happen to political prisoners, and that the mildest of protesters are being marked as leaders, then some will lose their nerve.
I did the same thing in SQL Server, too, so it's not a new concept and the other RDBMs with that ability still have a use for traditional stored procs.
My experience with both stored procs and running actual programming languages on the database is that one does not replace the other; but I'll wait with an open mind to see.
Furthermore, I just posted a question there, and in no way had to agree to transfer copyright ownership to them--only rights to reuse the question. Their cease and desist threats are fraudulent.
So desktop apps can't be connected to the Internet?
He even says why they went after Boxee in his article, but doesn't realize it: ". . .can only be used on PCs. Of course, we wouldn’t expect the company to do it any other way — after all, if it ran on set-top boxes, it would dry up the lucrative money stream that flows from cable operators to Hulu’s partners and parents."
Boxee allowed Hulu to be viewed on TVs. Hulu doesn't care that you watched their ads on your computer through Boxee, they cared that people were using Boxee to put it on their TVs.
That's actually exactly what I thought it was about. Your comment, applied to this article, is the perfect explanation of why it is terrible: The presentation isn't about what they want it to be about, but that doesn't make it an arrogant presentation. Google was not doing a product presentation and GigaOm didn't understand it, and got upset when Google dismissed questions irrelevant to what they were presenting.
I/O is a developer conference; talking about the protocol without an actual product is just fine--the demo was good enough to show developers what basic features they can use for whatever product they can imagine.
That demo just shows what you can do. You can't compare it to any existing product. As terrible as this article is, the author does come to the realization that it will be useful for their actual email and office products, however brushing that question off wasn't arrogant; it was a weak denial--a developer conference isn't the right place to talk about their office products.
It is like email--they are both communication protocols. Why would he compare a protocol to a product that uses a different protocol? It's like comparing bittorrent to Firefox.
The creators rightly dismissed the question of monetization because you don't monetize a protocol, you monetize programs built with it. The demo is just one of many potential products that can be built on it, so they can't answer that question based on it.
They rightly dismissed the competition of Sharepoint and Outlook because that was primarily a presentation of the protocol. The demo seemed like something thrown together to show how communication through the protocol looks like, and not the premier application that they will use it for.
I have an idea for potentially using the protocol for a distributed issue tracker that would work well with a DVCS; the protocol is not limited to Outlook and Sharepoint competition.