tauri-vs-electron
proxy-polyfill
Our great sponsors
tauri-vs-electron | proxy-polyfill | |
---|---|---|
2 | 3 | |
12 | 1,132 | |
- | 0.4% | |
2.7 | 0.0 | |
over 2 years ago | 6 months ago | |
JavaScript | JavaScript | |
- | 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.
tauri-vs-electron
-
What makes people hate electron ?
Main advantage is that 400MB apps become more like 10MB. RAM and CPU usage are somewhat improved (webview is usually at least a bit more efficient than chromium), and startup times are a lot faster. Some of this is achieved by using compiled code to do heavy lifting, rather than electron’s JS-based versions. Full comparison here.
- Tauri – Electron alternative written in Rust
proxy-polyfill
-
Smallest React State lib ever?
Didn't know about it, looks like Proxy can be polyfilled in RN: https://github.com/GoogleChrome/proxy-polyfill
-
Tauri – Electron alternative written in Rust
Proxy polyfill: assuming you are referring to this [0], since I haven't seen anything else like this, then I'll paste here what the readme says:
> The polyfill supports just a limited number of proxy 'traps'. It also works by calling seal on the object passed to Proxy. This means that the properties you want to proxy must be known at creation time.
i.e. that's not a polyfill. It's a polyfill for a subset of the thing, maybe that's useful for somebody, but it's useless for the use cases I had for Proxy so far.
Shipping an entire regex engine with your app: right, that's the only way to do something like that. Not that that's actually the same thing though, I can't just load this and use lookarounds as normal, i.e. it's not a polyfill.
For all practical purposes these features are not polyfillable. If your idea of a polyfill includes not actually polyfilling the entire thing or shipping an entire engine with your app then sure, anything is polyfillable.
[0]: https://github.com/GoogleChrome/proxy-polyfill
-
🚀10 Trending projects on GitHub for web developers - 28th May 2021
Browsers without ES6 Proxy support can use the proxy-polyfill.
What are some alternatives?
neutralinojs - Portable and lightweight cross-platform desktop application development framework
core-js - Standard Library
Video-Hub-App - Official repository for Video Hub App
window.fetch polyfill - A window.fetch JavaScript polyfill.
Slint - Slint is a toolkit to efficiently develop fluid graphical user interfaces for any display: embedded devices and desktop applications. We support multiple programming languages, such as Rust, C++ or JavaScript. [Moved to: https://github.com/slint-ui/slint]
comlink - Comlink makes WebWorkers enjoyable.
webview - Tiny cross-platform webview library for C/C++. Uses WebKit (GTK/Cocoa) and Edge WebView2 (Windows).
sycamore-mac
Native Windows GUI - A light windows GUI toolkit for rust
xplorer - Xplorer, a customizable, modern file manager
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
Sugar - A Javascript library for working with native objects.