7guis-html-css-js
vanilla-todo
| 7guis-html-css-js | vanilla-todo | |
|---|---|---|
| 1 | 4 | |
| 49 | 1,123 | |
| - | - | |
| 0.0 | 8.4 | |
| about 1 year ago | 3 months ago | |
| JavaScript | JavaScript | |
| - | ISC License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
7guis-html-css-js
-
Show HN: 7GUIs in Vanilla HTML, CSS, JavaScript
And this is what you end up with, managing all possible state changes manually. I've done this myself with jQuery, show/hide, enable/disable elements. Turns into a game of Whac-A-Mole and full-time job for testers. No thank you.
https://github.com/bradwoods/7guis-html-css-js/blob/19279899...
vanilla-todo
-
What We Need Instead of "Web Components"
Thanks for this, gives my intuition some words to back it up!
I find especially compelling how the author separates concrete problems like reconciliation (hard to argue against) from the abstract principle of "everything should be a component" (can be argued more easily IMO).
Shamelessly plugging https://github.com/morris/vanilla-todo here; in this try-hard-to-stay-vanilla case study there are similar conclusions: Reconciliation is hard, CSS global namespace is problematic, etc. - I also did not use web components, but could not explain/justify that decision well (until now!).
- Vanilla-todo: A case study on viable techniques for vanilla web development
- GitHub - morris/vanilla-todo: A case study on viable techniques for vanilla web development.
-
Show HN: 7GUIs in Vanilla HTML, CSS, JavaScript
A few years back I stumbled into something a bit more complex, still done in pure js, just for the hell of it: https://github.com/morris/vanilla-todo
And then wrote my own version, with code a lot closer to modern react, with undo/redo and other niceties - https://github.com/ivank/vanilla-teuxdeux
And what I leaned is that is astonishingly easy to write code that would be understandable to people coming from the redux crowd. Maybe that’s because redux is just such a simple concept in and off itself - a glorified switch on a big object. And it’s also quite easy to hack a simple version of vdom to make it all work.
What’s missing from all those vanilla js efforts though turned out to be testability. There is a ton of code in the modern js world just to allow you to mock/test your components, and thats for me the real tragedy of vanilla js.
I have no idea why W3C crowd have not invested into standardizing js tests in all these years…
What are some alternatives?
petite-vue - 6kb subset of Vue optimized for progressive enhancement
7guis-React-TypeScript-MobX - Implementation of 7GUIs with React, TypeScript and MobX
vanilla-teuxdeux - A case study to implement modern js app with vanilla web technologies
mvc_for_the_web - Example programs explaining the techniques of Model-View-Controller implemented as web applications.
SlickGrid - A lightning fast JavaScript grid/spreadsheet
Dragula - :ok_hand: Drag and drop so simple it hurts
RxJS - A reactive programming library for JavaScript