Last week I have been busy doing Open Source, leading projects, organizing NodeConf and the Italian NearForm meetup. There are a few new releases to talk about, so let’s dive in…
…litterally! Last weekend a few colleagues at NearForm traveled from all over Italy, France, Portugal and Serbia to Milano Marittima for a retreat! It has been an amazing experience. This is probably the part of of NearForm I missed the most: meeting people from all over the places and spend some quality time with them. If you are interested in participating in the next meetup, check us out at!
NearForm is working to shape a better world with open, creative software and we are looking for people to join our team. Contact us for your next career move
NearForm is working to shape a better world with open, creative software and we are looking for people to join our team. Contact us for your next career move
DevNation Day is a free, all-day immersive virtual experience created to bring you the most exciting developer and technology updates. It will cover five topics areas: Kubernetes/OpenShift, Java, Python, and JavaScript. You will hear from Red Hat Developer experts as well as leaders from across a number of companies and industries, including IBM, Oracle, and more. Stay up-to-date on the latest technologies from the comfort of your own desk, and interface with our speakers through polls, chats, and on-stage participation. We look forward to ‘seeing’ you there!
There is a good & bad news regarding ESM & Node.js core. However I think I need to provide a bit more context before breaking the news. I have always been a critic of the mass-move to ESM as recommended by a few other OSS maintainers as ESM was lacking certain features that we rely on every day while developing Node.js applications: module mocking and tracing / APM. ESM makes module resolution static and deterministic (which is good) but it cannot be altered at runtime and in order to support module mocking, tracing, code coverage and other things you need to install a loader before Node.js starts. This fundamental feature is actively worked on and it is not stable yet: we have just landed a significant breaking change to improve it. We are sorry this will disrupt some of your workflows.
Over the weekend I landed a new option to Node.js HTTP/1.1 server to limit the number of maximum connections. This will be useful to help the coordination between the load balancer and Node.js servers to spread the load evenly between all the available peers.
You can read more about the main change in the two following links, one describing the problem and a small PR describing the solution. They are worthwhile to read to understand more how debug JavaScript performance issues regarding shapes and megamorphic code. Read up:
Over the past week or so I started to learn how V8 optimizes property access through shapes and inline caches by following the blog post link in the decorators documentation (Shapes and IC + Optimizing Prototypes). After reading this and…
Over the past week or so I started to learn how V8 optimizes property access through shapes and inline caches by following the blog post link in the decorators documentation (Shapes and IC + Optimizing Prototypes). After reading this and…
Thanks to Igor Savin and the maintainers of colorette, we fixed an old regression in pino-pretty that caused colors to not be rendered in certain cases. Now it’s fixed!
The coronavirus disease 2019 (COVID-19) pandemic caused a rapid shift to full-time remote work for many information workers. Viewing this shift as a natural experiment in which some workers were already working remotely before the pandemic enables us to separate the effects of firm-wide remote work from other pandemic-related confounding factors. Here, we use rich data on the emails, calendars, instant messages, video/audio calls and workweek hours of 61,182 US Microsoft employees over the first six months of 2020 to estimate the causal effects of firm-wide remote work on collaboration and communication. Our results show that firm-wide remote work caused the collaboration network of workers to become more static and siloed, with fewer bridges between disparate parts. Furthermore, there was a decrease in synchronous communication and an increase in asynchronous communication. Together, these effects may make it harder for employees to acquire and share new information across the network. Using a large dataset of workers’ technology use from before and after the COVID-19 pandemic, Yang et al. find that firm-wide remote work caused the collaboration networks of information workers to become more static and siloed and communication to shift to more asynchronous media.
The coronavirus disease 2019 (COVID-19) pandemic caused a rapid shift to full-time remote work for many information workers. Viewing this shift as a natural experiment in which some workers were already working remotely before the pandemic enables us to separate the effects of firm-wide remote work from other pandemic-related confounding factors. Here, we use rich data on the emails, calendars, instant messages, video/audio calls and workweek hours of 61,182 US Microsoft employees over the first six months of 2020 to estimate the causal effects of firm-wide remote work on collaboration and communication. Our results show that firm-wide remote work caused the collaboration network of workers to become more static and siloed, with fewer bridges between disparate parts. Furthermore, there was a decrease in synchronous communication and an increase in asynchronous communication. Together, these effects may make it harder for employees to acquire and share new information across the network. Using a large dataset of workers’ technology use from before and after the COVID-19 pandemic, Yang et al. find that firm-wide remote work caused the collaboration networks of information workers to become more static and siloed and communication to shift to more asynchronous media.
Written by Jose Fernandez, Arthur Gonigberg, Julia Knecht, and Patrick Thomas In 2017, Netflix Studios was hitting an inflection point from a period of merely rapid growth to the sort of explosive growth that throws “how do we scale?”
Written by Jose Fernandez, Arthur Gonigberg, Julia Knecht, and Patrick Thomas In 2017, Netflix Studios was hitting an inflection point from a period of merely rapid growth to the sort of explosive growth that throws “how do we scale?”
