Modal dialogs have been vilified by modern UX theory as overly disruptive. But sometimes you want to be disruptive, whether you want show a fatal error or need an unskippable dialog prompting the user for information.

This week, let's take a short look at Vex, a front-end library for displaying

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/cWJfaRrAyXg/

Most of you have probably heard about how awesome React is, particularly when it comes to performance. The Virtual DOM is a great innovation in this regard, since it saves developers from having to deal with UI bottlenecks manually. However, sometimes speed is such a critical aspect that React's automatic

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/fcDjVWJUxq4/

As we look forward to the ES7 async function, let's take a moment to remember an aging former star that still has a little bit of life left in it: Async.js

Nowadays there are a number of ways to avoid callback hell:

• Transpiler, ES6/7 native promises and native

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/YEILbh96JAI/

The two business books that have most influenced me are Geoffrey Moore’s Crossing the Chasm and Andy Grove’s Only the Paranoid Survive. Grove’s book explains that, for long-term success, established businesses must periodically navigate “strategic inflection points”, moments when a paradigm shift forces them to adopt a new strategy or fade into irrelevance. Moore’s book [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/qIgu4yf-jUY/

Some, Every Every now and then in your everyday programmers life you come across an array and you need to determine something, usually whether all the elements in the array pass a certain test. You know, something like: var allPass = true; for (var i = 0; i < arr.length; ++i) { if ( ! [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/7mG0DL0991w/

While researching TypeScripts popularity I ran across a post by Adam Bard listing the most popular languages on Github (as of August 30, 2013). Adam used the Google BigQuery interface to mine Githubs repository statistics. What really interested me was not absolute popularity but which languages are gaining adoption. So I decided to use the [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/qBW1btZnF_k/

Every software project needs plumbing. If you write your code in JavaScript chances are youre using Grunt. And if your project has been around long enough, chances are your Gruntfile is huge. Even though you write comments and indent properly, the configuration is starting to look unwieldy and is hard to navigate and maintain (see [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/YqKdljiix8M/

Grunt is a great tool for automating boring tasks. Browserify is a magical bundler that allows you to require your modules, Node.js style, in your frontend code. One the most useful plugins for grunt is grunt-contrib-watch. Simply put, it watches your file system and runs predefined commands whenever a change occurs (i.e. file was deleted, added or updated). This [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/UH_WxAtkX8g/

At Salsita we implement a lot of browser extensions. We create them for our clients, for our own purposes or just for fun. We therefore decided a couple of years about to write a Chrome extension skeleton that provides boilerplate for the common code that every extension tends to need. The resulting skeleton has been a big help in [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/ASlY5l0JvxU/

We recently launched the private beta of Kitt, an iPhone browser developed by Salsita with support for Chrome browser extensions. You can find out more about Kitt in the screencast below: Around the time we were finalizing this screencast, Apple announced that they would be adding support for extensions to iOS 8, including Safari extensions that [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/q2kexTNoU1g/

During the development of our company website, we came across an interesting UX dilemma. The website uses full-width horizontal blocks of content with varying background colors. This caused problems with the fixed-position side navigation, since black text becomes hard to read when displayed over a non-white background.   While there are various ways to deal with this, we didnt want [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/s8lbw-zLAe8/

A quick update to my previous post about creating a DOM window wrapper. My colleague Tomas pointed out that Browserify breaks if it is running inside the wrapper, due some code in the shim it uses for the NodeJS process module. The code compares the source of an event with

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/Egn_XGnK_Sw/

A quick update to my previous post about creating a DOM window wrapper. My colleague Tomas pointed out that Browserify breaks if it is running inside the wrapper, due some code in the shim it uses for the NodeJS process module. The code compares the source of an event with

https://blog.javascripting.com/2014/05/27/dom-window-wrapper-update/

A quick update to my previous post about creating a DOM window wrapper. My colleague Tomas pointed out that Browserify breaks if it is running inside the wrapper, due some code in the shim it uses for the NodeJS process module. The code compares the source of an event with the window. In our case the [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/pEYnYDyTRjw/

A quick update to my previous post about creating a DOM window wrapper. My colleague Tomas pointed out that Browserify breaks if it is running inside the wrapper, due some code in the shim it uses for the NodeJS process module. The code compares the source of an event with the window. In our case the [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/kbbsLOH9Yic/

In order to enable Kitt, our iPhone web browser, to run browser extensions, we needed a way to run content scripts in a webpage. In Chrome, content scripts are run in a sandbox to prevent the two contexts from interfering with each other. They share only the window object. Although

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/1Ym8HxLtm2A/

In order to enable Kitt, our iPhone web browser, to run browser extensions, we needed a way to run content scripts in a webpage. In Chrome, content scripts are run in a sandbox to prevent the two contexts from interfering with each other. They share only the window object. Although

https://blog.javascripting.com/2014/05/19/wrapping-the-dom-window-object/

In order to enable Kitt, our iPhone web browser, to run browser extensions, we needed a way to run content scripts in a webpage. In Chrome, content scripts are run in a sandbox to prevent the two contexts from interfering with each other. They share only the window object. Although there are tantalizing signs that something [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/PRSRFJTAyMw/

In order to enable Kitt, our iPhone web browser, to run browser extensions, we needed a way to run content scripts in a webpage. In Chrome, content scripts are run in a sandbox to prevent the two contexts from interfering with each other. They share only the window object. Although there are tantalizing signs that something [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/adadUsQHSRY/

In order to enable Kitt, our iPhone web browser, to run browser extensions, we needed a way to run content scripts in a webpage. In Chrome, content scripts are run in a sandbox to prevent the two contexts from interfering with each other. They share only the window object. Although there are tantalizing signs that something [&]

http://feedproxy.google.com/~r/justdiscourse/browsing/~3/18UPBStmVrk/