News for hackers. Stuff that matters.
Re:Deno 1.33: Deno 2 is coming by frou_dh on Saturday April 29, 2023 @04:51AM (#35751258)
If you provide a compelling product offering, and the people understand what's available where, and choose to use it, then I guess that can be called vendor lock-in. But it's hardly nefarious.
Re:Deno 1.33: Deno 2 is coming by ohgodplsno on Saturday April 29, 2023 @05:08AM (#35751343)
It is nefarious when you build up your entire product for years, spamming it everywhere as "node but better", yell "it's so open source too!" on every roof, only to sneakily slide in lock-in features, it's worse than being nefarious. You most likely had this plan in mind all along, and actively lied to get there.

Watch as the same happens with Bun.

Re:Deno 1.33: Deno 2 is coming by frou_dh on Saturday April 29, 2023 @05:14AM (#35751372)
What's stopping you taking Deno CLI, using it for free forever, and completely ignoring anything related to Deno Deploy?

In this relationship of 3 years and counting, they are the positive contributors because they've given you something useful for free and you presumably haven't given them anything.

Re:Deno 1.33: Deno 2 is coming by iudqnolq on Saturday April 29, 2023 @06:21AM (#35751631)
In this specific case I think it's super reasonable.

The KV store has two backbends: local sqlite and distributed deno cloud.

If you choose the deno cloud backend you're signing up for a closed source cloud service from the start. There's no trickery.