hoodie
cookies.js
Our great sponsors
hoodie | cookies.js | |
---|---|---|
1 | 1 | |
4,394 | 2,380 | |
0.2% | - | |
0.0 | 0.0 | |
about 2 months ago | almost 5 years ago | |
JavaScript | JavaScript | |
Apache License 2.0 | MIT 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.
hoodie
-
Frameworks of the Future?
I'm not looking for the overthrow of CRUD-through-MVC. Rather, Hobo and Hoodie seemed like advances---Hobo was sort of Rails for Rails, and Hoodie was an offline-first framework for something like what we now call Progressive Web Apps---when I tried them early in their life-cycle, but both seem to have withered away. And nobody else (that I can find) seems interested in improving graphical design (as in, "just use Material Design, or Carbon, or whatever"), cleaner parent/child relationships, automatically updating views and controllers to match changes to the models, and probably features that I don't know that I need.
cookies.js
-
DDD Is Overrated
Sure you might not be able to write 100% of the documentation in one go and then the code, but AFAIK that's neither the goal or the intention of DDD, it's more like "document a bit, write a bit, repeat".
The way I do it is first write a draft of the documentation, of how I want the API to look like. Then check if that basic code is possible (which I can predict most of the times based on experience), then write some more docs or methods. When writing a lib I normally already know where I want to use it, so I can put example snippets from how I want to use it as the documentation first and then try to implement those methods.
Examples of libraries I've written mostly this way:
- https://github.com/franciscop/brownies
- https://github.com/franciscop/files
- https://github.com/franciscop/backblaze
What are some alternatives?
PouchDB - :koala: - PouchDB is a pocket-sized database.
js-cookie - A simple, lightweight JavaScript API for handling browser cookies
jquery-cookie
Cookies - JavaScript Client-Side Cookie Manipulation Library
localForage - 💾 Offline storage, improved. Wraps IndexedDB, WebSQL, or localStorage using a simple but powerful API.
LokiJS - javascript embeddable / in-memory database
WatermelonDB - 🍉 Reactive & asynchronous database for powerful React and React Native apps ⚡️
secStore.js - Encryption enabled browser storage
lawnchair.js - A lightweight clientside JSON document store,
sql.js - A javascript library to run SQLite on the web.
basket.js - A script and resource loader for caching & loading files with localStorage