Google Code Blog

The idea is by no means new. localStorage is old. So is the AppCache specifications that actually allows an application to go 'offline'. Gmail did this as early as 2009: http://googlecode.blogspot.sg/2009/04/gmail-for-mobile-html5-series-us… Unfortunately it's not as easy as it looks. I found that out when doing research for a weekend project. Here's an excellent A List Apart article detailing all the gotchas you can face while working with it: http://www.alistapart.com/articles/application-cache-is-a-douchebag/. The Financial Times Labs have an interesting article talking about an approach to deploying an offline app that uses the AppCache as little as possible: http://labs.ft.com/2012/08/basic-offline-html5-web-app/ And of course you can find information about it in places like Dive into HTML5 and MDN, by simply searching for them

"What's the best language" is a sure fire way to not get any useful answers(because you'll get all possible answers) from a crowd of programmers, IMO. What's "best" for what? Does the safety critical system need to be fast and respond to real time events in real time? Or is it safety critical but is allowed to be slow? What kind of hardware is it running on? Depending on your hardware, the only safety critical language may be assembler, so you can check every single instruction and make sure it's precise. Having said all that, Apollo 11's code was written in a meta-language, then compiled to assembly instructions, then hand-compiled into computer code. You don't get any more safety critical than taking the first men to the moon. http://googlecode.blogspot.com.br/2009/07/apollo-11-missions-40th-anni…

because they can be Because they have to be, due to simple supply/demand. I/O sold out in 20 minutes and some suspect that was even throttled. It's a shame, as the author says, because it tilts attendance in favor of either veterans with deep pockets, or employees of corporations. Good of Google to offer I/O to students at discounted rates; bad of them for not following through with filtering the attendance down to coders: http://googlecode.blogspot.de/2011/11/google-io-2012-extended-to-three…

here is my comment on the google code blogpost http://googlecode.blogspot.com/2011/05/spring-cleaning-for-some-of-our… i recommend posting your disappointment there, too - as google obviously does not care about developers anymore (and so does also not care about hacker news discussions)

Works great on latest chrome beta 64bit linux, GPU Accelerated Compositing, nvidia card, core 2 duo. Uses negligible amount of CPU and seems as fluid as a local OpenGL application. The other webgl examples from http://googlecode.blogspot.com/2010/12/webgl-now-in-beta-here-comes-3d… work pretty well too, although the "previous page" button doesn't seem to work properly, so I have to close the tab.

(I don't know why I keep wandering into this thread; I don't even like Dart, but here goes...) We agree that the browser market of 1995 is not one we want to replicate, but the rest of this is revisionist to a fault. The development of the open web itself has consistently been a messy business. There's a reason that the single-champion model has been adopted by several groups, including TC39: it works really well, and a lot of good standards have come out of it, whether on purpose (many recent specs) or not (many of the features we can thank old IE for). Even when things have been going great, people try to use committee maneuvering to torpedo things, or patent claims come out of the blue and suddenly you're turning to a different champion for your touch events. Pretending that we now have a one true way of developing the open web is silly, because it's not even a little true. > The Canvas spec is a complete steaming pile of nonsense that again, has only been iteratively improved into a more useful state by the tireless efforts of the whatwg (and whoever was maintaining it before them, I don't remember). Canvas delivers miserable performance and a crippled, arbitrary feature set that was clearly designed for the specific purpose of solving whatever problems Apple had at the time. Compare Canvas with WebGL, if you like: WebGL was developed in the open, based on an established, proven API that had been used to solve problems for decades, and it is quickly gaining on Canvas…

I'd rather have Google say "in order for GAE to stay alive, we've had to raise pricing on our current metrics to X", I can understand that, I can justify that, I can compare it and decide how to deal with it/optimize for it, but instead we got, "based on user popular feedback we're radically changing the way we measure usage, then charging some significant multiplier to whatever everybody is already paying so that it no longer makes sense to operate on our platform and you can't even really compare it in such a way as to make sense of the change, then we'll systematically not address anybody who asks us about this in forums or via other communications but we're going to do all this in the most frustratingly passive aggressive way possible" [1][2] Can anybody really believe that popular feedback to Google was "we're not being gouged nearly enough, Google, charge us 2000% more!" [1]http://googlecode.blogspot.com/2011/05/google-app-engine-new-version-a… "Over the last three years, we’ve collected great feedback from our customers and now believe that the biggest thing we can do to help our customers is to graduate App Engine from preview status. " "Adding business features will help App Engine meet a broader set of needs and the new, more transparent pricing model will help customers better align their App Engine investment with their business goals." [2]http://googleappengine.blogspot.com/2011/05/year-ahead-for-google-app-… "App Engine graduating from…

IIRC you used to be able to do this, kind of, with the Google Search Appliance virtual edition: https://googlecode.blogspot.com/2008/11/announcing-google-search-appli…

There's a plugin to run TCL in the browser [0]. Last update appears to be 2006 though, so I doubt it's usable on today's browsers. There was an effort at one time to implement a Dart VM in Chrome [1]. That has been stopped, though [2]. [0] https://www.tcl.tk/software/plugin/ [1] http://googlecode.blogspot.com/2011/10/dart-language-for-structured-we… [2] https://news.dartlang.org/2015/03/dart-for-entire-web.html

Wave was federated/vendor-neutral/client-synced. The federation protocol is described in http://googlecode.blogspot.com/2009/05/hello-world-meet-google-wave.ht… Syncing is described in https://svn.apache.org/repos/asf/incubator/wave/whitepapers/operationa… It was also every bit as buggy and confusing as Lotus Notes.

Many of the open source libraries are concrete implementations of the Java EE specs. Hibernate uses JPA, GUICE standarized the CDI implementation (http://googlecode.blogspot.nl/2009/05/javaxinjectinject.html). And many of the technologies offered by Java EE are standarizations of concepts. This is highly valueable for reuseability and not having 10 libraries completely reinventing the wheel.

This is the original dart language announcement: http://googlecode.blogspot.co.uk/2011/10/dart-language-for-structured-…

Correct. > UPDATE June 3: In the days since we announced the deprecation of the Translate API, we’ve seen the passion and interest expressed by so many of you, through comments here (believe me, we read every one of them) and elsewhere. I’m happy to share that we’re working hard to address your concerns, and will be releasing an updated plan to offer a paid version of the Translate API. Please stay tuned; we’ll post a full update as soon as possible. http://googlecode.blogspot.com/2011/05/spring-cleaning-for-some-of-our…

Not quite sure why this links to the code, and not the top level which has a lot more useful information (such as the simulator needed to run the code). http://www.ibiblio.org/apollo/ There's some more information here: http://googlecode.blogspot.co.uk/2009/07/apollo-11-missions-40th-anniv…

Your claim that it was ever meant to stay "an x86 sandbox" is contradicted by a lot of things, including the actual launch announcement for NACL: http://googlecode.blogspot.com/2011/08/native-client-brings-sandboxed-… " The next milestone for Native Client is architecture independence: Portable Native Client (PNaCl) will achieve this by using LLVM bitcode as the basis for the distribution format for Native Client content, translating it to the actual target instruction set before running. " I actually dislike PNaCL for a different set of reasons, but claiming it was built as an x86 sandbox, and meant to stay that way, is just revisionist history. If you believed otherwise, it was, in fact, your misunderstanding.

This is a blog linking to a blog linking to the source (from 2009). http://googlecode.blogspot.com/2009/07/apollo-11-missions-40th-anniver…

http://www.chromium.org/spdy/spdy-whitepaper has data on improvements in lab tests. http://googlecode.blogspot.com/2012/01/making-web-speedier-and-safer-w… has a blurb where Google announces that they've made search (already highly optimized) faster with SPDY. This is a fascinating result, because this result was obtained after Google Search switched to using HTTPS, which typically makes websites slower, but in Google's case, made it faster because of SPDY. Note that Twitter and Facebook have also adopted SPDY. I'd be rather skeptical that Google, Twitter, and Facebook would all switch to SPDY if there weren't real world benefits.

I'm not the OP, but I don't think he was necessarily talking about the Google Reader API (rather just the service). If you're getting hung up on documented/undocumented APIs, pick any one of the deprecated examples from this list (http://googlecode.blogspot.com/2011/05/spring-cleaning-for-some-of-our… and substitute it in for Google Reader.

They were threatening to do that for last year's meeting, and then backed out on it. There was no test. http://googlecode.blogspot.com/2011/11/google-io-2012-extended-to-thre… In the meantime, be sure to brush up on your coding skills. They’ll come in handy when the new application process opens in February. That’s all we can tell you for now, but we’d advise against making travel arrangements until then.

I am suprised nobody mentioned it already, but the Google Wave Protocol [0] was exactly about bringing some of these properties back to the Web: easily discoverable information, real-time data feeds, decentralization of content, running your own "site", etc. The author said "we've abandoned [these] core values", and this is precisely why Wave failed: people don't care enough about these values. [0] http://googlecode.blogspot.com/2009/05/hello-world-meet-google-wave.ht…

Do not book your flights yet. Remember Google IO 2012... they announced some dates, then a few months later they changed the dates of the event (shifted it a few weeks later). Be careful when you book flights until they officially put tickets on sale. EDIT: http://googlecode.blogspot.com/2011/10/save-date-for-google-io-2012.ht… initially announced on Oct 17, 2011. Changed on November 28, 2011. Dates of the event shifted from April 24-25 to June 27-29, 2012.

Google built such a converter, but it only works with a subset of SWF and ActionScript: http://googlecode.blogspot.ca/2011/06/swiffy-convert-swf-files-to-html…

I suppose [some] Google services may be the server side with Fast Open support: http://googlecode.blogspot.com/2012/01/lets-make-tcp-faster.html

No. Announced October 2011. http://googlecode.blogspot.com/2011/10/google-cloud-sql-your-database-…

You missed the Google Search API :-) deprecated twice: - http://googlecode.blogspot.com/2009/08/well-earned-retirement-for-soap… - http://googleajaxsearchapi.blogspot.com/2010/11/fall-housekeeping.html

Google has various open source offerings (including Rietveld, written by Guido van Rossum, who also wrote Python), see http://googlecode.blogspot.com/2008/07/looks-good-to-me-source-code-re… I have no opinion on any of those, though.

> Enterprise features: Coming later this year, hosted SQL databases, SSL on your company’s domain for secure communications, and access to advanced Google services. http://googlecode.blogspot.com/2010/05/announcing-google-app-engine-fo… (Haha. I just noticed the May 2010 date on the blog post.)

I don't hope for or care for a total re-write; that's up to them. But they should be able to cache all resources with AppCache. They should be able to cache recent messages with LocalStorage. These are not new technologies; they've been around for a couple of years at least. Here's Google discussing their use of AppCache in Mobile Gmail well over 2 years ago.[1] [1] http://googlecode.blogspot.com/2009/04/gmail-for-mobile-html5-series-u…

Google do have a preannounced path throught deprecation to termination and they claim [w]herever possible, the documentation includes suggested alternatives designed to help you achieve similar functionality — whether it’s a new version or related offering. http://googlecode.blogspot.com/2011/05/spring-cleaning-for-some-of-our… In the case of the translation APIs, they were clearly broken and facilitated content spamming, and the replacement APIs appear to be serviceable.