Node’s (19.1) test runner, initial impressions and opinions Photo by Nguyen Dang Hoang Nhu on Unsplash Note: what I write could be wrong by the time that you read it At the time of writing (node 19.1), test APIs are to be considered experimental, so what I write could be out of date by the time a new node version will be out Intro At the end of this blog post, you will know what I think about the “new” feature of node, of having a built-in test runner.

Why did I switched as a main machine to my iPad I switched since almost a year to the iPad as a main machine, this was due to the fact that I already had it, and I found myself using it way much more than my laptop, and I decided to invest some money in a keyboard and call it my main machine from that moment on. What I discovered is that, for certain workload, it was actually helping me to focus, thanks to the different way of thinking about computing that the iPad has.

This is a bit of a technically lighter explanation meant for not technical people to try to understand what is a cookie and why should you even care about it. Disclaimer for technical people, to boil it down, some stuff will be purposely slightly inaccurate, or more reflective of HTTP 1 instead of HTTP 2. But for the sake of understanding why cookie matters or not, it’s irrelevant. A web server doesn’t necessarily remember you To understand the need for cookies, what you need to know at the beginning, is the fact that every time that you reload a page, the “website” doesn’t necessarily know if you reload three times, or you are three different people.