3 ms·
They’re operating like a startup, which like you say should be perfectly fine. Can’t pretend like a giant when you don’t have the bank account for that. Though
by qprofyeh 3y ago
They’re operating like a startup, which like you say should be perfectly fine. Can’t pretend like a giant when you don’t have the bank account for that.
Though they’re also selling a developer ecosystem. A lock-in. Are you willing to bet your company’s own software tools on a vendor that could go bankrupt from their other (hosting) business? The question is if Deno hosting dies, will Deno as a platform still thrive?
- vorticalbox 3y ago> The question is if Deno hosting dies, will Deno as a platform still thrive? that I am unsure about, a large part of the appeal at least for me is the deno deploy. URL imports are a bit of a hassle when you are trying to get them from say a private github repo.
- soulofmischief 3y agoDeno supports package.json now https://docs.deno.com/runtime/manual/node/package_json https://docs.deno.com/runtime/manual/node/package_json
- PoignardAzur 3y agoI think by now accusations of lock-in are a bit shaky. They're providing self-hosted alternatives for all the features of their ecosystem (and it's all open-source anyway).
- skybrian 3y agoI'm just writing hobbyist software, but I'm not too worried. My backup plan is to put my Deno app in a Docker file and deploy it somewhere. (It's a bit trickier than that since the SQLite database holding the KV store would need to be backed up, but it seems doable with Litestream?)
- tracker1 3y agoI don't think Deno itself is going anywhere if the startup fails, there's also self hosting. It's be tough, but going the other way to Node as a transition is entirely possible with relatively minor effort.