flexbugs
js-framework-benchmark
flexbugs | js-framework-benchmark | |
---|---|---|
9 | 64 | |
13,647 | 6,484 | |
- | - | |
0.0 | 9.8 | |
4 months ago | 8 days ago | |
JavaScript | ||
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
flexbugs
- Flexbugs
-
Use any web browser as GUI, with Zig in the back end and HTML5 in the front end
For old features yes, for new ones it depends.
https://github.com/philipwalton/flexbugs
-
I am not that excited about new CSS features
First, we read all the articles that showed us how to use it. Then we need to understand the axes. After that, we needed to wait for browser support. In the meantime, some of us brave enough used float fallbacks. On top of all that, we needed to deal with bugs. Those were the happy times, but they got us to this point in the frontend development phase.
-
What are some cross-browser quirks to watch out for nowadays?
To actually contribute, there's some flexbox bugs here which are still valid. https://github.com/philipwalton/flexbugs
-
My Good Friend Flexbox
If you find yourself in a situation when you have to solve a flexbox related layout bug for IE11, you might want to have a look at this collection of known issues and workarounds which helped me a great deal in the past.
-
Make formal verification and provably correct software practical and mainstream
For functional stuff, sure, but I don't think this is achievable within the UI domain. CSS rules have implementation details that change how you write it, for example there's a documented set of issues in flex implementations maintained here: https://github.com/philipwalton/flexbugs
It might be practical and possible to become mainstream for some domains, but it's doubtful for others.
- I hit a wall learning CSS Flexbox alignment and justification two weeks ago, so I wrote a web page to try to figure it out. I accidentally documented all the differences between how Chrome and Firefox interpret flexbox alignment and justification. IDK if this is useful or not, but here it is.
- Long live Flexbox
-
Debugging CSS: Some Tips and Tricks
For example, I've regularly ran into flexbox issues that are Safari-specific. I've discovered these by testing in other browsers and confirming that the issue only shows up in Safari. A good reference of Flexbox browser-specific bugs is Philip Walton's flexbugs repo.
js-framework-benchmark
-
Popularity is not Efficiency: Solid.js vs React.js
JavaScript benchmarks are instruments for measuring the speed and effectiveness with which a JavaScript engine—such as the ones found in web browsers—can complete particular tasks. Benchmarks are used by developers and browser vendors to evaluate various engines, find places in the code where improvements are needed, and make sure JavaScript standards are being followed.
-
Use any web browser as GUI, with Zig in the back end and HTML5 in the front end
Strange then that frameworks advertise how fast they are at rendering, mutating, and creating objects in the DOM, and one of the main JS benchmarks everyone likes to measure their performance by is literally a benchmark about DOM manipulation: https://github.com/krausest/js-framework-benchmark
Oh wait. It's not strange. Because state manipulation is a largely solved problem, and even the least performant state manipulation is blazingly fast. However, presenting components in the browser's DOM is tens of magnitudes of orders less performant than anything you can throw at state manipulation.
And every single framework is busy solving one single problem: how do we touch the DOM as little as possible?
- JavaScript-Framework-Benchmark
- GitHub - krausest/js-framework-benchmark: A comparison of the performance of a few popular javascript frameworks
- JavaScript Framework Benchmark
- Vue 3 now outperforms Svelte and React
-
Vue 3 is currently performing better than Svelte and React
It literally says at the bottom "Data from https://krausest.github.io/js-framework-benchmark/"
- Cample.js benchmark reactivity without VDOM
- Rust é uma linguagem que embora tenha uma curva de conhecimento considerável, entrega vários benefícios como segurança e produtividade, reduzindo consideravelmente a verbosidade
-
Imperative - 1.5kb React alternative using Generators
The standard benchmark for js frameworks would be best: https://github.com/krausest/js-framework-benchmark
What are some alternatives?
browser-compat-data - This repository contains compatibility data for Web technologies as displayed on MDN
mikado - Mikado is the webs fastest template library for building user interfaces.
magmide - A dependently-typed proof language intended to make provably correct bare metal code possible for working software engineers.
sycamore - A library for creating reactive web apps in Rust and WebAssembly
webui - Use any web browser as GUI, with your preferred language in the backend and HTML5 in the frontend, all in a lightweight portable lib.
yew - Rust / Wasm framework for creating reliable and efficient web applications
gnoga
imba - 🐤 The friendly full-stack language
dafny - Dafny is a verification-aware programming language
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.
webui-demo - WebUI standalone binary template
Svelte - Cybernetically enhanced web apps