Profile cover photo
Profile photo
Seva Adari
About
Seva's posts

Post has attachment
..... Google has habitually made wise decisions, so what could this lunacy really be all about?
http://www.pcmag.com/article2/0,2817,2415756,00.asp

Post has attachment

Post has attachment
Andy Wilson of VoltDB gave a talk (Triangle JS meetup at WebAssign) on "Building Scalable Node.js Apps with VoltDB". Much of the talk was devoted to benchmarking. Interestingly Java driver is screamingly faster than the Node.JS driver (in terms of number of transactions).

Post has shared content
Last month I had the pleasure of seeing John Hughes talk about QuickCheck at Software Passion Summit 2012 in Götenburg, Sweden. QuickCheck is one of those brilliantly simple ideas. It was first done in Haskell. It inspired me to try to do it in JavaScript.

Post has shared content

Post has shared content
+Martin Görner's HTML5/CSS3/SVG slides from #dataconnexions conference yesterday. Worth checking out !

Direct link to presentation: http://animateyourhtml5.appspot.com/pres/index.html#1

Post has shared content

Post has shared content
+Derek Greer does a great job explaining the mysteries of JavaScript closures, a topic often confusing to new JavaScript programmers.

Post has shared content
Essential JavaScript Design Patterns 1.5 Released (Free Book)

Over the past year or so I've been actively trying to encourage more developers to invest time in learning about the benefits of design patterns and how they can be applied to JavaScript. To help with this, I wrote a book on the topic which I released for free. Today a new version of it is available to read online and includes lots of updates and a few new sections

The book: http://addyosmani.com/essential-design-patterns

I'll be trying to get out ePub/PDF/Kindle versions of the book out next week for anyone interested in those, but in the mean time, if you could help spread the word about the book I would appreciate it greatly :)

Post has attachment
Multiple logins are cumbersome, but has one single advantage: if ever a system is compromised, the ensuing damage is limited to that single system. Standardized single sign-on eases the multiple login pain, but a break-in/compromise will extend the damage to all systems that are part of it. Application's context and security needs should dictate the right approach.
Wait while more posts are being loaded