[null, null, null, {"document_url": "http://blog.mchv.me/2012/03/solar-web-experiment.html", "unformatted_src": "http://3.bp.blogspot.com/-Ek3EllMJpuQ/T1oyLgNNz7I/AAAAAAAAAeE/fyY9H2soHdE/s320/Screen+shot+2012-03-09+at+5.35.53+PM.png", "src": "http://3.bp.blogspot.com/-Ek3EllMJpuQ/T1oyLgNNz7I/AAAAAAAAAeE/fyY9H2soHdE/s320/Screen+shot+2012-03-09+at+5.35.53+PM.png", "formatted_filename": "Screen shot   at", "rendered_width": 320, "rendered_height": 217}, null, null, null]


As someone interested by tooling, I often think about how to reduce frictions between the developed applications and the development tools. In other words, how to reduce the context switching cost. For two weeks, I have started to work on a new experiment, named Solar, a play module to work on your play applications directly in your browser. I have been largely inspired by Orion and Erwan module, but I had specific goals, that's why I did not reuse most of those projects code. Actually, I would like to focus on several concerns:
