JavaScript Frameworks - Heading into 2023
The wonderful thing about glimpsing into the future is that the path is never completely clear. We can look at trends, and look at innovations and try to chart a course. Better still we can be part of those innovations to guide the direction. But nothing is certain. 2022 had a ton of big releases that push web development forward. We saw the 1.0 releases of both Astro and Sveltekit. SolidStart, an
The JavaScript Paradox
I'm not sure if there's ever been a language more loathed, yet so widely used, as JavaScript. I'm not of that camp. I quite like JavaScript. Its quirks, its flaws. How it somehow built upon Scheme yet was destined to be the most pervasive programming language. JavaScript was designed to be a companion. A scripting language to perform menial tasks to assist small pieces of interactivity on the page
The Cost of Consistency in UI Frameworks
One interesting thing we found when researching my last article is that every framework's version of this React code logs different things when you click the button: What we ended up with in the log was: React 0 0 0 Vue 1 2 0 Svelte 1 0 0 Solid 1 2 2 I first posted this a year and a half ago but it's been haunting me ever since. I keep revisiting it. In my dreams, and my day job. When working on M
Conquering JavaScript Hydration
SSR was never the problem. The problem was, and still is, the client-side hydration. For all the effort we've put into Server Rendering on the web, we still haven't found a universally good solve for balancing the developer costs with end user costs. Regardless of how we optimize for server rendering, hydration hangs over us. That JavaScript that needs to be run on page initialization, that makes
The Quest for ReactiveScript
@RyanCarniato Let’s chat some time. I’ve done an excessive amount of research on this topic in the context of languages (eg Lucid, FRTime, etc) and would love to learn more from you as well and swap opinions. I've been meaning to take him up on his offer, but in the meantime what I can do is write about it. Because the last year I've done a lot of searching and thinking into how I'd approach this.
Understanding Transitional JavaScript Apps
okay i mulled over this idea in my head for a month and then just sat down and wrote this in one pass without switching tabs so here it is, raw and extra spicy: "Second guessing the modern web" https://t.co/NWt1oYF54M I've written countless articles about the technologies around these topics but maybe it's time to step back and really appreciate what this means for the average web developer. Death
JavaScript Framework TodoMVC Size Comparison
Size in JavaScript Frameworks is actually a pretty tricky thing to estimate. Even nailing down the size of runtimes is unclear. You might go to bundlephobia.com but the size there can be misleading. With tree-shaking not all code is included. Bundlephobia also doesn't include sub-modules. Things like svelte/motion or preact/hooks. There isn't only the size of the runtime but the size of the compon
JavaScript vs JavaScript: Round 2. Fight!
After I finished the first article I wasn't sure how long it would be before we'd have enough topics for the next round. But given the continuing atmosphere around the JavaScript ecosystem, many of these topics just fell on my lap. So let's get this started. Fight! 1. Build vs No Build Several years ago I read a great article(which I can't seem to find anymore) that saw JavaScript being at a cross
JavaScript vs JavaScript. Fight!
Ryan Carniato for This is Learning Posted on Aug 19, 2021 • Updated on Sep 10, 2021 With software development, we are often presented with alternative choices for libraries and tools that appear to accomplish the same sort of things. Each one will advertise its key advantages, and we attempt to weigh the pros and cons. Sometimes, the differentiators have less to do with what we are accomplishing a
Components are Pure Overhead
A couple of years ago in the The Real Cost of UI Components, I explored the cost of components in JavaScript frameworks. I asked whether components were just overhead? And the answer was: it depends. The Virtual DOM library I tested, ivi, had no issues handling more components. But Lit and Svelte were dramatically worse. They scaled back to almost React levels of performance as I broke them down t
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
