#217 – June 25, 2017
Full Stack Fest 2017: Problems of today, wonders from the future
Barcelona, 4-8 Sept. 2017 – Are you a curious mind? Full Sack Fest is a week-long conference based in the amazing city of Barcelona that peeks into the web of tomorrow. Serverless, Blockchain, WebVR, Distributed Web, Progressive Web Apps... Come and see! Early bird tickets available with a 10% discount using the code DIGEST.
The search for the Goldilocks browser and why Firefox might be “just right” for you
Today Mozilla is releasing a new version of Firefox that runs using a multi-process architecture, for the first time using several separate processes for your web page content (your tabs). Now, you might know that some other browsers have done this sort of thing for a while. But even if you think you know everything about multi-process browsers, or if you don’t have the first clue, read on.
A crash course in memory management
To understand why ArrayBuffer and SharedArrayBuffer were added to JavaScript, you need to understand a bit about memory management. You can think of memory in a machine as a bunch of boxes. I think of these like the mailboxes that you have in offices, or the cubbies that pre-schoolers have to store their things.
I just wanted to build something cool using machine learning on a bunch of public images. But after showing it to a couple of my "friends" they thought it was too creepy and Instagram might sue me for breaking their platform policy and I should stop doing it.
Tabs, spaces and your salary - how is it really?
A couple of days ago, David Robinson published an article on the Stack Overflow blog with a very provocative title: Developers Who Use Spaces Make More Money Than Those Who Use Tabs. It uses the data from Stack Overflow developer survey to show that indeed, using spaces is associated with higher salaries, even when we account for experience level. So, should you start using spaces instead of tabs to increase your salary?
Last October, we released the Mercury Web Parser, and the results were astounding. Our costs dropped immediately, and today, Mercury Web Parser costs around $400 per month to operate — roughly two orders of magnitude less than the cost to operate the Readability API.