31–40 of 60 posts
I poked around with this a few months ago to figure out how it works locally. The answer is SQLite: https://til.simonwillison.net/deno/deno-kv I'm finding the business model aspect of Deno KV absolutely fascinating. const kv = await Deno.openKv(); That's a Deno core API. It works fine in the open source version of Deno using a local SQLite database file. But as soon as you deploy your application to their proprietary…
I poked around with this a few months ago to figure out how it works locally. The answer is SQLite: https://til.simonwillison.net/deno/deno-kv I'm finding the business model aspect of Deno KV absolutely fascinating. const kv = await Deno.openKv(); That's a Deno core API. It works fine in the open source version of Deno using a local SQLite database file. But as soon as you deploy your application to their proprietary…
This is the enshittification of open source. It has been happening for a while with a bunch of startups like Supabase claiming to be "open source" and marketing themselves as such but making it really hard to self host for a long time. It wasn't just them either. I would see with disgust a bunch of startups use "open source" as their marketing tactic, no matter how hard it was to setup or run without their hosted ser…
I'm really confused by this statement. What exactly is being degraded in their service? Or in their API? Or in the underlying tech they are compatible with?
All I see here is an open source system that you can manage and deploy yourself, with a 100% compatible API for a cloud service that handles that for you, should you decide to pay money to have that problem solved for you.
I find your comment to be quite dramatic.
Earlier quoted context omitted.
One does not have to use/not use something to have valid criticisms of it/opinions about it [1] 1 - https://i.kym-cdn.com/entries/icons/original/000/036/647/Scr...
That meme doesn't further your point because the peasant is "using" society and understands the problems with it.
Earlier quoted context omitted.
That meme doesn't further your point because the peasant is "using" society and understands the problems with it.
My point with the meme link is that you can respond to any complaint about anything with a 'gotcha' argument that's ultimately invalid.
I poked around with this a few months ago to figure out how it works locally. The answer is SQLite: https://til.simonwillison.net/deno/deno-kv I'm finding the business model aspect of Deno KV absolutely fascinating. const kv = await Deno.openKv(); That's a Deno core API. It works fine in the open source version of Deno using a local SQLite database file. But as soon as you deploy your application to their proprietary…
Why does a KV store need SQLite? Does it provide transactionality?
By the time you've implemented even a basic key-value store with on-disk storage you've probably written a bunch of code that would be unnecessary if you had used SQLite.
Earlier quoted context omitted.
This is the enshittification of open source. It has been happening for a while with a bunch of startups like Supabase claiming to be "open source" and marketing themselves as such but making it really hard to self host for a long time. It wasn't just them either. I would see with disgust a bunch of startups use "open source" as their marketing tactic, no matter how hard it was to setup or run without their hosted ser…
Does this change your mind at all? https://github.com/denoland/deno/blob/be1fc754a14683bf640b7b... It looks to me like they've documented the KV Connect protocol they invented to support this feature, in enough detail that anyone else could build an alternative backend for it. This has helped me feel completely OK with how they're handling this. They get an advantage in that they've already built an extremely robust…
import KV from "https://deno.land/kv" // for example
Treating their hosted service as "part of the runtime" which is what the Deno global tends to be for is the only remaining ick factor for me.
I don't know enough about this to make any real nuanced comments, but I hope they clean up this import cuz this is ugly: > import { Semaphore } from " https://deno.land/x/semaphore@v1.1.2/semaphore.ts "; Should just be~ > import { Semaphore } from "deno/utils"; Or something like that.
What syntax would you suggest for importing a specific version of a library?
idk i just think there's many options besides a full url in your code
Earlier quoted context omitted.
Why does a KV store need SQLite? Does it provide transactionality?
What would you use instead? By the time you've implemented even a basic key-value store with on-disk storage you've probably written a bunch of code that would be unnecessary if you had used SQLite.
I worked on some of this - happy to answer questions :)