Semantic-ui: The Big Elephant in the room

[younggrandpa]

So I revisited Semantic UI after using the framework one time for a project three years ago. I thought I would use the framework in react and I spent three days solving dependency issues when installing the Semantic UI package. I remember having the same struggle in my old project but I sorted it out in just a day. I didn’t expect that installing Fomantic-UI solved the problem. Reading through the history of the community supported fork was like watching Mum and Dad fighting.

Apart from avoiding passive aggressive remarks like “Why would you want to do that?”, I’m not one who will post a question on forums without exhausting all efforts in finding a solution first. So I went through the rigmarole of researching and testing. Whilst I should have just typed ‘npm installation issues’ on Github’s search box instead of using google to get me to that thread where one dude suggested Fomantic-UI, one cannot discount the fact of the many instances of unanswered questions I’ve read in different threads. Refer to @GuacheSuede ‘s comments here.

Some of us just want to use the framework and program right away. This - just like back in the day when you have to pay for a Microsoft suite of development packages and installation was a breeze. Sure, it’s not free and one would still read through forums for issues. But there’s a business organisation who has the financial resources and people to steer the boat in the direction that their customers want their product to go. Thus, there’s a sense of trust and most of the time, processes are replicable and results are predictable.

I’m also not one who will rant in forums. I would be thankful for those who spent their time contributing to open source projects. And I’m aware of the risks of going with this route. The notion of ‘free’ libraries or components is flawed because of the time you spent solving issues. I think the thought of components coded by developers are scary enough especially when it gets deprecated and there’s no proper change management at all levels. I hate to think that correlating the choice for open source as a form of loss aversion and ending up costing me more. The question is if we want the open source movement to succeed what technical standards should we follow?

I propose also adding ethical standards into the picture. That said, I’d like _to address the big elephant in the room:_ Has development and support for the project has slowed down? I’m sure your reasons for being quiet are valid and people should have compassion. But for the love of God, please say something on your website that support for the project will end. If not, please answer people’s questions.

You guys might want to correct the first part of your documentation. If I may suggest:

• People have different levels of knowledge and skills. Specify the pre-requisites before they even start following the getting started section of your documentation.

• Most parts of the project documentation are very helpful. However, numerically outline  installation and tooling process as you’re defining steps. Consider grouping different options like in A. B. C fashion.

Perhaps open source shouldn’t be free and expensive? At the risk of sounding simplistic, devise a monetary incentive scheme where:

• One vote is equivalent to an X dollar figure. A system will divide the proceeds among those who qualify to receive a reward. (All things considered including countries who would find $1 equivalent in their local currency as expensive).
• There should be a central governing body every year. The community gets to vote who sits in the central committee.
• People who discover issues and explain the problem according to set standards receives a monetary reward.
• Members of the community gets to decide which issue is more pressing by putting in their votes. The central community members will prioritise the issue that gets the most votes. Everyone could vote as many times as they want. I’m sure their employers have a $ budget to spare.
• Members of the community gets to decide which enhancements is worth adding to development. The central community members will prioritise the issue that gets the most votes.
• Members of the community who knows the core system from the inside and out and can solve issues first gets a reward.
• Members of the community who can do technical writing receive a reward for improving a documentation for said solutions and/or new enhancements.
• The central community receives a reward for implementing changes to the core.
• A small percentage commission given to someone who can bring in a sponsor.
• Central community sets forum rules giving emphasis where everyone’s opinion matters but still encourage competition.

I'm not sure if there's a platform to implement the above suggestion. There's nothing really simple in our profession. The point is there are no free lunches.

Cheers!

[xumix]

Not going to lie, I've started using Semantic UI because of a great set of components and native React bindings, but looking at the current state of development I'm more and more looking back at Bootstrap

[GammaGames]

I've gone over to fomantic, development is active and they have a bunch of features and bugfixes Semantic has been needing. I'm still planning on porting existing apps over but for sure my future projects will be using fomantic.

[younggrandpa]

Not going to lie, I've started using Semantic UI because of a great set of components and native React bindings, but looking at the current state of development I'm more and more looking back at Bootstrap

@xumix To each his own I guess. Competition encourages product innovation. Bootstrap may have matured. When it was fairly new, we got into a problem where each frontend dev in our team had different interpretations of usage. It was probably a problem again on documentation. Nevertheless, Semantic-UI established a grammatical structure that was easy for every team member to understand. Speaking the same language -- if you'd like to call it that.

I've gone over to fomantic, development is active and they have a bunch of features and bugfixes Semantic has been needing. I'm still planning on porting existing apps over but for sure my future projects will be using fomantic.

@GammaGames Agree. As I've mentioned above, competition is healthy. I think letting Fomantic, grow on its own would be good. I hope though that Semantic-UI React will catch-up with the new modules like Calendar.

[xumix]

@younggrandpa Well, Semantic ui React dev explicitly said they were not going to switch to Fomantic
and this is excatly why I'm looking into react bootstrap

[younggrandpa]

@younggrandpa Well, Semantic ui React dev explicitly said they were not going to switch to Fomantic and this is excatly why I'm looking into react bootstrap

@xumix Go with what works for you. Let's see how their decision pans out.

[ptejada]

I came across tidelift a while ago. They must be doing something right that are still in business
https://tidelift.com/lifter/search/npm/semantic-ui