Google Code Blog

so i actually watched this and marcus nelson is quite informative giving you an interesting behind the scenes on his startup, uservoice, from the pre-first-dollar-angel days to the most recent 800k round. what initially caught my eye was the association of uservoice with google via their openid integration ( http://google-code-updates.blogspot.com/2009/05/google-openid-api-taki… ). then when i got to their site i realized they are the people behind the little floating feedback tab on what seems to be more and more websites out there. after that, i just had to take a look. the convo does not have any tech details behind their product/platform but rather the soup to nuts story of how they went from a shoestring to getting enough funding to make it happen. worth a listen if you are either working on getting funding or thinking about it.

Ok, great. Now. For Mozilla's own sake I really hope this lovely feature comes disabled by default. PS. To get an idea of what it is have a look here - http://google-code-updates.blogspot.com/2009/04/google-location-servic…

I think you've missed the mark on a few points. As far as I know safari has the fastest javascript engine no matter where it runs, including ARM. It also supports local storage without google gears, buy using html5 local storage. With html5 I'm not sure what the point of gears is. As far as native client is concerned regarding ARM, it'll probably happen but not because of the iphone and android, they have ways of running native apps. Apple wants you to use the app store and as far as I know android locks you into a vm so you'd need to write custom code anyway. It'll be for chrome os on netbooks. http://www.techcrunch.com/2009/06/24/iphone-3gs-javascript-performance… http://webkit.org/blog/126/webkit-does-html5-client-side-database-stor… http://google-code-updates.blogspot.com/2009/05/gmail-for-mobile-html5…

Yep, you are right, FF 3.5 is being provided with location by the Google Location Service (http://google-code-updates.blogspot.com/2009/04/google-location-servic… Also, this service implements http://dev.w3.org/geo/api/spec-source.html, which should, once widely adopted, void the need of a wrapper library such as geo.js posted here. Edit: Typo

Yes: http://google-code-updates.blogspot.com/2008/12/native-client-technolo…

Above link is part 1; it gets into mobile phones at about -26:00 Part 2 is here http://google-code-updates.blogspot.com/2009/04/ppk-open-web-goes-mobi… and it starts off right away in mobile browsers

Um... I think GWT will kill them all. http://google-code-updates.blogspot.com/2008/12/google-web-toolkit-out…

There's also some good info on what you can do with it at http://google-code-updates.blogspot.com/2008/11/announcing-google-sear…

Actual link: http://google-code-updates.blogspot.com/2008/10/google-moves-towards-s…

Read the original article on Google's Blog http://google-code-updates.blogspot.com/2008/10/google-moves-towards-s… They don't want to add just another OpenID to the mix. They want to leave people with the same signup procedure they're used to (ie. enter your email). However, if they enter an @gmail.com address, the server automagically figures out how to log them in using OpenID. It's a good idea in theory, but seems like it will require a fair amount of rewrite on the OpenID library side. Not a big fan of that...

My first reaction was "no - gears has been out for ages"... but no, you're totally right. Gears + Android might be an interesting play for Google as well. http://google-code-updates.blogspot.com/2008/03/power-up-your-mobile-w…

The problem is that Microsoft inversely gains from improving the ease of browser development. The easier it becomes to develop software using open source tools(No Visual studios) on an OS-independent platform(The web with browsers) the less money they make. Google's recent project (Native Client) is what I've been waiting for as a C++ developer. It basically allows you to run native code(assembler) in browser. But then has security mechanism so that the code cannot do anything to the client computer unless the user of that client has given the container(Sandbox) that runs the code permission. This will allow people to build their own UI frameworks, that render much more rich graphics and hopefully behave the same no matter what Browser/OS combination you are running on. References: Announcement: http://google-code-updates.blogspot.com/2008/12/native-client-technolo… Native client code base hosted at Google code: http://code.google.com/p/nativeclient/ Ars Technica review: http://arstechnica.com/news.ars/post/20081209-safer-than-activex-a-loo… Do people really think we'll ever reach a point where different vendors building code-bases based on documentation built by a committee will ever behave even remotely the same? Have you read any of the W3C documentation, it's fucking ridiculous. We should be sharing implementations, it's the only way to ensure bit-level identical behavior of a target system(Performance…