awesome-react-renderer
solid
awesome-react-renderer | solid | |
---|---|---|
7 | 20 | |
1,860 | 5,767 | |
- | - | |
4.0 | 9.3 | |
15 days ago | about 3 years ago | |
TypeScript | ||
- | MIT License |
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.
awesome-react-renderer
-
Interview with Senior JavaScript Developer 2024 [video]
Yes, the reactions to it were not very enthusiastic as you'd expect. Also it did have a11y issues.
There are a lot of interesting renderers for react, some of them are even maintained: https://github.com/chentsulin/awesome-react-renderer
-
nvim-react: ReactJS like UI framework for Neovim (WIP)
Cool work! But title is indeed misleading :( It's because what you've presented is indeed possible with react and js as they're quite versatile, look at this awesome list for examples: https://github.com/chentsulin/awesome-react-renderer
-
Why would we need React without ReactDOM library?
There is a lot of them https://github.com/chentsulin/awesome-react-renderer
-
Why did react chose virtual DOM instead of using real DOM, when other frameworks are more fast even after using real DOM?
For example, because I know React, I was able to code a 3D application that uses ThreeJS and place 3D objects on the screen instead of divs, using the same methodologies just like in a normal web app. You can see other rendering targets at https://github.com/chentsulin/awesome-react-renderer. There are some pretty interesting ones out there.
-
Why Virtual DOM is considered faster that directly updating the real DOM.
List of custom renderers
-
Starter using Vite + React + TypeScript + Tailwind CSS.
Due to its awesome renderer system, there are many React Renderor. So React can be not used only Web, for example, used by React Native.
- Awesome React Renderer
solid
-
Why Virtual DOM is considered faster that directly updating the real DOM.
The strength of V-DOM definitely doesn't lay in performance. It made it easier for developers to write more maintainable interactive UI. Other than that I'd rather think of it as a compromise. Fortunately, frontend web dev continuously progresses and there are initiatives like https://github.com/ryansolid/solid which focus on compilation-time diffing.
-
Learning to Appreciate React Server Components
You see I work 12 hours a day. 8 hours of that is my professional job where I am a developer on the Marko core team at eBay. Then after some much-needed time with my family, my second job starts where I am core maintainer of the under-the-radar hot new reactive framework Solid.
-
Hyperapp – Is It the Lightweight 'React Killer'?
They’ve been well received, and the core ideas behind them have inspired the likes of Vue’s Composition API and a big part of Solid’s API.
- Solid Update: March 2021
-
Introducing maple, a VDOM-less fine grained reactive web framework in Rust + WASM
After discovering solid js, I wondered how feasible it would be to write such a framework in Rust. After two days of hacking around, here is the result!
-
Introducing maple, a VDOM-less fine grained reactive web framework running in WASM
After discovering solid js, I wondered how feasible it would be to write such a framework in Rust. After two days of hacking around, here is the result!
-
[AskJS] Any interesting use cases for Proxy?
Solidjs UI library uses Proxies in order to make state reactive https://github.com/ryansolid/solid
-
[AskJS] What you love about Javascript that we don't find in another programming language and why many OO programmer from others language Java, C#, C++ etc hate/don't like it ?
[0] https://github.com/ryansolid/solid#the-gist
-
Server Rendering in JavaScript: Optimizing Performance
The key thing to understand though is this is not a React-only approach. I make heavy use of this pattern in my Solid projects as it makes a really nice isomorphic solution and works really well with the next topic...
-
Building a Reactive Library from Scratch
The main ones that I'm referring to have proxy implementations along with their basic signal atoms. MobX's `observable`, Vue's `reactive`, Solid's `state` all are reactive proxies that properly handle subscriptions.
What are some alternatives?
soprano.nvim - Play soprano music in neovim
Svelte - Cybernetically enhanced web apps
morphdom - Fast and lightweight DOM diffing/patching (no virtual DOM needed)
marko - A declarative, HTML-based language that makes building web apps fun
vite - Next generation frontend tooling. It's fast!
Tailwind CSS - A utility-first CSS framework for rapid UI development.
rust-dominator - Zero-cost ultra-high-performance declarative DOM library using FRP signals for Rust!
react-pdf - 📄 Create PDF files using React
hyperapp - 1kB-ish JavaScript framework for building hypertext applications
nvim-react - Reactive UI framework for neovim
knockout - Knockout makes it easier to create rich, responsive UIs with JavaScript