I'm currently working on a small application that will replace an existing excel sheet. I want to make it accessible over the internet and add some extra things like exporting and automatic e-mails of reminders.
My first response as someone whos a fan of using ScarletDME and the Pick way of thinking was to try and use Pick. I don't care for the usual excuses that it won't be maintainable by others or that it's a dead language. Everyone can learn Pick and it isn't difficult to get started with, especially if you write code in a way where you think about the future programmer.
What stopped me from using ScarletDME specifically though was that there was no javascript library. I wanted to use Sveltekit and I wanted to use the Carbon Design System. These are things I'm already comfortable with and so what I wanted was not a database environment but just the database. Instead of using sqlite and the package better-sqlite3, I wanted to use scarletdme and some non-existent node wrapper library.
I had made one for UniVerse and if UniVerse didn't have a license fee I would have probably used it. It does however have a license fee and so it wasn't on the table.
I could go out and probably make something that could work well enough but the application was small and it wasn't something I wanted to put off. I wanted to actually make the application and so I reached for sqlite.
This post exists more as a reasoning and hopefully a jumping off point. I think having some sort of native javascript interop is important in the grand scheme of things. Javascript has won in how prevalent it is and it is the best way to expose people to Pick. Once exposed, maybe then they would also enjoy the pick environment.