Semantic UI vs Semantic UI React: What are the differences?
Semantic UI: A UI Component library implemented using a set of specifications designed around natural language. Semantic empowers designers and developers by creating a shared vocabulary for UI; Semantic UI React: Integrating Semantic-UI and React. Semantic UI React is the official React integration for Semantic UI. jQuery Free, Declarative API, Shorthand Props, and more.
Some of the features offered by Semantic UI are:
- Build Responsive Layouts Easier
- Self Explanatory
- Tag ambivalent
On the other hand, Semantic UI React provides the following key features:
- No jQuery dependency
- No animation dependencies
- Reuse SUI CSS transitions
"Easy to use and looks elegant" is the primary reason why developers consider Semantic UI over the competitors, whereas "Great look&feel" was stated as the key factor in picking Semantic UI React.
Semantic UI and Semantic UI React are both open source tools. It seems that Semantic UI with 45.9K GitHub stars and 4.84K forks on GitHub has more adoption than Semantic UI React with 9.89K GitHub stars and 2.69K GitHub forks.
According to the StackShare community, Semantic UI has a broader approval, being mentioned in 77 company stacks & 55 developers stacks; compared to Semantic UI React, which is listed in 16 company stacks and 22 developer stacks.
What is Semantic UI?
What is Semantic UI React?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Semantic UI React?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Semantic UI?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling
import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.
React Helmet was chosen to handle
<head> content, because it works universally, making it easy to throw back the correct
<title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.
<style> tags when using #StyledComponents.
React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.
Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.
Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.
We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.
We use Semantic UI for our frotend. A heavily customised version of it, but still Semantic UI under the hood.
Used Semantic UI + Angular2 together with Spring or Node/Express for full stack web application development.