Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please Bring it back? #142

Open
kaigouthro opened this issue Nov 11, 2018 · 1 comment
Open

Please Bring it back? #142

kaigouthro opened this issue Nov 11, 2018 · 1 comment

Comments

@kaigouthro
Copy link

When i looked over the styling and everything, it blew my mind that the official semantic react release looks pretty much like bootstrap with a couple bonuses. your version is a whole other level of "damn that's sexy"... and new types of components.. i'm going to work on my next project in tandem, one with the official and one with yours, and see which i like better and comes out better.

i would love to see this completed fully and extended, or even combined with the other library just to get your CSS plugged into official cannon.

@hallister
Copy link
Owner

I think this project still has potential, but functionally speaking it would obligate Semantic itself to reverse course from its current state.

Semantic's CSS is a nightmare. It's entire design is dated and completely breaks the "top down" model that a view library like React expects. That's why the official React port of Semantic is designed the way it is. It's trying to fit React into a model it was never designed to fit in.

The future of this project is dependent on one of two things:

  1. Semantic completely rewrites the CSS from the ground-up that doesn't rely on jQuery as the solution to virtually all its problems.
  2. This project completely removes Semantic as a dependency and moves to a CSS-in-JS solution to Semantic.

The former is a challenge because the there's little-to-no support for Semantic financially, and not a lot of contributors to the core project. (see Semantic-Org/Semantic-UI#6109), the latter is an enormous undertaking that would require a great deal of either financial or dev support which a 43k starred project like Semantic can't even get, let alone a version that goes in a different direction than the official React port.

At the end of the day, corporate support is what a project the size of Semantic really needs, but that's really hard to get for UI libraries, because all the major corporations employ their own designers/design languages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants