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

91–100 of 257 posts

Re: Semantic UI

#92

Post by NicoJuicy »

du_bing wrote: post #76
NicoJuicy wrote: post #59

Earlier quoted context omitted.

I hate to say this, but when I opened this with my smartphone, the layout was not responsive. So I closed it again

Co-worker here, yeah, truly some pages of the site are not yet quite responsive, sorry for that, we plan to improve it in the future. On the site there are some particular templates designed to show the responsiveness or non-responsiveness, you could open them on smart phone or desktop computer to see the differences: http://semantic-ui-forest.com/templates/bootstrap/grid/ http://semantic-ui-forest.com/templates/boot…

I think it's not detecting my mobile as mobile. Motorola Play X here in Android, chrome

Re: Semantic UI

#93

Post by nkkollaw »

It looks great.

However, I've used it in the past and the CSS size is _HUGE_, with no way to reduce it. We're talking about > 500KB of CSS (in my case, at least). The JavaScript is extremely bloated as well.

Honestly, being that heavy I wonder how anyone can use it. If your site is to be viewed by mobile users, adding 500KB just to style a few elements is unacceptable.

I'd much rather go with Bootstrap. It has the added benefit of having the majority of front-end devs know it, and you can buy or use a theme for free and make it look great.

Re: Semantic UI

#94

Post by chenshuiluke »

frik wrote: post #36
sheeshkebab wrote: post #4

This doesn't work well on mobile - on iOS at least... scrolling is funny, flickering screens, jerky inputs. Loading feels slow too - and I'm on wifi.

The worst site I visited the last 7days (iOS). A lot of things broken, flickering, broken scrolling, overlapping things, slow, laggy, buggy. Do you even test for mobile? Why is this on HN frontpage?

Because its an otherwise very useful and good looking CSS library.

Re: Semantic UI

#95

Post by rvanmil »

TomFrost wrote: post #32

Semantic recently adopted my team's React adaptation as their official React port. It's lighter weight, eliminates jQuery, and all components are standard React components that can be extended or dropped in as-is. https://react.semantic-ui.com/

I've been looking for a replacement for Bootstrap since it's been alpha for ages and it doesn't look like there is any interest in an official React implementation. So this might be it, I'm going to give it a try :)

Re: Semantic UI

#96

Post by wruza »

du_bing wrote: post #76
NicoJuicy wrote: post #59

Earlier quoted context omitted.

I hate to say this, but when I opened this with my smartphone, the layout was not responsive. So I closed it again

Co-worker here, yeah, truly some pages of the site are not yet quite responsive, sorry for that, we plan to improve it in the future. On the site there are some particular templates designed to show the responsiveness or non-responsiveness, you could open them on smart phone or desktop computer to see the differences: http://semantic-ui-forest.com/templates/bootstrap/grid/ http://semantic-ui-forest.com/templates/boot…

The rendering is awful and somewhat irrational for all three links on my phone. Was that designed to show non-responsiveness?

Re: Semantic UI

#97

Post by wruza »

xiaohanyu wrote: post #31

Hi, guys, We have spent hundreds of hours build a new website with Semantic-UI for Semantic-UI: http://semantic-ui-forest.com/ . Semantic-UI is my favourite front-end CSS website, I have built several websites with Semantic-UI, and I love it, feel delightful when developing with Semantic-UI. But compared with Bootstrap, the ecosystem of Semantic-UI is small, so we have semantic-ui-forest for you: http://semantic-ui-f…

>Not advertising

A SEO expert walks into a bar, bars, pub, public house, Irish pub, drinks, beer.

Re: Semantic UI

#98

Post by BilalBudhani »

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?

Re: Semantic UI

#99

Post by SerLava »

RubyPinch wrote: post #61
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…

> you only have to touch your stylesheets instead of manipulating both the stylesheets and HTML. Well isn't the point here that you'd only have to modify the HTML, leaving the CSS alone for the most part?

I find that this is such a superior approach for certain websites. If a site has a large number of secondary pages designed around totally different content, the "only touch the stylesheet" seems to lead to despair.

I've seen people crap out things like #aboutPage #mainContent p:nth-child(2) div button {styles go here} ... because they follow the "separation" concept blindly. And then, you know, a paragraph gets added in later. Made up example but you get the point.

Re: Semantic UI

#100

Post by rimliu »

jasim wrote: post #58
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…

The concept of 'semantic classnames', even if propagated by w3.org has caused as much grief as the concept of 'separation of concerns' between HTML & CSS fad. The reason we need semantics in HTML is to make the markup accessible for screen-readers, and no screenreader considers the class name of an element when reading it out. What we instead need are semantic tags like article, section etc. and aria tags like role.…

Semantic names for CSS classes have the same utility as good variable/function/method names in code. They describe what is this for, not how should it look. I have seen enough .red12px where it was green and 10 px already. Cannot wait for the new web standards movement to start already.
Post reply on HN