I can't imagine a wasm running inside nodejs being faster than native code that's been optimised for decades.
No PostgreSQL install needed—just Node.js
postgres is 32MB, nodejs is 63MB. I know that 31MB isn't a huge deal for most folks, but it's hard to see as "doesn't require postgres" as a selling point when you need something else that's twice the size instead.
This isn’t because of the size. Frankly, this is appealing because we already use both python and node package managers, so not needing to reach for another binary install mechanism is really appealing.
The same package manager that installs python should be able to install Postgres of pretty much any distro. I frankly don’t know of any exceptions to this.
Comments
I can't imagine a wasm running inside nodejs being faster than native code that's been optimised for decades.
postgres is 32MB, nodejs is 63MB. I know that 31MB isn't a huge deal for most folks, but it's hard to see as "doesn't require postgres" as a selling point when you need something else that's twice the size instead.
This isn’t because of the size. Frankly, this is appealing because we already use both python and node package managers, so not needing to reach for another binary install mechanism is really appealing.
The same package manager that installs python should be able to install Postgres of pretty much any distro. I frankly don’t know of any exceptions to this.
Haha yeah, I put a (I know) in the readme
Was just to have kind of SQLite dx in 1 hour thus did so.
And then I thought why not open source it?
Maybe in v2 I could abstract actual binary with same dx