4 ms·

Is anybody using Deno at work? I feel like there was this rush of excitement when it first came out, and that's mellowed to a steady stream of updates and some

Is anybody using Deno at work? I feel like there was this rush of excitement when it first came out, and that's mellowed to a steady stream of updates and some sustained low-medium interest. It seems like everybody's following it from the sidelines, waiting to see what happens. That's my situation at least. I'd love a world where I can write everything in TypeScript with minimal building hassle, but I'm curious to what degree that's panning out in industry.

zachlatta 5y ago
We're using Deno for some small projects at Hack Club. We open source everything. Code for them should be somewhere in https://github.com/hackclub/hackclub https://github.com/hackclub/hackclub. In particular, we've been using it to replace some bash and Ruby scripts we had.
nullspace 5y ago
We are, in a limited fashion. Can't give too much details (mostly because I'm not directly working on it), but the ability to run in a constrained sandbox and the ability to easily do go style imports from github is seriously useful for our use case. Don't know how it's going to pan out, but from a high level deno seems to be very well designed. I'm looking forward to see the various niches in which people use it.
tupac_speedrap 5y ago
Not that I know of. TypeScript has had some major adoption over vanilla JavaScript over the past few years, I used it a bit when it was relatively new and now it is pretty common to see it advertised on job specs but I have never seen Deno once, maybe they use it in "ployglot" shops where everybody uses more esoteric languages but I haven't seen it advertised anywhere.
eyelidlessness 5y ago
I know at least one person on the Snowpack/Astro team has expressed[1] interest in dual Node/Deno support. I’m not currently advocating for supporting Deno on my professional projects. But this isn’t for lack of interest, it’s just lower priority than other changes I want to make first. I absolutely want to switch when I can justify it, if for no other reason than fast TypeScript ESM without a build/transformation step. 1: https://twitter.com/n_moore/status/1423672410486755332?s=21 https://twitter.com/n_moore/status/1423672410486755332?s=21 Edit: forgot link
gutino 5y ago
Yes we are building an API of serverless services
mrkurt 5y ago
We have a customer running about 300 million requests per day through a Deno app to generate image variants.
- Madeindjs 5y ago
  Why did you choose Demo over Node.js? Is this making performances improvements?
  - mrkurt 5y ago
    Much faster builds, easier to write code for, etc. It's probably similar performance to Node, all the heavy lifting is done outside v8 (just like it would be in Node). The JS environment is largely just accepting HTTP requests, doing a bunch of logic, handing off instructions to lower level image manipulation libraries, and then streaming the response back to users.
maga 5y ago
I'm using Deno for developing my isomorphic libraries (e.g. structurae[1]). It comes with a built-in toolchain (formatter, linter, test runner, compiler) that significantly reduces headache when compared to jangling prettier, eslint, jest, and tsc. [1] https://github.com/zandaqo/structurae https://github.com/zandaqo/structurae
rektide 5y ago
I find doubt/skepticism like this unimportant & irrelevant. I am far more interested in a Tim Orielly style "Follow the Alpha Geeks" mentality, of mining the scene for what is interesting & empowering & novel, understanding contributions & possibilities. Deno brings two main things that seem undeniably critical & without peer: 1. Fantastic rust integration. Node has neon & napi-rs, but neither of these present as rust-first & readily available extension point, to replicate what node did: be the incredibly super successful bridge between the native platform & the javascript language. Whatever success Rust has will strengthen & alloy Deno's position. 2. Unparalleled web platform support. Always bet on the web. The web is everywhere, it's platform is excellent & healthy & robust, some last cracks of missing capabilities are being filled in. Deno presents as a possible server-side desktop-side web environment in a way nothing else does. Whatever success the web has will strengthen & alloy Deno's position. Fretting about where in the adoption curve something is is uninteresting to me, a geek. I would rather focus on the thing, know it, assess it's potential, see others assessments, & make my own projections of usability & adoption, than look about for signs. Hopefully the brilliant things will have their due day.
- brundolf 5y ago
  I'm not fretting or skepticizing, I'm just trying to get a pulse on where things are and where they're going. Adoption isn't irrelevant, because it determines things like ecosystem maturity, long-term support, etc. I wouldn't feel comfortable recommending that my company build a critical new system on a technology until I feel confident that it has a future. So I'm just trying to get a read on where we are with that when it comes to Deno.
- deleted 5y ago
  [deleted]
j-pb 5y ago
Yes. We also don't use it with typescript (and would actively advocate for its removal from deno when asked), best JS runtime I've ever used.
- keb_ 5y ago
  Question from someone who rarely uses TypeScript: why don't you use TypeScript and why do you advocate for its removal?
  - runawaybottle 5y ago
    I can tell you why I don’t like it. Everyone’s subtle OCD seems to come out with Typescript. Instead of cutting down on the number of function arguments, people don’t give a shit. They add more and more args, and maniacally define the types for every little thing. It’s like some odd version of list-making (many people get a kick out of compulsively making these detailed lists). It used to be that you think very carefully about how to keep a function simple, but Typescript is bringing out this dark side in people that allows them to just define 15 argument functions, so long as is has a nice exhaustive Type. Sometimes you have to save people from themselves. I’ll stay hyperbolic and say in several years time, we will all be drowning in type-inflated code bases. JavaScript people always find a way to make things hard.
    - mikevm 5y ago
      Somehow people have been programming just fine in statically typed languages for decades without turning their code into a shitshow. It just appears that JS attracts a lot of poor programmers due to the low barrier to entry.
      - holoduke 5y ago
        Poor programmers everywhere. Java, C++, PHP, JavaScript. I have seen them all. Like C in JavaScript is so flexible that it is hard to enforce certain (company) standards. That makes it a bit more prone to issues. But many great examples of good plain js programs

zachlatta 5y ago

We're using Deno for some small projects at Hack Club. We open source everything. Code for them should be somewhere in https://github.com/hackclub/hackclub https://github.com/hackclub/hackclub. In particular, we've been using it to replace some bash and Ruby scripts we had.

nullspace 5y ago

We are, in a limited fashion. Can't give too much details (mostly because I'm not directly working on it), but the ability to run in a constrained sandbox and the ability to easily do go style imports from github is seriously useful for our use case. Don't know how it's going to pan out, but from a high level deno seems to be very well designed. I'm looking forward to see the various niches in which people use it.

tupac_speedrap 5y ago

Not that I know of. TypeScript has had some major adoption over vanilla JavaScript over the past few years, I used it a bit when it was relatively new and now it is pretty common to see it advertised on job specs but I have never seen Deno once, maybe they use it in "ployglot" shops where everybody uses more esoteric languages but I haven't seen it advertised anywhere.

eyelidlessness 5y ago

I know at least one person on the Snowpack/Astro team has expressed[1] interest in dual Node/Deno support. I’m not currently advocating for supporting Deno on my professional projects. But this isn’t for lack of interest, it’s just lower priority than other changes I want to make first. I absolutely want to switch when I can justify it, if for no other reason than fast TypeScript ESM without a build/transformation step. 1: https://twitter.com/n_moore/status/1423672410486755332?s=21 https://twitter.com/n_moore/status/1423672410486755332?s=21 Edit: forgot link

gutino 5y ago

Yes we are building an API of serverless services

mrkurt 5y ago

We have a customer running about 300 million requests per day through a Deno app to generate image variants.

Madeindjs 5y ago
Why did you choose Demo over Node.js? Is this making performances improvements?
- mrkurt 5y ago
  Much faster builds, easier to write code for, etc. It's probably similar performance to Node, all the heavy lifting is done outside v8 (just like it would be in Node). The JS environment is largely just accepting HTTP requests, doing a bunch of logic, handing off instructions to lower level image manipulation libraries, and then streaming the response back to users.

maga 5y ago

I'm using Deno for developing my isomorphic libraries (e.g. structurae[1]). It comes with a built-in toolchain (formatter, linter, test runner, compiler) that significantly reduces headache when compared to jangling prettier, eslint, jest, and tsc. [1] https://github.com/zandaqo/structurae https://github.com/zandaqo/structurae

rektide 5y ago

I find doubt/skepticism like this unimportant & irrelevant. I am far more interested in a Tim Orielly style "Follow the Alpha Geeks" mentality, of mining the scene for what is interesting & empowering & novel, understanding contributions & possibilities. Deno brings two main things that seem undeniably critical & without peer: 1. Fantastic rust integration. Node has neon & napi-rs, but neither of these present as rust-first & readily available extension point, to replicate what node did: be the incredibly super successful bridge between the native platform & the javascript language. Whatever success Rust has will strengthen & alloy Deno's position. 2. Unparalleled web platform support. Always bet on the web. The web is everywhere, it's platform is excellent & healthy & robust, some last cracks of missing capabilities are being filled in. Deno presents as a possible server-side desktop-side web environment in a way nothing else does. Whatever success the web has will strengthen & alloy Deno's position. Fretting about where in the adoption curve something is is uninteresting to me, a geek. I would rather focus on the thing, know it, assess it's potential, see others assessments, & make my own projections of usability & adoption, than look about for signs. Hopefully the brilliant things will have their due day.

brundolf 5y ago
I'm not fretting or skepticizing, I'm just trying to get a pulse on where things are and where they're going. Adoption isn't irrelevant, because it determines things like ecosystem maturity, long-term support, etc. I wouldn't feel comfortable recommending that my company build a critical new system on a technology until I feel confident that it has a future. So I'm just trying to get a read on where we are with that when it comes to Deno.
deleted 5y ago
[deleted]

j-pb 5y ago

Yes. We also don't use it with typescript (and would actively advocate for its removal from deno when asked), best JS runtime I've ever used.

keb_ 5y ago
Question from someone who rarely uses TypeScript: why don't you use TypeScript and why do you advocate for its removal?
- runawaybottle 5y ago
  I can tell you why I don’t like it. Everyone’s subtle OCD seems to come out with Typescript. Instead of cutting down on the number of function arguments, people don’t give a shit. They add more and more args, and maniacally define the types for every little thing. It’s like some odd version of list-making (many people get a kick out of compulsively making these detailed lists). It used to be that you think very carefully about how to keep a function simple, but Typescript is bringing out this dark side in people that allows them to just define 15 argument functions, so long as is has a nice exhaustive Type. Sometimes you have to save people from themselves. I’ll stay hyperbolic and say in several years time, we will all be drowning in type-inflated code bases. JavaScript people always find a way to make things hard.
  - mikevm 5y ago
    Somehow people have been programming just fine in statically typed languages for decades without turning their code into a shitshow. It just appears that JS attracts a lot of poor programmers due to the low barrier to entry.
    - holoduke 5y ago
      Poor programmers everywhere. Java, C++, PHP, JavaScript. I have seen them all. Like C in JavaScript is so flexible that it is hard to enforce certain (company) standards. That makes it a bit more prone to issues. But many great examples of good plain js programs