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.
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.
[1]: https://nadh.in/blog/javascript-ecosystem-software-developme...
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…. :(
But I love the idea
Discussed at the time:
Bravo to the author, keep at it. I'll be recommending this to anyone who will listen.
https://oat.ink/components/#form
Looks a lot like a raw HTML+CSS framework I made in 2009:
https://alganet.github.io/ghiaweb/ (it has some small glitches, browser widgets changed a lot since 2009).
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!
https://oat.ink/components/#grid
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.
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.
I like your presentation of the components, but i'm having trouble finding the essential distinctions
Oat is an ultra-lightweight HTML + CSS, semantic UI component library with zero dependencies. No framework, build, or dev complexity. Just include the tiny CSS and JS files and you are good to go building decent looking web applications with most commonly needed components and elements.
Semantic tags and attributes are styled contextually out of the box without classes, forcing best practices, and reducing markup class pollution. A few dynamic components are WebComponents and use minimal JavaScript.
6KB CSS, 2.2KB JS, minified + gzipped.
That's it.
Fully-standalone with no dependencies on any JS or CSS frameworks or libraries. No Node.js ecosystem garbage or bloat.
Native elements like <button>, <input>, <dialog> and semantic attributes like role="button" are styled directly. No classes.
Semantic HTML and ARIA roles are used (and forced in many places) throughout. Proper keyboard navigation support for all components and elements.
Easily customize the overall theme by overriding a handful of CSS variables. data-theme="dark" on body automatically uses the bundled dark theme.
This was made after the unending frustration with the over-engineered bloat, complexity, and dependency-hell of pretty much every Javascript UI library and framework out there. Done with the continuous PTSD of rug-pulls and lockins of the Node.js ecosystem trash. [1] I've published this, in case other Node.js ecosystem trauma victims find it useful.
My goal is a simple, minimal, vanilla, standards-based UI library that I can use in my own projects for the long term without having to worry about Javascript ecosystem trash. Long term because it's just simple vanilla CSS and JS. The look and feel are influenced by the shadcn aesthetic.
The upvotes on the submission look legit to me, as does the submission itself.
[1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
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.
edit: clarification, focus
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...
edit: That is, the footer is not within a visible area of the sidebar.
Its not that rare I think.
*small fintech with couple of billions in the accounts, not a startup, not a Fortune 500 company
I fail to understand why a ton of breathless blog posts about the process of AI-assisted coding are more interesting to HNers than some of the actual code (potentially, not claiming anything about it) written.
Maybe you or the GP could actually say what you think are "weird comments" and why you think this is being "boted"?
---------------
[1] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
[2] Why are people obsessed with star counts? I at least only star things to bookmark them, not vouch for them in any way. It does not seem unreasonable to me that 5 times as many people bookmarked the repo in the early days than are using it on npm. Also, npm is not necessary, the author shows at least 2 other ways to use it (direct download, link to GitHub pages) which will not show up in npm stats.
I think theres alot indian developers who are hacker news as well as on github and other forums.
> Use of semantic elements is an interesting take. I'll give it a try.
> Thank you for this, can’t wait to use. Minimalism at its best.
> Good one. Presentation is good too. Thanks
These are the kind of comments you see from Indians paid to boost Youtube content.
Following the first comment you quoted...
> I love it. We need to see more of this.
...shows that the author talks about using a “Chase card abroad” in a previous comment [1], which means they cannot be Indian as Chase doesn't issue cards or have substantial operations in India.
I don't want to run around following specific comment authors back through their threads, but as an Indian by birth it is pretty hurtful to see this kind of drive-by casual characterization of an population in a space like this. It also seems to be pretty contrary to the HN guidelines (“Please don't sneer, including at the rest of the community.”)
--------------