Hacker News Reader

I do not question if it is high-level as much as I do its practicality. jQuery manipulates the DOM, React manipulates a virtual DOM pushing the changes to the client. That's about as vanilla as it gets.

Could you be a little more descriptive? If you're talking about creating a more visually appealing UI/UX experience, are you talking about creating a framework that more effectively handles UI component state?

Maybe I'm missing something and am way off base.

View on HN

Great question. So sorry for the confusion- I only used jQuery UI as an example, but perhaps it wasn't the best one. I'm trying to create a UI component library in vanilla JS/CSS that can be extended for use in React.

So I'm looking to create something very similar to Material Design, a vanilla JS/CSS library (https://material.io/components/web/), which is extended and used in Material UI, a React component library (http://www.material-ui.com/).

I guess I'm essentially asking: if I were to build Material Design, knowing full well I'd use it later to create something like Material UI, are there any recommendations out there for building the vanilla lib to make sure I don't shoot myself in the foot integrating that vanilla lib into the React lib?

Reply on news.ycombinator.com