Hacker News Reader

Comment by peterangular | Hacker News Reader

Hasn't had any updates for two years and looks like it's doing something weird with the base font inclusion assuming you have "nunito" already (not a safe assumption).

Also I'd suggest to anyone to potentially avoid using CSS vars if you're looking for enterprise browser support due to old IE. Obviously make your own decisions on this one but it I think 10 starts getting really weird with them...

All-in-all for the limited benefit this micro-lib brings I'd say go to something that's popular/supported vs. a project that hasn't seen a commit in 2 years.

View on HN

> I'd say go to something that's popular/supported vs. a project that hasn't seen a commit in 2 years.

Isn't the whole point of a micro lib that it is limited in scope, well-designed, and shouldn't need to change much? I have my own libraries that see few commits as of late but still work fine

I haven't tried this yet, but in the author's defense the repo has no issues against it, so it's not like there is tangible proof that the author is neglecting maintenance or anything. Besides, the whole thing <500 lines of CSS - if it does what you need it to why go with anything that would be more complicated and more likely to break with an upgrade?

Isn't the whole point of a micro lib that it is limited in scope, well-designed, and shouldn't need to change much?

In the case of a CSS framework specifically, browsers are a moving target and you would expect changes to either fix issues or to take advantage of new features. 2018 is more than 10 versions of Chrome old, and while it's possible that nothing in that time was worth adding to this framework it does seem unlikely. At the very least you'd expect a line in a readme to be updated to say its been tested and it works.

As long as the old thing works there is no reason to chase the new features, especially because they are by definition not available in old browsers.

Sure, which is exactly why I said I'd expect at least an occasional update to a readme to say the framework has been tested and still works.

More broadly for web dev though, the fact a feature isn't available in old browsers is a bad a reason not to use a new feature if it's useful and improves a site for the user. Obviously you shouldn't break your site in old browsers but progressively enhancing to take advantage of things is a very good thing. Browsers implemented @supports in CSS for precisely this reason.

Water.css is a credible alternative: https://kognise.github.io/water.css/

Discussion: https://news.ycombinator.com/item?id=19593866

Interesting it errors under safari technology preview r105 when I hit switch theme button, works fine under safari though both on Mac/iOS.

Hey, developer of Water.css here - I'll take a look!

It doesn't use variables in the minified version where the vars are already expanded: https://raw.githubusercontent.com/ajusa/lit/master/dist/lit....

Also how much support & udpates do you want to see in a piece of CSS that's barely a dozen blocks? It's a strange comment to make.

A friend of mine made PrefaceCSS:

https://cluzier.github.io/PrefaceCSS/dist/index.html

I really like this one. It's still got a minimal old school feel but with enough style to not look... unstyled.

I have to admit, I found the wonky vertical alignment of the text on the buttons really off-putting (caused by Nunito).

> Also I'd suggest to anyone to potentially avoid using CSS vars if you're looking for enterprise browser support due to old IE.

You can trivially process your css files through babel + postcss to support arbitrary browser targets. In this case, postcss will inline the vars letting write modern css while shipping css that works in old browsers.

Reply on news.ycombinator.com