Monthly Archives: October 2014

Axiomatic CSS and Lobotomized Owls

Consistent margins is one use case for taking advantage of the CSS selector * + *


Managing flow content can get unwieldy–too many class selectors can become a specificity headache, nested styling can get redundant, and content editors don’t always understand the presentational markup. Heydon Pickering offers an unexpected option for handling cascading styles more efficiently: a variation on the universal selector.

Read the article at

Swarm.js+React — real-time, offline-ready Holy Grail web apps

Swarm.js works like Firebase but with the addition of offline client-side storage that is sync’ed to the server later


The new Swarm+React TodoMVC demo can:

– synchronize in real-time (WebSocket),

– cache data at the client (WebStorage),

– load and work completely offline (Application Cache).

The app employs Swarm models and React views. It is important to notice that the code is written like it is a local MVC app. The only network-aware call in client-side code is connect() which “plugs” the model into the server’s sync “outlet”. Later on, all the sync is done by Swarm in the background; update events are delivered to views using the popular on()/off() subscription pattern, and even that is hidden inside ReactMixin.

The app is optimized for instant load using the Holy Grail approach. All the views, models and even the router are shared between client and server. The server-side code prerenders React views so the browser gets static HTML (fast). The page is made live once scripts and data arrive (slower). Holy Grail is critical, considering that React.js is rather heavy. The resulting page load latency is quite close to RTT.

Read more from the source: Swarm.js

It’s called Windows 10 because old programs would confuse “Windows 9” with “Windows 98”

Cut the crap! The real reason Microsoft skipped Windows 9: old programs check if the version string starts with “Windows 9” to detect 95, 98 and ME


A quote from CNET’s anonymous source:

Microsoft dev here, the internal rumours are that early testing revealed just how many third party products that had code of the form

if(version.StartsWith(“Windows 9”)) { /* 95 and 98 */ } else {

and that this was the pragmatic solution to avoid that.

Read the full article at CNET