Based on our record, React.run seems to be a lot more popular than Garden (Clojure). While we know about 176 links to React.run, we've tracked only 2 mentions of Garden (Clojure). We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Thanks for the vanilla-extract recommendation, I'll be using this! In my case, tailwind was useful for providing a handy set of vocabularies for simple and common stylings. But once customizations start to pile on, we're back into SCSS. Using 2 systems at once meant additionally gluing them with the postcss toolchain, so effectively we have 3 preprocessors running for every style refresh. Looking in at TypeScript... - Source: Hacker News / over 1 year ago
I spent some time doing this ~3 years ago, so I don't know about now, but to my knowledge it was the only language where you could really use one language for everything: no HTML (via hiccup), no CSS (via garden), clojure/clojurescript everywhere, and no shell (via babashka). Source: almost 2 years ago
The official React docs don’t share the same sentiment. They currently recommend the Pages Router and describe the App Router as a “Bleeding-edge React Framework.”. - Source: dev.to / about 11 hours ago
The official react docs recommend using a meta framework for new projects: https://react.dev/learn/start-a-new-react-project This leads me to wonder, do they practice what they preach? If so what meta-framework do they use with react? Is it something in house? - Source: Hacker News / 3 months ago
Https://react.dev/learn/start-a-new-react-project. - Source: Hacker News / 3 months ago
"If you want to build a new app or a new website fully with React, we recommend picking one of the React-powered frameworks popular in the community." Documentation. - Source: dev.to / 3 months ago
As of writing this, there's a lot of criticism of React and where its heading. Apparently, React themselves recommend using a meta-framework and not just "plain React" in their "getting started" page, which is... interesting. I particularly resonated with this article, and also enjoyed this funny video, which I think explains the current turmoil in the React ecosystem (and FE ecosystem in general) pretty well. - Source: dev.to / 4 months ago
CSS Next - Use tomorrow’s CSS syntax, today.
React - A JavaScript library for building user interfaces
Stylecow - CSS processor to fix your css code and make it compatible with all browsers
Vite - Next Generation Frontend Tooling
PostCSS - Increase code readability. Add vendor prefixes to CSS rules using values from Can I Use. Autoprefixer will use the data based on current browser popularity and property support to apply prefixes for you.
Node.js - Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications