🚨 Breaking Changes Drop unmaintained node 16 support - by @jerome-benoit in #116 (5e08d) Remove useless benchmark todos - by @jerome-benoit in #118 (434d0) Remove *Concurrently methods - by @jerome-benoit in #135 (1297a) Fold warmup step into benchmark run - by @jerome-benoit in #150 (4fcd4) API simplification details: Bench concurrency setting is now controlled only at runtime via concur
JSer.info #684 - Tailwind CSS v4.0 alphaがリリースされました。 Open-sourcing our progress on Tailwind CSS v4.0 - Tailwind CSS OxideというRustで書かれたエンジンを追加、Lightning CSSを組み込むように変更することでパフォーマンスやビルドトインでサポートする構文が改善されています。また、記事ではv4のロードマップについても触れられています。 TypeScript 5.4がリリースされました。 Announcing TypeScript 5.4 - TypeScript BetaやRCからの大きな機能的な追加などはありません。 クロージャーにおけるNarrowing結果の改善、NoInfer Utility Typeの追加、 --module preserveの追加が行われ
Huge thanks to Jarred Sumner for reviewing this post. It wouldn’t have been possible without his help. Bun is a new and ambitious JavaScript toolset and runtime. Early adopters have been reporting that Bun JavaScript is incredibly fast. So fast that it has been touted by some as a Node.js killer. Curious, I decided to check out Bun for myself and benchmark it against the competition. Is it as fast
25 October 2020 On Javascript Performance 1. Techempower Rankings by billwhizz Why is Javascript in the top 2 of techempower? This question was recently asked on github, prompted by the arrival of a new javascript platform near the summit of the intermediate techempower rankings. This platform, Just(js), is something I have been hacking on as a side-project for some time now. Here I will attempt t
By Jacek Schae Also available in: Turkish — thanks to @erdenizZz, Portugues — thanks to @felipefialho For the third time, we are comparing Front-End frameworks by using the Real World example apps. RealWorld example app gives us: RealWorld App Something more than a “todo”. Usually “todos” don’t convey enough knowledge and perspective to actually build real applications. Standardized A project that
Today we are announcing a new version of the JetStream JavaScript benchmark suite, JetStream 2. JetStream 2 combines a variety of JavaScript and WebAssembly benchmarks, covering an array of advanced workloads and programming techniques, and reports a single score that balances them using a geometric mean. JetStream 2 rewards browsers that start up quickly, execute code quickly, and run smoothly. O
High, Low, AverageWedgetail gives you accurate timings for the best, worst and average timings. Measure thousands of executionsGet accurate statistics out of the box, by setting `numberOfExecutions` to at least 5000. import test from "ava"; import { timeExecution } from "wedgetail"; test("Can time a function", async t => { // This object contains a definition of the threshold // at which your func
このブラウザ バージョンのサポートは終了しました。サポートされているブラウザにアップグレードしてください。
Output (DOM) - click to monitor output (DOM) while test is running
Performance is an important criteria when choosing test-runner. Tests should pass as fast as possible to detect errors earlier, improve developer experience and reduce CI servers running time. In this story I will compare the most popular JavaScript test-runners on the same set of unit tests and find the winners. CandidatesI will not go deep into the specific features of test-runners. Each one has
Air.js is an ES6 benchmark. It tries to faithfully use new features like arrow functions, classes, for-of, and Map/Set, among others. Air.js doesn't avoid any features out of fear that they might be slow, in the hope that we might learn how to make those features fast by looking at how Air.js and other benchmarks use them. This documents the motivation, design, and license of Air.js. To run Air.js
Modern load testing for developers and testers in the DevOps era. Download · Documentation · Community Forum · Public Roadmap k6 is a modern load-testing tool, built on our years of experience in the performance and testing industries. It's built to be powerful, extensible, and full-featured. The key design goal is to provide the best developer experience. Its core features are: Configurable load
The history of JavaScript benchmarks is a story of constant evolution. As the web expanded from simple documents to dynamic client-side applications, new JavaScript benchmarks were created to measure workloads that became important for new use cases. This constant change has given individual benchmarks finite lifespans. As web browser and virtual machine (VM) implementations begin to over-optimize
Two years ago I’ve started my journey to explore Virtual DOM and wrote kivi library. This library is using key ideas from React, but has completely different implementation. The primary goal for this library was to show the best numbers in benchmarks. I wouldn’t recommend to use kivi for anything except benchmarks, and I hope nobody is using it. Almost all implementations that have the best result
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
