proxy-polyfill
sycamore-mac
| proxy-polyfill | sycamore-mac | |
|---|---|---|
| 3 | 3 | |
| 1,132 | 8 | |
| 0.2% | - | |
| 0.0 | 0.0 | |
| 6 months ago | over 2 years ago | |
| JavaScript | Rust | |
| 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.
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.
sycamore-mac
-
A first look at Sycamore's new reactive primitives: how the next version of Sycamore will be the most ergonomic yet
Not inherently, but practically yes – currently. There are attempts to use it for desktop ui https://github.com/Submersible/sycamore-mac but in general nothing prevents you from using it as you like and implement a backend you need.
-
How's the GUI-creation side of Rust looking nowadays?
Sycamore. And before people start complaining that it's just a webview or a browser in disguise, I would like to add that Sycamore was built from the start to allow multiple render backends. Right now, there are only backends for DOM and SSR (Server Side Rendering) but it should be pretty easy to extend it to native UI frameworks. In fact, there is a POC here of Sycamore running on macOS: https://github.com/Submersible/sycamore-mac although it is right now far from usable.
-
Tauri – Electron alternative written in Rust
I used this a bit, it was really great. Writing a Rust backend & exposing it to TypeScript was really slick!
There was one issue I ran into that made me think about jumping to Electron mid project, but I can't remember what it was now, but I think it was something like making my app bleed the entire MacOS window while still being moveable.
The other downside is you're going to be tempted to go down the rabbit hole and do everything in Rust. [1]
[1] https://github.com/Submersible/sycamore-mac
What are some alternatives?
core-js - Standard Library
dioxus - Fullstack GUI library for web, desktop, mobile, and more.