Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library
131–140 of 151 posts
Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library
#132This site got me going. Almost had whiplash when I tapped a link and the page loaded literally instantly. I've almost forgotten that that's possible on the internet. I'm not a web dev, but I'm inspired to get into it now because of this site.
I mean you also have HN as a reference.
Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library
#133This is of special interest to me, because man do I hate UI frameworks with tons of external dependencies. Looking at you, Bootstrap.
I used to think bootstrap was bloated too...and then i had heard - now, i don't know if its true - that bootstrap was originally intended *ONLY* as an internal prototype building tool, and any bloat did not matter...because expected audience, usage would be totally fine for a bloated framework...When i heard, i gave boostrap more of a pass...but, then again, i stopped using it, and began using other, lighter weight f…
Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library
#134Earlier quoted context omitted.
I'm not a web dev, what do you love about it?
It leverages semantic html elements for styling… it may not seem like a huge deal on the surface, but it’s very useful in keeping html page sizes down, keeping the html itself simple to use, and so on. there are other similar projects out, and i like them too.
Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library
#135Earlier quoted context omitted.
I mean you also have HN as a reference.
I use an app for HN, and try to wherever I can due to my general experience with web things, so it's a different feel. But also HN being snappy is pretty much an upfront expectation given it's like 99.99% text.
Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library
#136Thank you testing this on older browsers before releasing. This is truly an ultra minimal library - https://ibb.co/DDGmLYdg , https://ibb.co/h1WQG3GK
Genuine question, do you normally use old browsers as your daily driver for interfacing with the web? I’d be interested in learning why.
And just to be clear, I was poking fun at this so called “CTO”. That guy should have known better.
I see many web/ui frameworks posted in HN which don’t test in older browsers but still claim to be minimal or plain.
Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library
#137Earlier quoted context omitted.
I use an app for HN, and try to wherever I can due to my general experience with web things, so it's a different feel. But also HN being snappy is pretty much an upfront expectation given it's like 99.99% text.
TIL there is an HN app.
Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library
#138There’s a ton of semantic drop in css libraries similar to this. Love seeing new ones. Quality varies wildly but this site shows 50+ drop in stylesheets for those writing semantic html: https://dohliam.github.io/dropin-minimal-css/
do you have any recommendations from the list?
- water.css https://watercss.kognise.dev/
- magick.css https://css.winterveil.net/
- mui.css: https://www.muicss.com/
- pico.css: https://picocss.com/
Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library
#139Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library
#140Earlier quoted context omitted.
I used to think bootstrap was bloated too...and then i had heard - now, i don't know if its true - that bootstrap was originally intended *ONLY* as an internal prototype building tool, and any bloat did not matter...because expected audience, usage would be totally fine for a bloated framework...When i heard, i gave boostrap more of a pass...but, then again, i stopped using it, and began using other, lighter weight f…
The problem with Bootstrap is that it depends on jQuery and Popper, and its CSS has global classes. It’s perfectly fine if BS is the only UI framework, but if you need to bring to bring in other frameworks or libraries (by choice or by force), then there’s a chance you’ll run into conflicts.