FaxJs
unocss
Our great sponsors
FaxJs | unocss | |
---|---|---|
6 | 56 | |
388 | 15,339 | |
- | 2.3% | |
0.0 | 9.6 | |
almost 3 years ago | 4 days ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 or later | 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.
FaxJs
-
Is React Having An Angular.js Moment?
More accurately, Facebook engineer Jordan Walke created the small UI framework FaxJs, Facebook realized that a technology like this could solve their horrible mess of cascading DOM updates that made it near-impossible to make product improvements, and they soon turned it into React.
-
Maud: A Rust macro for writing HTML
That's actually the heritage of JSX!
XHP was launched in 2010 (https://www.facebook.com/notes/10158791323777200/)
The first version of FaxJs (the precursor to React) was launched in 2011, being directly inspired from XHP (https://github.com/jordwalke/FaxJs)
React was made in 2012 by the same person who made FaxJs, taking the best ideas from FaxJs and creating React.
So yeah, JSX actually comes from the idea of XHP :)
-
Why React Functional Components are the future?
React was introduced to the world in May 2013 at a JavaScript conference in the US. It proved to be a game-changer and quickly became the king of JavaScript libraries. It was brought into existence by Jordan Walke, a software engineer at Facebook. He also created FaxJS in 2011, the early prototype of React.
-
State of the Web: React
Around a decade ago, Facebook started looking for a way to modernize its web app. It was becoming increasingly complicated, and they needed a framework to make it easier to build and maintain. To fix this, they created a project called Bolt. Bolt was an MVC framework built on top of JavelinJS, and it solved many of the problems Facebook had. However, it was not perfect. Jordan Walke, a developer at Facebook, created the next iteration of Bolt, called FaxJS. It offered many features that React has today, like rendering on both client and server, DOM diffing, and more. Jordan Walke renamed FaxJS FBolt and started using it in Facebook's codebase.
-
Top JavaScript Trends to Watch in 2021
Source: FaxJs on GitHub
-
Learning how frontend frameworks are built. Help!
Also keep in mind that when React was created by Jordan Walke, he was trying to solve a very specific problem (correctly displaying notification / message counts, which was a big issue at Facebook at the time), and not setting out to create a complete and all-encompassing UI framework. If you're interested in the prototype, FaxJS, which he created, and which subsequently spawned React, here's the repo: https://github.com/jordwalke/FaxJs
unocss
-
Tailwind CSS v4.0.0 Alpha
I wish tailwind would support attributify like https://github.com/unocss/unocss, which is much more readable for complex layouts:
link
- UnoCSS — an Instant On-Demand Atomic CSS Engine
-
Catalyst – Tailwind CSS Application UI Kit
I feel the same about people praising Tailwind.
Tailwind (and similar, I tend to use https://unocss.dev/) is not good for your frontend architecture BUT they allow you to be so fast, that it negates the benefits.
For a job well done, I'd follow the principles of https://maintainablecss.com/
-
What do you think we can do better to improve Vue position in the frontend space as a dominant UI framework?
I think UnoCss is may be better than Tailwind already and has a good Vue integration https://unocss.dev/
-
~~New~~ Old way to write CSS
The most popular tools that implement this approach are: Tailwind, WindiCSS, UnoCSS.
-
Which is best for DX and efficiency, TailwindCSS, UnoCSS, PandaCSS, or the new MasterCSS
- UnoCSS: https://unocss.dev/
-
A design system for the federal government
haha, fair point. Still, I'm on the fence about how utility components are namespaced in USWDS. Perhaps giving users the flexibility to define the namespace might work better? One thing that bugs me is the absence of class-sorting like we have in TailwindCSS. Plus, there are some gaps I've noticed in USWDS. The naming, especially when comparing "padding-x-2" and "p-x-2", can be really annoying when switching around, maybe that could also be an option for the developer or project. Similar to the ideas antfu has on uno.css https://unocss.dev/ ♥
-
Modern CSS Framework or Library for Static Websites?
UnoCSS is a popular option
-
Vrite Editor: Open-Source WYSIWYG Markdown Editor
UnoCSS — for styling with Tailwind-like atomic CSS;
-
Why I Switched From Neovim to VSCode
Some exceptional libraries and frameworks only support VSCode, which you could argue is a bad thing, but it makes sense, VSCode is the most popular code editor after all. For example UnoCSS only has a VSCode extension, and it's my favourite way to write CSS. Astro has a LSP but I've found that the experience in VSCode is much better than in Neovim.
What are some alternatives?
React - The library for web and native user interfaces.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
htmlgo - Type safe and modularize way to generate html on server side.
windicss - Next generation utility-first CSS framework.
Preact - ⚛️ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.
tail-kit - Tail-kit is a free and open source components and templates kit fully coded with Tailwind css 3.0.
xhp-php5-extension - A PHP5 extension that augments the syntax of the language such that XML document fragments become valid PHP expressions.
unplugin-vue-components - 📲 On-demand components auto importing for Vue
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
Quasar Framework - Quasar Framework - Build high-performance VueJS user interfaces in record time
whichever-compiles
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript