Hacker News Reader

Comment by colesantiago | Hacker News Reader

Is anyone using Deno at scale or in production yet?

Me and my friend use it in production for hobby projects. It works great so far with very few issues but you kind of have to keep up to date and the updates are coming really, really fast.

Thanks for the heads up, can’t quite understand why you’re getting downvoted. What kind of project are you using it on?

I didn't down vote but I'd imagine his down votes are because he said "using in production for hobby projects".

When people ask about production, they usually want stuff where money is at stake, or even better, someone's livelihood.

For me, "production" is the stable, tested version you ship that runs constantly. The one facing most users.

You can have hobby projects with users, and 24x7 uptimes being a goal. It makes sense to distinguish "dev" from "prod" with those and to use mechanized testing and CI/CD, just as with commercial projects.

A lot of open source projects fall into this category.

Who said we don't make money from our side projects?

"Hobby" implied that

I was being downvoted because of classic HN elitism which is getting worse every day.

Several web projects, I don't really want to link it here to out myself, but one is a podcast player.

fly.io is [0].

[0] https://news.ycombinator.com/item?id=22621926

I don't think Deno supports SSL yet.

Deno not supporting TLS isn't a show stopper, in my opinion. Not many production environments expose Deno (or Node) instances directly, but rather have a reverse proxy sitting in front providing SSL and routing.

It’s totally a breeze to get https set up with Caddy.

Better leave that to a terminator/proxy anyway unless you’re interested in hotpatching your app layer every month. It’s usually less problematic to upgrade a proxy.

The ticket for TLS support was closed in December (https://github.com/denoland/deno/issues/1568) and there seems to be a lot of TLS support including esoteric use cases now.

TLS is supported but poorly documented. I got something working after scouring Github issues and Stack Overflow. HTTP/2 is not yet supported.

Good, use webservers that get property audited.

My rule of thumb is to use TLS everywhere for everything unless I have a proper reason for not using it (i.e. strong performance hit).

mTLS in a Kubernetes cluster with Istio was a killer feature for us.

Is there any demand for that? I mean in 2020 you are one docker command away from having an automatically refreshing tls server ready and serving.

A lot of people are moving as many security features as possible out of the application and into the infrastructure.

Reply on news.ycombinator.com