I agree, I really like the automatic updating that Chrome uses.
I think that both Firefox and IE will eventually change to that model also. It gets out security patches more quickly, ensures that most everyone is using the latest renderer, has the latest features, and best of all doesn't nag me about updates.
There are definitely disadvantages to automatic updates, but for me personally I find the advantages too tempting to go back.
Agreed, also the ingredients used for the top sellers should be fresher since they are being consumed at a greater pace. This reminds me of how Krispy Kreme has one item that they are known for, the glazed donut, which brings in customers who they are able to sell milk, coffee, and other assorted donuts.
I agree, it sounds as though they are "reeducating" him into a white hat and not necessarily hiring him on as a employee. It would surprise me if they actually hired him right now because he had set up a phishing scam. It is good though that they are working with him vs throwing the book at him especially for one so young.
I would be very interested in seeing how many developers would pay for the Translate API if Google had decided to monetize it instead of deprecating it then shutting it down as some of the commentors on the blog had suggested. At the same time if the Google Translate API is such a popular service then maybe there is enough demand to support a startup providing a Translate API ;)
Starting a startup to replace Google Translate wouldn't be a simple proposition. Google's translation algorithms are considered best-of-breed and involve highly sophisticated statistical machine learning trained over a significant portion of their web crawl corpus data. Their staff scientists and engineers working on Translate are some of the best in the field, and the complexity here should not be underestimated. That said: yes, there's very obviously an opportunity here for the right team; but that opportunity is so big, its been there this entire time, even with the Google Translate API around.
Right... Some problems are fine just throwing resources at them, some problems need experience and knowledge, and in my opinion, you're not going to get the intellectual capital you really need for something like this, especially with a lean startup, unless you are the intellectual capital.
I wonder how much work it would be for Google to build a "Translation appliance" people could buy? I'd wager they'd do $100million in government sales alone the first year.
I commented on a different story about the API changes (specifically Translate) and thought I'd been stupid to miss a big "DEPRECATED" message when I started out several months ago. Seems there was nothing to miss!
I (or more specifically, the client) would certainly pay for something like this. If anyone does have a replacement that is roughly as simple to use and isn't £1000/mo then you have a customer right now.
I would pay for what I use which isn't a whole lot, but it will be hard to find a programmable replacement like the Translate API. It's also a little hard to believe that it was a "financial burden" for one of the richest corporations in the world.
They have something like 37 Billion dollars in retained earning and don't pay a dividend. They didn't get that mountain of cash by losing money on things.
Assure yourself, if you are using a free google-anything, somehow or other, it adds to their income.
I think it will be more interesting/telling to see the numbers that Microsoft post after Nokia begins to ship phones with WP7 on them. While WP7 is not a popular choice right now, the Nokia partnership definitely makes it interesting to watch.
I am especially curious to see how Nokia leverages the WP7 platform in countries outside of the US because of Nokia's global market share and marketing.
I'm interested too. Nokia hasn't been able to sell many Maemo phones, I'm not sure how having Windows Phone 7 would really improve that. They seem really good at selling cheap phones, but not smartphones. Maybe with Microsoft's marketing muscle they'll do better.
I am definitely working hard to experience all of the mentioned "joys" :) I find developing software is a lot of fun because as long as you work hard enough it is within reach to create something that a lot of people will use and enjoy.
District 9 was a great movie I am glad it won the BitTorrent Oscar ;) I am surprised Avatar was downloaded so many times considering that it wasn't a very good movie aside from its visuals.
This made me think of this Leo Laporte caller http://www.youtube.com/watch?v=S0zt4opqL18 :) Personally I disagree with the author’s stance on the unlocked door analogy. The author argues that there are no physical characteristics to identify a wireless network’s ownership and a default ssid with no security can only mean that its intention is for public use. I argue that unless the user specifically knows the intentions of a particular wireless network then they must by default assume that it is a private wireless network regardless of the ssid and security used. Using the unlocked door analogy if every house in a neighborhood was the same color and had their doors open does that mean a person should by default assume that every home is for public use?
While I do agree that development, build, and testing shouldn’t rely on a single IDE/toolset, I have to admit that I really do enjoy the explorative properties of many of the current IDEs for Java, C++, and C#. When I need to dig through foreign code I always find it a lot easier to do it using a IDE that has good jump and search capabilities like Eclipse.
