10 ms·

Here you go: https://github.com/akrymski/espresso.js/tree/master/examples/todomvc https://github.com/akrymski/espresso.js/tree/master/examples...

• hombre_fatal 4y ago
  In HN fashion it was more of an open thought I had about the topic in general rather than a response to your library. But even reading code for projects like a todo app will show you how the code can be put together but necessarily higher level understanding. In other words, the kind of eurekas you think people should be able to glean from a real world example are great to establish in plain text. For example, imagine what you would write if you had a blog post that walks the user through how to build the todomvc. Another example is how I launched two macOS apps to the app store before I realized that the Combine api was supposed to be used and abused rather than a lower level api to be avoided in favor of other state management levers. And all it took was for someone with much more experience to simply tell me. I think it’s the hardest part of writing docs. And maybe you do it somewhere, I only read the api reference pages. The best example of this I can think of is mhartl’s Ruby in Rails tutorial. It has lots of wisdom about the “why” instead of just the “how”.