Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Semantic UI

semantic-ui.com

Post reply on HN
Print view View original

121–130 of 257 posts

Re: Semantic UI

#121

Post by [deleted] »

Mikhail_Edoshin wrote: post #85
jameslk wrote: post #34

I've always found it ironic that this library calls itself "Semantic UI" but doesn't follow the practice of semantic HTML/classes[0]. W3C suggests[1] that classes should be used for semantic roles (e.g. "warning", "news", "footer"), rather than for display ("left", "angle", "small" -- examples taken from Semantic UI's docs). So instead of giving a button the class of "button" it would be better to give it a class suc…

I always found that "semantic" approach very misleading. In computer languages "semantics" is what the computer does with your input. This is the semantics of C, for example. Markup languages are no different. Until you have a clear specification what computer does with the markup, you have no semantics. I.e. , , and tags have perfect semantics, while things like or have none or very vague wishy-washy one.

[deleted]

Re: Semantic UI

#122

Post by vinayakkulkarni »

BilalBudhani wrote: post #98
vinayakkulkarni wrote: post #91

Just FYI, https://www.zomato.com/ one of the biggest in it's industry uses Semantic-UI :) Love the Framework and Jack + all contributors effort in it :)

Whoa! This is interesting. Just curious to know - how did you decide to go with Semantic UI? - what all frameworks did you compare? - which preprocessor are you using?

I ain't working in Zomato :P

Got the info from this thread: https://github.com/Semantic-Org/Semantic-UI/issues/2449#issu...

Re: Semantic UI

#125

Post by pedalpete »

tomelders wrote: post #104

Please stop with these things. They're never fit for purpose, and now there's another thing that looks - to non technical people - like a panacea for all development woes. Designers will never follow your constraints. Managers will never understand why this hasn't magically reduced our estimates by 90%. And yet again, it's just "developers being difficult" because there's a bunch of guys in India who say they CAN wor…

Nobody is forcing you to use it. I don't use these libraries anymore, but that doesn't mean they don't have a purpose. And no, people shouldn't 'stop with these things'. You shouldn't be the one telling people what they should and should not be doing. You don't have to like it, but there are many developers who are really bad at styling. They don't have a good eye for design and they're trying to build a usable product, or they have an internal need, or want to learn. Libraries such as these have many purposes, even if you don't like them.

Re: Semantic UI

#126

Post by nailer »

andrewingram wrote: post #117
nailer wrote: post #114

Earlier quoted context omitted.

> If I move a component from one place to another, I expect it to look the same (with a caveat for responsive layouts) assuming it's still rendered with the same input properties. What's preventing you from doing this with your presentation login in your stylesheet, and what about this requires you to split your presentation logic between a stylesheet and HTML? We use components everywhere. We style in stylesheets. H…

Sorry, i'm struggling to follow what you're asking here. Whether you style in stylesheets or by some other means (CSS-in-JS?) is an implementation choice rather than something that affects the fundamental pattern. If your components are truly portable, you're already doing things the way I suggest. If they inherit things like fonts and colors from their parent via the cascade rather than via explicit properties, then…

> Whether you style in stylesheets or by some other means (CSS-in-JS?)

We're specifically talking here about putting styling logic - "left" "shiny" "big" etc - in HTML.

> is an implementation choice rather than something that affects the fundamental pattern.

Sure, you can still use a component pattern with styling split into HTML and stylesheets - it certainly doesn't effect the pattern.

The issue is: when you want to change the appearance of your component, do you want to modify styling logic in two places or one?

Re: Semantic UI

#127

Post by hnlauncher »

jameslk wrote: post #34

I've always found it ironic that this library calls itself "Semantic UI" but doesn't follow the practice of semantic HTML/classes[0]. W3C suggests[1] that classes should be used for semantic roles (e.g. "warning", "news", "footer"), rather than for display ("left", "angle", "small" -- examples taken from Semantic UI's docs). So instead of giving a button the class of "button" it would be better to give it a class suc…

That W3 tips link is a decade old and not in any way normative. Appealing to it's authority is silly IMO and talking about semantic CSS like one does semantic HTML is even sillier as semantic CSS doesn't exist in the HTML sense.

Re: Semantic UI

#128

Post by Rotareti »

malloryerik wrote: post #17

Might also check out Ant Design. https://ant.design/ It's integrated with React and there's a separate mobile UI for it. Ant is Chinese, with docs translated into English. Like China, it's huge^^ I've just been fooling around with it today for the first time in create-react-app and seems good so far. Haven't tried on mobile.

Looks great! I wish the doc was fully translated though.

Re: Semantic UI

#129

Post by ludbek »

I have been using Semantic UI for a while now. Overall I love this framework. It has lots of essential components. I highly recommend it to lean startups who dont have enough expertise for designing and developing their own UI components.

But I do hate it for having weak and restrictive responsive queries.

Re: Semantic UI

#130

Post by andrewingram »

nailer wrote: post #126
andrewingram wrote: post #117

Earlier quoted context omitted.

Sorry, i'm struggling to follow what you're asking here. Whether you style in stylesheets or by some other means (CSS-in-JS?) is an implementation choice rather than something that affects the fundamental pattern. If your components are truly portable, you're already doing things the way I suggest. If they inherit things like fonts and colors from their parent via the cascade rather than via explicit properties, then…

> Whether you style in stylesheets or by some other means (CSS-in-JS?) We're specifically talking here about putting styling logic - "left" "shiny" "big" etc - in HTML. > is an implementation choice rather than something that affects the fundamental pattern. Sure, you can still use a component pattern with styling split into HTML and stylesheets - it certainly doesn't effect the pattern. The issue is: when you want t…

One, that's why I style inline :)
Post reply on HN