JavaScript frameworks in 2020, continuous JavaScript burnout (Deno.js, Svelte.js, Alpine.js)

Today we are exploring some newer JavaScript frameworks and tooling. We're also talking about the very real affliction known as JavaScript fatigue. What is JavaScript fatigue? And how does it relate to all these shiny new JavaScript frameworks? Live chat has been enabled for your supreme enjoyment!

45:44 Internet vs Electricity
50:12 IQ tests & vetting (Are technical interviews the same as IQ tests?) =========================
awesome stuff goes here:
=========================

I’m an affiliate of AlgoExpert / Educative / Amazon and may make a few bucks if you buy something:

📚PEEP MY FOUR CONSECUTIVE #1 NEW RELEASES:

✅ SUPPORTING REALTOUGHCANDY

[RealToughCandy]

TIMESTAMPS BELOW
5:50 Deno
19:11 Alpine
29:28 Svelte
36:55 Snowpack
45:44 Internet vs Electricity
50:12 IQ tests & vetting

[marble_wraith]

Deno! I can't Wait for the 1.0!

As long as they deliver on the featureset they've been pushing so far, it's almost guaranteed to replace node for new projects.

The biggest pain point i see right now, is figuring out how to migrate an existing project from legacy (node) to deno. Why is that? Because the way packages / dependencies are structured in node (via node_modules) is fundamentally different (hacky / commonJS), from deno (official ECMA standards).

In fact we're already seeing a little of what happens when you mess with dependencies in existing projects (via Yarn v2), which doesn't use node_modules. Some packages are dependent on node_modules being there, and as such Yarn v2 is a breaking change.

Switch over to deno, where they use the ECMA standard [not require()], and no node_modules folder is required, potentially it's the same kind of issues.

I can see a few ways of solving this problem, allegedly someone has created a polyfill of sorts (looking at the issues on github), but the "safest" way would undoubtedly be to manually refactor... that's a lot of packages to get through.

[williamraezer]

I wish I understood why we needed more frameworks to do the exact same thing. Yet, I'm JUCE c++ and Unity guy so what do I know?

[andresconrado]

It's a race with no finish line. It will nevcer end.

[zensukai]

Javascript days are numbered? Ahhh yah, no! Javascript is not going anywhere ... WebAssembly will not over run the most popular language on the planet.