gmosx

Well, I am using my own templating library, normal-template: http://github.com/gmosx/normal-template

It's similar to json-templates but with a few extra tricks. You can find some documentation here: http://www.nitrojs.org/normal-template

I am not sold on the templating library either. But the Closure library is quite extensive and abstract. It contains tons of useful (and well designed) UI components and compares favorably to something like jQuery UI. On the other hand there is a higher barrier of entry due to the lack of adequate documentation.

I am not sure why you have problems to access the page. Works ok for me. Try again! This has nothing to do with Closure though, it's not used in the page ;-)

I really suggest you buy the book mentioned in the article. The author discuses extensively (and, to me at least, convincingly) the design decisions behind Google Closure.

Even though I bought my Kindle less than a year ago, I am considering switching to the new version. All my wishes are fulfilled in this version:

* WiFi support = blog access, web browser, full content in subscriptions and hopefully lower prices for international users

* better contrast (I found Kindle2's contrast lacking)

* Even lighter

* Better Forward/Backward buttons positioning

* Improved PDF support

Oh, and I love the dark color ;-)

Which library is used to render the PDF file?

And don't forget about crippling the internet by googling Google ;-)

looks cool...

Also check out Bolin's "Closure: The definitive guide" book, available as a rough cut. A great book indeed.

hmm.. AWS is evolving relentlessly, GAE engineers should work harder (and faster) to catch up... It will be an interesting battle (and let's not forget about Microsoft, or even Apple)

great designs. and your blog is truly awesome!

Python is probably a better option than Ruby. If your main interest is the web tech scene, you should probably devote some time to JavaScript.

good and true, html5/css3 innovation started with Apple's work on webkit.

macros cannot implement the whole proposal. but still some kind of macro system may be a worthwhile addition to, say, the closure compiler

I use the Google chrome developer tools. Highly recommended!

Nice article, we want more :)

btw, even with these limitations (I live in Europe), I love my Kindle.

If you live in the US, yes, kindle redefines reading.

If you live in Europe, the device, due to whisper-net limitations is crippled: no images in subscriptions, no simple web browsing, no blogs and the books are often more expensive than the paperback editions (!)

Nah, I think Apple has already chosen JavaScript. Don't forget, Apple actually spearheaded the HTML5 movement...

I would love to see a pure Java version of Cappuccino as well.

In the meantime I use Google Closure. Certainly not the best library but it suits my needs (web applications for the Google Marketplace). Even though it looks ugly at first sight, it is actually an effective solution.

One drawback is the relative lack of support from Google regarding docs, tutorials.

#2 great idea ;-)

I don't have any technical problem with NodeJS.

My problem with NodeJS is that it practically stopped the progress on the CommonJS discussion group, by moving the attention from important issues like a standard library, module transport, etc to non-issues like async. What a pitty...

Great idea, you should probably ask Hannes (the RingoJS lead developer though)

just ignore the nodejs part, then you don't have to like the whole article...

(btw, nodejs and ringojs are on the same side: SSJS)

I thinks it was clear: it's not my product, I am a user of RingoJS. Hannes and the rest of the developers deserve the credit, and the glory...

;-)

comet updates are a niche application

I don't dislike node.js (I don't agree with the direction). I just believe that RingoJS is a better solution for the majority of developers. (NodeJS may be better in niche applications like chat systems, a gaming server etc, even though I believe that technologies like GAE's forthcoming Channel API are even better)

The point of the article is to bring Ringo in the spotlight. I strongly believe that the developers are doing a great job and the seamless access to Java libraries is the great selling point.

If the article generates some (well deserved) attention for Ringo, it will be a success (even if some people do not agree with the wording)

Don't judge the whole article by a single line...

btw, I have a special definition of toy:

6. Why not use NodeJS?

Well, NodeJS is a valid, if over hyped, solution. But it only helps you come up with a toy application. With 'toy' I mean an application that runs on your laptop or your staging server. For a production app you need deployment processes, multi version processes, system setup, server tuning, database scaling, backup processes, security policies, monitoring, profiling, admin console etc, etc. App Engine is the easiest way to go from toy to production (though Heroku-Node may provide a viable alternative).

(from http://www.gmosx.com/blog/agVnbW9zeHIPCxIHQXJ0aWNsZRipwwEM/o...)