Comparing various JavaScript frameworks and what is Deno?

Going into a Google report that gives us the ability to compare different JavaScript frameworks. And diving into what is Deno and it's new release.

🗞 News

Smashing Magazine 🇺🇦 @smashingmag

✏️ How To Use Google CrUX To Analyze And Compare The Performance Of JS Frameworks (by @DanShappir)

smashingmagazine.comHow To Use Google CrUX To Analyze And Compare The Performance Of JS Frameworks — Smashing MagazineIn this article, Dan Shappir analyzes the performance cost associated with various frameworks and explains the wide variety of framework and platform choices that are currently available to front-end and fullstack developers.

It is a pretty well-known fact that Google collects information from various websites. However, did you know that this information can be parsed for different web technologies?

Google collects performance information from millions of opted-in Chrome browsers around the world and uses this information as a performance ranking factor for its search engine. But it also makes this information freely available so that anyone can use it to check the real-world performance of individual websites. Even more significantly, it’s possible to segment this data according to the technologies used in the websites.

This article explores the difference between many websites and the different frameworks they may use.

The entire report is called the Google Chrome User Experience Report. Overall it is as you would expect. All frameworks offer ways to build fast websites, but their comparisons can get a little washy.

SvelteKit, Gatsby, and Wix sites performed very well although with a caveat. SvelteKit had barely any sites registered so it was difficult to draw any conclusions.

Next.JS did not perform as well as expected in the Core Web Vitals category. Check it out for a more in-depth report.

Deno @deno_land

Deno v1.22 has been released: ✅ The default type checking mode has been updated ♻️ Deno.emit() has been replaced with a user-land module ✅ Adds Response.json() and Navigator.userAgent ✅ Improves the test runner Read more in the release notes

deno.comDeno 1.22 Release NotesDeno 1.22 changes default type-checking behavior, removes Deno.emit() API, adds Response.json() API, adds Deno namespace to workers by default, and more

Deno recently came out with version 1.22.0. But what is Deno?

Deno is a simple, modern and secure runtime for JavaScript, TypeScript, and WebAssembly that uses V8 and is built in Rust.

Simply put Deno looks to be a replacement for Node.js that offers Typescript support of the box and is considerably more secure. Among other things:

1. Provides web platform functionality and adopts web platform standards.

2. Secure by default. No file, network, or environment access, unless explicitly enabled.

3. Supports TypeScript out of the box.

4. Ships only a single executable file.

5. Has built-in development tooling like a dependency inspector (deno info) and a code formatter (deno fmt).

6. Has a set of reviewed (audited) standard modules that are guaranteed to work with Deno: deno.land/std.

Essentially Deno makes it so that you have to opt-in to certain actions with flags. This makes it a whole lot more secure than Node. Also, it automatically dies on uncaught errors so no further execution of code can happen.

This new release of Deno adds some overall improvements to several features. I definitely suggest checking it out if you’re a node developer as this is the next logical evolution of it.

📦 More interesting Articles

⚛ React

• Remix and the Edge

🎨 CSS

• Best practices for dashboard design

• The truth about pixels and REM

🧪 Testing

• Cypress 9.6.1 Release

🔧 Other

• Beginners Guide to npm package manager in 2022

• New to the web platform in April

• From 0 to 80 in Rust as a JS dev

• API to parse GitHub markdown