After reading the excellent ☞ REST Litmus Test for Web Frameworks I was wondering what web frameworks are really passing it.
If you know of any please share it with me. Including links to the documentation/code for each of the points in the post will definitely be even more helpful.
I’ve submitted this question also on ☞ Hacker News and ☞ Reddit. Once I’ll get some results I’ll make sure to start updating this post.
Prepare your wallets for a long list of iPhone apps: 50!
The ones I liked from the post:
… so just a few from the long list. Maybe your wallet is safe though.
I have found an extremely simple and nice trick for using the Safari JavaScript console: the window.console object. It provides a couple of interesting functions:
for(var a in window.console) {
window.console.log(typeof window.console[a] + ':' + window.console[a]);
}
function:function profileEnd()
function:function count()
function:function assert()
function:function warn()
function:function info()
function:function profile()
function:function trace()
function:function timeEnd()
function:function dir()
function:function log()
function:function dirxml()
function:function error()
function:function debug()
function:function time()
function:function group()
function:function groupEnd()
I couldn’t find these functions documentation though.
You can read some more notable news on JavaScript.
John Resig (of jQuery fame) reviews an AJAX tracing tool for Internet Explorer:
dynaTrace provides some information that I’ve never seen before - in any tool on any browser.
An overview of the following JavaScript frameworks and their functions: jQuery, MooTools, The Dojo Toolkit, Prototype, Script.aculo.us, ExtJS, Adobe Spry, BBC Glow, Yahoo! UI Library
An advanced JavaScript tutorial authored by John Resig.
About the ☞ pros and ☞ cons of the ☞ new Google released JavaScript library.
An interesting tool for providing feedback about websites (design, content, etc.). The team behind Notable is also maintaining an interesting ☞ blog. You probably have already seen around the internet other forms of capturing feedback about the site, but most of the time those are just forms or forums integrations, while Notable seems to offer more advanced options.
It is interesting to note how Notable team have started to promote their product. They have picked major websites and used Notable to provide feedback on their design:
You can find a more extensive review of Notable ☞ here.
Another tool I’ve mentioned in the past is LaunchSet which is helping you to manage the whole beta/alpha/private access and data for your new website/startup.
Applying ☞ A/B testing is not as easy as one would think and the results are heavily depending on having a correct, well thought set of metrics. Even more important: these metrics should be actionable metrics
- Any team can create a true split-test experiment that affects only the sandboxed parts of the product, however:
- One team must see the whole experiment through end-to-end.
- No experiment can run longer than a specified amount of time (usually a few weeks).
- No experiment can affect more than a specified number of customers (usually expressed as a % of total).
- Every experiment has to be evaluated based on a single standard report of 5-10 (no more) key metrics.
- Any team that creates an experiment must monitor the metrics and customer reactions (support calls, forum threads, etc) while the experiment is in-progress, and abort if something catastrophic happens.
Looks like Safari 4.0 has better support for HTML5 Input attributes than Firefox 3.5.
A couple of big names — Marissa Mayer (Google), Matt Mullenweg (Wordpress), Eric Schurman (Bing), Jake Brutlag (Google), etc. — talking and showing data about the influence of site performance on users behavior.
I was really impressed by the presentation given by Francisco Tolmasky of 280slides.com and it definitely caught my attention and made me add Cappuccino and Atlas to my list of technologies to try asap
In case you don’t have 28’ to watch the presentation, I’ll try to sum it up for you: ☞ Cappuccino and ☞ Atlas represent the framework and tool to build the future desktop and web applications. Just try to imagine the simplicity of building interfaces with VisualBasic or ASP.NET and combine that with well established technologies like HTML, Javascript, REST and you’d somehow get closer to what Cappuccino and Atlas are proposing. But you’ll have to watch the video to really get what they are. Plus, Francisco is a really good presenter so combining that with the coolness of the product you’ll probably not even feel like 28’.
Here are a couple of links that would get one up to speed to test or develop using the open sourced Tornado Python non-blocking web server and framework:
In what regards the web framework, Tornado seems to sit somewhere between web.py or Google App Engine simplicity and Django feature richness. There isn’t any mention about data storage access, so I assume that you can pick whatever solution you’d like. I must confess that I would still like to see their data access layer considering the storage model FriendFeed is using.
Now, Tornado’s strongest point seems to be its non WSGI compatible, non-blocking web server implementation, which seems to perform quite well (at least for those trivial tests).
With the published performance metrics ☞ and keeping in mind it is Python, I’d say it is definitely something that a web developer should check.
