robertkrahn01

18 ms·

1. 151.▲
   Emacs + scala(beltmogul.blogspot.co.nz)

   2 points by robertkrahn01 13y ago|0 comments
2. 152.▲
   by robertkrahn01 13y ago

   Another Spritz-like implementation: http://lively-web.org/users/robertkrahn/speedread.html
3. 153.▲
   by robertkrahn01 13y ago

   East Palo Alto Struggles to Remain Affordable for Low-Income Residents [ http://www.kqed.org/a/forum/R201401171000 ]
4. 154.▲
   by robertkrahn01 13y ago

   Well, my personal pov is that for certain prototyping requirements component systems are actually a good fit because they make it easy to rewire thinks quickly and to easily plugin/replace strategies (as in strategy object). In this re
5. 155.▲
   by robertkrahn01 13y ago

   A must have architectural pattern for such a list: "Entity Component System" http://en.wikipedia.org/wiki/Entity_component_system
6. 156.▲
   by robertkrahn01 14y ago

   Great to see LK come up here. Yes, the approach of Lively goes towards what is mentioned in the article, right now however, the client session (what you run in the JS VM in your browser) is what the image is for Lively. We developed a persi