solid
linaria
solid | linaria | |
---|---|---|
20 | 46 | |
5,767 | 11,189 | |
- | 0.5% | |
9.3 | 8.4 | |
about 3 years ago | 9 days ago | |
TypeScript | TypeScript | |
MIT License | 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.
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.
linaria
-
How we improved page load speed for Next.js ecommerce website by 1.5 times
The code duplication occurred due to disabling the default code splitting algorithm in Next.js. Previous developers used this approach to make Linaria work, which is designed to improve productivity. However, disabling code splitting led to a decrease in performance.
-
An Overview of 25+ UI Component Libraries in 2023
KumaUI : Another relatively new contender, Kuma uses zero runtime CSS-in-JS to create headless UI components which allows a lot of flexibility. It was heavily inspired by other zero runtime CSS-in-JS solutions such as PandaCSS, Vanilla Extract, and Linaria, as well as by Styled System, ChakraUI, and Native Base. ### Vue
-
Why Tailwind CSS Won
I like Linaria [0] because your IDE typechecks your styles and gives you autocomplete/intellisense when typing styles. With Tailwind you have to look everything up in docs because it's all strings, not importable constants. Leads to a lot of bugs from typos that aren't a thing with type checked styles.
[0] https://github.com/callstack/linaria
-
I've decided to go back to using the Pages Router for now (long post)
And if you're wondering why I'm not using something like Linaria or some other runtime-less CSS-in-JS tool, it's simply because I don't want to have to spend my time setting things up and working around stuff and all that jazz. I just want something that works, and I've already got a personal scaffold for getting SC to work out of the box with Next, so, right now, it's either that or sticking to CSS/SCSS/SASS. For me, that is. I know it's such a small thing, but, honestly, one less headache for me is 2 steps forward.
- What's the best option these days for CSS in JS?
-
How bad is it to use CSS-in-JS with regards to the future of React?
I know that there are solutions that generate static css files (like vanilla-extract or linaria), but neither of them work with app router currently (1, 2).
-
JSS vs Styled Components? and why?
If you really want tighter interaction with JS, try a zero-runtine solution like linaria
-
What is the best CSS framework to use with React? why?
https://github.com/callstack/linaria is objectively the best. It's 100% styled component compatible, but with zero runtime which not only makes it substantially faster, but also makes it easy to do things like server side rendering, etc.
-
Why is tailwind so hyped?
tags inside SFCs are typically injected as native
</code> tags during development to support hot updates. <strong>For production they can be extracted and merged into a single CSS file.</strong></p> </blockquote> <p>There are also 3rd party CSS libs that do the same thing such as <a href="https://linaria.dev/">linaria</a>, <a href="https://vanilla-extract.style/">vanilla-extract</a>, and <a href="https://compiledcssinjs.com/">compiled CSS</a>. Which can be used in the event you're stuck with something that doesn't have baked in support via SFC formats (looking at you React).</p> <p>These are my preferred ways of handing it.</p> <ol> <li>Tailwind</li> </ol> <p>Option 2 is tailwind, which works backwards.</p> <p>That is, instead of the above with extraction where you write the styles, and the framework or libs extract them and replace them with class names, it's the other way around.</p> <p>You're writing class names first (which are essentially aggregated CSS property-values) which then generate and/or reference styles.</p> <p>It has the advantage of being easy to write (assuming you've got editor LSP, linting, etc), but as you've discovered, it's difficult to read / can get really messy really fast.</p> <p>As far as all the other claims on the Tailwind site, it's all marketing, at least 80% bullshit.</p> </div>
- Individual css for every component?
What are some alternatives?
Svelte - Cybernetically enhanced web apps
emotion - 👩🎤 CSS-in-JS library designed for high performance style composition
marko - A declarative, HTML-based language that makes building web apps fun
Tailwind CSS - A utility-first CSS framework for rapid UI development.
morphdom - Fast and lightweight DOM diffing/patching (no virtual DOM needed)
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
rust-dominator - Zero-cost ultra-high-performance declarative DOM library using FRP signals for Rust!
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript
hyperapp - 1kB-ish JavaScript framework for building hypertext applications
classnames - A simple javascript utility for conditionally joining classNames together
knockout - Knockout makes it easier to create rich, responsive UIs with JavaScript
React CSS Modules - Seamless mapping of class names to CSS modules inside of React components.