News for hackers. Stuff that matters.
Re:The Deno Company by not_knuth on Monday March 29, 2021 @08:16AM (#26620458)
If I understood correctly this is how they intend to make money:

> Not every use-case of server-side JavaScript needs to access the file system; our infrastructure makes it possible to compile out unnecessary bindings. This allows us to create custom runtimes for different applications: Electron-style GUIs, Cloudflare Worker-style Serverless Functions, embedded scripting for databases, etc.

So it's basically more of a Redhat approach to making money from open source? They intend to build tailored services on top of Deno for companies that request them?

Re:The Deno Company by sbarre on Monday March 29, 2021 @08:36AM (#26620617)
I'm not sure that they meant those specific runtimes would be premium products.

My read was that anyone could more easily configure a runtime to expose (or not expose) the underlying bindings that it requires, vs. just having them all in there by default.

I think "us" in that statement is the Deno community, not Deno the company.

But maybe I'm wrong.

Re:The Deno Company by not_knuth on Monday March 29, 2021 @09:19AM (#26621072)
Clicking around the website and reading more comments leads me to believe that this is the product they intend to monetize with:

https://deno.com/deploy

I still find it strange that there is no mention of it in the post...

Re:The Deno Company by sbarre on Monday March 29, 2021 @09:41AM (#26621367)
That makes sense...

So if you're up for it, you can still roll your own deployment infrastructure and tailor your builds as needed etc.. and support all of that internally.

Or you can pay Deno to handle it for you and you can focus on building your apps.

Re:The Deno Company by qbasic_forever on Monday March 29, 2021 @03:48PM (#26627269)
That's a description of a command line flag or feature of the runtime, not a business model.
Re:The Deno Company by denkquer on Monday March 29, 2021 @08:53AM (#26620798)
I recall Ryan regreting nodes full-permission approach. Not every script should be able to access the fs for securities sake.
Re:The Deno Company by Griffinsauce on Monday March 29, 2021 @09:44AM (#26621425)
Deno's permissions are per-process though, it's a big jump for sure, but also still leaves the door wide open for abuse by dependencies of any serious project.
Re:The Deno Company by e12e on Monday March 29, 2021 @04:34PM (#26627808)
It does allow for some coarse grained improvements for certain services, though.

You might write an smtp daemon that only delivers email on to another service via LMTP - thus without ability to write to (or read from, depending on configuration) the file system, for example.

Yes, you can accomplish this via containers, too - but it's nice to get as much out of process isolation as possible, not to mention it is likelier easier to test and debug the closer to the surface of the runtime limitations are implemented.

Re:The Deno Company by tannhaeuser on Monday March 29, 2021 @11:24AM (#26623123)
How is that different from Node.js which also runs in a single process? Or does Deno create per-request processes (or v8 "isolates" etc) like CGI does?
Re:The Deno Company by zastrowm on Monday March 29, 2021 @01:41PM (#26625445)
I think the point was that it's not different from Node.js - and thus not much of a benefit.

If it was more along the lines of "I want to use this array helper library, but it shouldn't have any permissions" then it would be a lot more useful, but right now if your Deno app needs any file or network access, then all of your dependencies get access too.

Re:The Deno Company by Griffinsauce on Monday April 12, 2021 @09:45AM (#26779327)
Yes, this was my point. It's only trivially better in practice since you'll have to open all the doors nearly all the time.

We have so many dependencies that really only need to work in-memory and have zero IO needs. That part is not solved in Deno at all.

Re:The Deno Company by why_Mr_Anderson on Monday March 29, 2021 @08:40AM (#26620670)
Javascript embedded scripting for databases .../shivers
Re:The Deno Company by sbarre on Monday March 29, 2021 @08:50AM (#26620766)
Why?

I think the point being made here is that it will be easier to create purpose-built runtimes that only provide needed bindings, making them more secure and possibly also more performant?

JS/TS as languages are here to stay, so let's give them the best possible ecosystem.

Re:The Deno Company by qbasic_forever on Monday March 29, 2021 @04:48PM (#26627975)
Stuff like CouchDB have been around for a decade now, it's fine. All of NPM still runs on it...