When I did a prototype with deno, I was interested in testing with SQLite. Wanting more performance, I went to enable WAL, only to discover it's not supported. To make it worse, I couldn't get the version from npm to work either.
I like the ideas and simplicity of deno, but my opinion after only spending a few days with it, is that it tries to replace everything, but for each of those things, it only recreates 80% of the functionality.
I also think being backwards compatible with npm is a blessing and curse. A blessing because it can onboard more users, but a curse because those users have no incentive to switch now, since cross compatibility would also allow them to switch later.
Not that this helps retroactively, but the proper SQLite that's in fact already inside the Deno binary (rusqlite) will soon be usable from JS/TS when https://github.com/denoland/deno/pull/27308 is landed, as opposed to the several somewhat hacky third-party FFI/Wasm packages, one of which you presumably tried.
4 comments
[ 3.5 ms ] story [ 24.6 ms ] threadI like the ideas and simplicity of deno, but my opinion after only spending a few days with it, is that it tries to replace everything, but for each of those things, it only recreates 80% of the functionality.
I also think being backwards compatible with npm is a blessing and curse. A blessing because it can onboard more users, but a curse because those users have no incentive to switch now, since cross compatibility would also allow them to switch later.