Echo JS 0.11.0

<~>
tracker1 2 days ago. link 1 point
Interesting... I might take a look once you have PostgreSQL and/or SQLite support working in the box.  Would suggest looking at some of the database extensions that are used with VS Code for refinement and inspiration... the MS-SQL extension is one of the better ones, you can run in docker pretty easily for the server instance, though on arm mac, you'll need Rosetta2 configured with Docker.

I would also suggest using the Rust side to handle at least the main portions of theming as much as possible... Windows, Mac, Linux (Gnome/GTK or KDE/Qt theme detection) to establish a baseline light/dark and appropriate accent/highlight color for buttons, etc.  This is an area were you can go a long way with just a minor amount of time ensuring appropriate fonts/colors for the environment by default.  Much easier with Rust than Electron even.

On the AI front, Not sure if it would be worth trying to train a relatively limited cpu-based model, given a populated database/schema table(s) constructed to a more common format... the variance will really come down to db specific characteristics...  MySQL/Maria's back-tick usage vs pg's case handling and ansi-quotes and MS-SQL's square brackets.  They all also have different schema interrogation to get the schema structure as well as varying behaviors.  SQLite in particular is both better and worse than MySQL in some ways depending on your schema definitions vs usage.

Other than the variance, the SQL language itself is really pretty succinct and limited enough that you should be able to minimize the need for more expensive interactions for most usage.

Adjacent would suggest supporting a migrations project structure, similar to say grate or similar tooling in order to facilitate db "projects" associated against a db instance.  Not to be MS centric, I just find the tooling around MS-SQL and Grate to be relatively nice to work with compared to others.  My DB preference is PostgreSQL though.

Replies