-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improved Sections #10
Comments
1. Avoid "&"I'll push back on adding "&" to categories, wherever possible. As with user stories, systems thinking, and knowledge management, lumping classes of information with "and" leads to sloppy categories:
2. APIsI'm not sure this is enough to justify its own category (the only rows I see are Java, HTTP, and remote client). It also doesn't feel like a category that would grow over time as people add features to their Datalog dbs. Unless perhaps we included client libs and drivers in here and people started building up non-Clojure front ends to APIs? Then I buy it. 3. Where did "Transactions" go?This is the second-largest category, behind Query. The category was intentional and I wouldn't roll its contents into any of the proposed 4 above. As a db user, I would want to know how I insert data into the database and how transactions are handled, separate from all these other topics. There are also a lot of weird transaction semantics to Datalog dbs that users coming from an RDBMS background will appreciate having collocated in one place, I think. ("Just what the heck is a composite tuple or a transaction function, anyway?") 4. ConsolesI don't think the consoles go under "Administration," (or the proposed "Operations 5. Repeated section headings
Makes sense. SummaryMaybe it would be better to make these changes piecemeal, rather than sweeping changes through a new PR? It would also be nice if they were driven by the community, rather than by us, since that was the entire goal of reorganizing the rows into collocated categories. |
Currently (since dabebc3) the sections are:
However, there are a few categorization anomalies, like including the clj/s runtimes under "Developer Experience", or having the consoles not under "Administration".
I propose:
If those don't seem obviously problematic (looking for feedback @deobald 🙂), I will draft a PR with the full set of changes.
Also, given the section headings, the column headings should probably be repeated each time to avoid forcing people to keep track of which column is which.
The text was updated successfully, but these errors were encountered: