<a href="https://github.com/fosiao/rclone-webui-oat" rel="nofollow">https://github.com/fosiao/rclone-webui-oat</a> seems replacing the heavy duty unmaintained react version at <a href="https://github.com/rclone/rclone-webui-react" rel="nofollow">https://github.com/rclone/rclone-webui-react</a>
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.
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.<p>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.<p>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.
This has the simplicity I thought I was going to get from DaisyUI but didn’t. Pairing this with Datastar seems like a super powerful combination that leans on actual web standards, not “ecosystems”.
The motivating blog post[1] linked from the front page is probably going to generate a more interesting discussion than the framework itself.<p>As someone who has to deal with both angular and nextjs for different (but overlapping) stacks at work, I find myself increasingly sympathetic to this viewpoint.<p>[1]: <a href="https://nadh.in/blog/javascript-ecosystem-software-development-are-a-hot-mess/" rel="nofollow">https://nadh.in/blog/javascript-ecosystem-software-developme...</a>
Nice link - still relevant IMNHO - even though it's from 2021.<p>Discussed at the time:<p><a href="https://news.ycombinator.com/item?id=28892933">https://news.ycombinator.com/item?id=28892933</a>
This website pleases me greatly. 0 time from tap to fully loaded pages.
Previously (2021): <a href="https://news.ycombinator.com/item?id=28892933">https://news.ycombinator.com/item?id=28892933</a>
<aside> is not the correct semantic element for sidebars. The purpose of <aside> is for content that is indirectly related to the "main" content of the page. Sometimes a sidebar fits that definition but not always
Looks good and like the lightweight aspect. As always, what do I have to do get tabs that look like tabs? What do people have against tabs that look like tabs, instead of buttons?
I tried doing something like that in my app, and quickly discovered that some modern semantic/functional tags are STILL not supported in some browsers. Or work badly.<p>For example, in Safari showModal for a dialog tag causes recalculating layout for EVERY element on a page, it’s up to 59x slower than chromium…. :(<p>But I love the idea
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: <a href="https://dohliam.github.io/dropin-minimal-css/" rel="nofollow">https://dohliam.github.io/dropin-minimal-css/</a>
I had to read your comment three times before figuring out that you mean “drop-in”. Sometimes hyphens do matter! :)
This isn't upvoted enough. This is more interesting than the OP's project! Thanks for sharing!
I love it. You can use the right arrow to cycle through them.
do you have any recommendations from the list?
Nice solution. Reminds me of <a href="https://semantic-ui.com/" rel="nofollow">https://semantic-ui.com/</a> and <a href="https://fomantic-ui.com/" rel="nofollow">https://fomantic-ui.com/</a>
Thank you testing this on older browsers before releasing. This is truly an ultra minimal library - <a href="https://ibb.co/DDGmLYdg" rel="nofollow">https://ibb.co/DDGmLYdg</a>,
<a href="https://ibb.co/h1WQG3GK" rel="nofollow">https://ibb.co/h1WQG3GK</a>
Confusing name, conflicts with Oat++?<p><a href="https://oatpp.io/" rel="nofollow">https://oatpp.io/</a>
The "preview" and "code" buttons in the components break the "alt+arrow" bindings to go back to the previous page. Instead it just alternates between "preview" and "code".
Reminds me of what bootstrap [1] was like around a decade ago. It's gotten quite a bit bloated since then though.<p>1. <a href="https://getbootstrap.com/" rel="nofollow">https://getbootstrap.com/</a>
Why do all the UI component libraries always feature an accordion (something i can build myself in 5 minutes and very rarely need), but always omit a date picker / calendar component (something that is needed almost in every corporate web form and really requires a lot of effort to build)?
This is a very nice library. At a first reading it seems complete (but did I see summary/detail - I don't remember). Bookmarked for further investigation. Congratulations and thank you.
This 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 frameworks...and nowadays, i so rarely touch any web stuff...and when i do its only for me so then use zero frameworks, and merely display whatever default the browser shows with zero CSS, javascript...then again, my private web page needs are so basic anyway.
This is gorgeous. I hate frontend because of its sheer gratuity, and this is the kind of thing that might get me back into it. The only other contender for interactivity I'd consider is HTMX, and I'm going to boldly assume I'll be able to combine them without too much bother.<p>Bravo to the author, keep at it. I'll be recommending this to anyone who will listen.
Surprised that none of the comments here are comparing this to Bootstrap.
Great work! PicoCSS feels a bit <i>too</i> minimalist at times. This looks like a better balance of lightweight and functional.
It’s a bit odd that the accordion uses details but the dropdowns require a custom element.
I know that guy from listmonk! I always thought the frontend could use some love and planned to spend a couple of days on contributing a couple of ideas, but I never came around. Now I know why things are as they are :)
Seems pretty unresponsive to me. I'm getting at least half a second of delay before the accordion, drop-down, or switch do anything. Chrome on Windows.
Was looking at the spinner component for a few seconds thinking "that's a bit slow"...
ultra-lightweight, these dev's probably go hiking. I like : )
Thank you for sharing, I would like to see a navigation/menu component added though as that's required for most websites.
What's with variable names starting with "#" as first character?
If you are referring to class members in the JavaScript then those are private fields[1]<p>[1] <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_elements" rel="nofollow">https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...</a>
That's just markdown headers. Some people like to include # as part of the header aesthetic
My initial reaction was that I have to use this just because of the buzzword density in the title. But after reading up, it looks like the author was pretty successful in moving the bloat from code to announcement title. I'll give this a try!
Amazing! I recently started building something similar for the same reasons, but more out of frustration rather than out of desire. I'll have to give this one a try and see if it fills the need.
Nice job! Clicked tru my obscure mobile firefox and all worked well!
If nothing else, it's refreshing to see nicely modern CSS and JS formatted and laid out in a legible manner.
<a href="https://github.com/knadh/oat/tree/master/src" rel="nofollow">https://github.com/knadh/oat/tree/master/src</a>
This looks very very cool. Will definitely look in to using this for more static internal tools!
Thank you for this, can’t wait to use. Minimalism at its best.
how do you contrast this with <a href="https://picocss.com/" rel="nofollow">https://picocss.com/</a> ?<p>I like your presentation of the components, but i'm having trouble finding the essential distinctions
The form component:<p><a href="https://oat.ink/components/#form" rel="nofollow">https://oat.ink/components/#form</a><p>Looks a lot like a raw HTML+CSS framework I made in 2009:<p><a href="https://alganet.github.io/ghiaweb/" rel="nofollow">https://alganet.github.io/ghiaweb/</a> (it has some small glitches, browser widgets changed a lot since 2009).<p>Particularly the use of the label, fieldset and legend elements as native accessible solutions instead of instrumenting divs. Even the styling and the example resembles it a bit!<p><a href="https://oat.ink/components/#grid" rel="nofollow">https://oat.ink/components/#grid</a><p>This is where it falls from grace IMHO. Grid classes are fundamentally non-semantic. I know they're popular and useful, but there must be a better (semantic) way of doing this. I haven't found it yet, but there must be.
The code example doesn't render for me.
No, this is "Oat - Ultra-lightweight, semantic, zero-dependency Javascript UI component library". If it doesn't work without javascript it is not an HTML UI component library.
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
Claims no classes but uses data- attributes and also classes (just look at the button example…)<p>Looks okay, but I don’t see why to use this over something like Marx if all you need is to not have bare browser default styling.
should call it oatmilk for max exposure
5 day old repo, 2000 stars on GitHub, 400 total weekly downloads on npm. Frontpage of hacker news with a bunch of weird comments. Moderation has been lacking recently.
You are jumping to conclusions. The author is the CTO of the largest online brokerage in India but more importantly, they have created many open source software of good quality. His website and blog are of great quality. Whether you think this library deserves more attention or not is your personal preference but it is far from spam. I havr no affiliation with them but like their work.
I'm not sure which comments you're finding weird, but I spot checked a bunch and didn't see anything that looked particularly bogus, other than <a href="https://news.ycombinator.com/item?id=47026348">https://news.ycombinator.com/item?id=47026348</a> and some trollish ephemera.<p>The upvotes on the submission look legit to me, as does the submission itself.
The author is the CTO of Zerodha, India’s largest online brokerage. Not that it matters, just an observation.
I thought they also OSSed a pretty solid <a href="https://github.com/frappe/helpdesk" rel="nofollow">https://github.com/frappe/helpdesk</a> helpdesk but that was from Frappe, not Zerodha.
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.
CTO in my company* remains SME on a several components, commits to several production repositories (and expects the most stringent PR checks), and maintains couple of small tool used by us and the customers.<p>Its not that rare I think.<p>*small fintech with couple of billions in the accounts, not a startup, not a Fortune 500 company
Sad that HN is now also getting boted by LLMs. People are just shameless. HN is one of the few places left where you can post / self promote something you have made only for people to take advantage of it.
This is kind of misleading. It says it's an HTML UI library, then it says HTML + CSS, and then it says it also includes JavaScript. Why is this better than, say, DaisyUI?
(Submitted title was "Oat – Ultra-lightweight, semantic, zero-dependency HTML UI component library" - we've replaced it now)
Iirc there's a few web components in there which would require js.
I just want something that's as easy to use as DaisyUI or even Bulma with one good set of components & themeing(beyond just palletes, like rounding, blur, transparency etc) & I'm good. For all the self-hosting model afficianados surely needing a build platform to create a blackhole of npm modules & internet connectivity for even a single build surely negates the entire point of a coding LLM if we still force it to deal with frontend
You mean you want DaisyUI but with extended theming, like ability to make inputs, etc, rounded? This is also something I was considering.
[dead]
[flagged]
[flagged]
[flagged]
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<p><a href="https://oat.ink/components/#form" rel="nofollow">https://oat.ink/components/#form</a><p>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.
But there's no enhancement here. That's just the native date picker control with a bit of styling on the textbox portion of it.
Thanks, I missed that when looking through the component list on the top level.
I'm not a web dev, but doesn't HTML come with a date picker?
I love it. We need to see more of this.
This does not even need a LLM skill, just load the whole code up in context, so efficient.