Major performance improvements are introduced: SSR with Next.js 4 is 2.6x faster and style initialization is 20% faster. According to CSS-in-JS benchmarks, Next.js styles are now the fastest of any library.
In this post the authors are going to highlight some of the more prominent changes: better TypeScript integration, better error handling, better support for functional components in single-file components, and environment-agnostic server-side rendering.
Microsoft Edge is coming to iOS and Android, letting Windows customers roam their browsing experience wherever they go. Here's what developers need to know.
Microsoft’s TypeScript programming language brings many of the advantages of static typing to JavaScript. Although it doesn’t enforce types at runtime, it enables richer static analysis, encourages more safety, and opens the door for better IDE integration. TypeScript code is typically transpiled to standards-based JavaScript so that it can run natively in browsers and Node.js.
Last summer the author wrote a post which quickly became my most popular one to day. With webpack 2 and 3 it got outdated, so he decided to write a new one.
The Firefox Quantum release is getting close. It brings many performance improvements, including the super fast CSS engine that we brought over from Servo.
Is being able to handle 5 times more request per second not better? Well, no. Not when the payload we are delivering back is a tiny useless JSON blob. If your production application is a hello world server, then sure, 500% is amazing. But then again, why use a framework at all?! Also, how do you still have a job?
Imagine, for example, a complex image transformation algorithm that’s running in the browser. While the Call Stack has functions to execute, the browser can’t do anything else — it’s being blocked. This means that the browser can’t render, it can’t run any other code, it’s just stuck. And here comes the problem — your app UI is no longer efficient and pleasing.