Live data from Hacker News

Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library

oat.ink

81–90 of 151 posts

Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library

#81

This 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.

You should try making a site with Astro. Load speed is cray cray.

Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library

#83
post #34

Earlier quoted context omitted.

The author is the CTO of Zerodha, India’s largest online brokerage. Not that it matters, just an observation.

A CTO that codes? Interesting indeed.

That's pretty common in small companies. It's less common in large companies but can happen - you may use the "CTO" title for the founding engineer who still leads code and architecture, then hire someone under a different title (frequently "VP of Engineering") to handle the management / team growing side of the role.

Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library

#85

What's with variable names starting with "#" as first character?

That's just markdown headers. Some people like to include # as part of the header aesthetic

No, the Q was about javascript not markdown. Peer comment from afishh (9m after yours) has it right.

Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library

#86
I think it's valiant to try to do all of this with semantic HTML elements to achieve the right effects, and try to go for a "classless CSS" paradigm to get a nice looking and functional web app (as a fan of classless CSS myself). But scrolling through the component catalog, it unfortunately feels like it's all over the place and inconsistent with semantic vs basic elements, data tags vs aria attributes, and sprinkling some css classes over some of it.

I do very much like that by introducing aria attributes, the CSS reacts to it and styles it appropriately. As opposed to a full-blown react component library which does all of that for you. It would be a good exercise for developers to think aria-first and let the library just help with styling.

Lastly, I think the best part is that this component library has a native sidebar. So many of these I see and they have a nice web page which showcases all the components and I want to replicate their layout and nav/sidebars but they only focus on smaller re-usable components and not the layout. So that's a nice touch, I think. And, as someone who keeps an eye on but doesn't do a lot of frontend, the fact that a sidebar is an aside > nav > ul next to a main just makes so much sense and doesn't have a lot of cruft around it.

Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library

#87

There’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/

I love it. You can use the right arrow to cycle through them.

Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library

#88
post #28

No Datepicker?

As pointed out in another comment, it's under the form elements, not listed as a top-level component as many UI libraries do https://oat.ink/components/#form Which actually makes sense: Oat's driving philosophy seems to be to use and enhance native controls as much as possible, and the date picker is already a native type on the input element.

Thanks, I missed that when looking through the component list on the top level.

Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library

#89
post #83
post #34

Earlier quoted context omitted.

A CTO that codes? Interesting indeed.

That's pretty common in small companies. It's less common in large companies but can happen - you may use the "CTO" title for the founding engineer who still leads code and architecture, then hire someone under a different title (frequently "VP of Engineering") to handle the management / team growing side of the role.

That sounds like a reasonable split to me, so much so I’m not sure I’d understand why you’d want the same person handling both code/architecture and management.

Re: Oat – Ultra-lightweight, zero dependency, semantic HTML, CSS, JS UI library

#90

People need to stop with these stupid 12 column grids and learn how grid and flex work. Other elements are ok but this is just stupid

It's a 12 column grid system built with CSS Grid. 12 column grids are a common design pattern. What would you propose instead?
Post reply on HN