1. It is possible to create different types of items: books, ideas, projects, tasks, etc.

2. Every item can have its own custom fields, such as author for a book or priority for a task.

3. All items are stored in a single SQLite table, so you can search through all items and edit them if necessary.

4. Fourth, it is possible to establish relations between items: parent, child, or simple link.

5. There is a space called "Quickbox" where you can quickly register a link or a note to read later and transform it into an item.

6. Items can be part of one or more notebooks, such as Personal, Work, or Family.

I have many ideas to make it more useful, but some basic features are still missing, such as:

1. Attach images or documents to each item and access all the attachments as a separate library.

2. Multi-user support

3. Multilingual support

4. Kanban support for tasks.

The most interesting part for me is adding systems/structures that can help me analyze problems and find proper solutions.

This idea is still vague, but I'd like to implement workflows that can help me become a better thinker, improve my creativity, and enhance my ability to make rational decisions. I'd like to integrate also logic programming in the process, probabily using Prolog.

I don't want to lose the manual aspect of thinking, so I'm considering creating prefilled documents to help study problems and find solutions.

I have used Golang and SQlite on backend and PWA and HTMX on frontend.

1. you have no control over the generated SQL and because it has to be generic and db agnostic, might not be the best option depending on the database you are currently using

2. when something doesn't work as expected, and it happens, they are difficult to debug (too many layers) and find the issue

3. they are extremely inefficient, because they have to dynamically build every time the code is run the corresponding SQL code : I'm sure most would implement some caching mechanism to prevent this , but in any case it's a waste of resources.

This is just anecdotal, but I remember trying SQLAlchemy many years ago for a small Python program I was writing for a RaspberryPi 3 : it was extremely slow. So, I removed the library and used instead the native database binding for MariaDB instead, and the speed improved a lot.

For PHP, the situation is the worst because there is no application server (they exist, but not very widely used), but the code is regenerated every time. This is the main problem in any large PHP project, such as Nextcloud. If they would adopt FrankenPHP or RoadRunner, they could improve the performance of the applications a lot.