EQCSS, an experiment in extending CSS with Element Queries, a way to apply styles based on element-specific conditions
Read more from the source: Smashing Magazine
Test units of code, pieces together, or the full-fledged application
To help with that problem, in this article I’ll give you a guide comparing the different kinds of testing types available, and some recommendations for their use.
Read the article at codeutopia.net
MS Edge adds ES6 features including import and export
Most of ES2015 (aka ES6) language support is already available in Edge, and last week’s Windows Insider Preview build 14342 brings more ES6 capabilities including modules, default parameters, and destructuring. We’re not stopping there – Edge also supports all ES2016 (aka ES7) proposals – the exponentiation operator and Array.prototype.includes – as well as future ECMAScript proposals such as Async Functions and utility methods like Object.values/entries and String.prototype.padStart/padEnd.
Read more from the source: Microsoft Edge Dev Blog
Come on TC39, V8 and Node have implemented all but the most obscure parts of ES6–where is the standard for import?
NodeJS 6.1 passes 96% of ES6 tests, failing only on proper tail calls, iterator closing, and some Proxying of internal `get` calls.
But no standard is in sight for resolving resources based on the string in import statements.
View the compatibility table results at node.green
WebKit ends its use of prefixes following Microsoft’s decision to make Edge support WebKit prefixes
WebKit’s new feature policy is to implement experimental features unprefixed, behind a runtime flag.
We’ll be evaluating existing features on a case-by-case basis. We expect to significantly reduce the number of prefixed properties supported over time but Web compatibility will require us to keep around prefixed versions of some features.
Read the announcement at WebKit
Contrary to Yahoo’s recent move to ban remote work, research shows companies who commit to telecommuting foster happier employees and more efficient teams
We’re still not sure why Yahoo’s CEO recently decided to ban the practice, but we can tell you this:
Companies committed to remote work share two common traits:
- Happy employees
- Efficient teams
Those aren’t claims based on anecdotal evidence. Numerous scientifically-rigorous, survey-backed empirical findings show how companies offering the flexibility to work from home (or coffee shops or co-working spaces) tend to be more profitable and productive than businesses that support on-site work only.
Read at Jell Blog