No post body was provided.
Deno.js in production
81–90 of 100 posts
Re: Deno.js in production
#82Earlier quoted context omitted.
On one hand, JavaScript being easy makes programming accessible. On the other hand, the state of programming is terrible and getting worse. So you can't say if it's bad or not.
It’s not getting worse. Go ahead and make a relatively complex app with jQuery 2.0 and let me know how it compares to spinning up a Next.js app.
Or better yet, you could use neither! If it helps you remember, JavaScript is bad, so more JavaScript is more bad.
Re: Deno.js in production
#83I haven't had the same success with Deno that I expected. At first, I was shocked by how good the tooling is, and I was super happy with its dependency management. All of the problems started once I started getting into actual business logic. `redis` and `ioredis` `npm` packages don't work with Deno, even with the Node compat layer (I tried). So you have to use the Deno driver for Redis. But you look up the library f…
My experience was very similar. I was excited to start working on a personal project in Deno and found trying to use npm and import maps to be so painful, it left me wondering how I hadn't heard of these problems before (or since, really).
Re: Deno.js in production
#84I haven't had the same success with Deno that I expected. At first, I was shocked by how good the tooling is, and I was super happy with its dependency management. All of the problems started once I started getting into actual business logic. `redis` and `ioredis` `npm` packages don't work with Deno, even with the Node compat layer (I tried). So you have to use the Deno driver for Redis. But you look up the library f…
> `redis` and `ioredis` `npm` packages don't work with Deno, even with the Node compat layer (I tried). I'd love to hear specifically what didn't work and how close the Deno team is to maybe fixing those sorts of issues. Not that they owe that to us open-source wise, just curious as like... otherwise you are right. We're starting the ecosystem again over from scratch.
redis clearTimeout shim does not work correctly, console gets blasted with timeout messages nonstop because `on('error')` from the EventEmitter keeps getting triggered, even though the client is connected just fine.
ioredis commands hang randomly. I couldn't do GETs or SETs.
Re: Deno.js in production
#85I haven't had the same success with Deno that I expected. At first, I was shocked by how good the tooling is, and I was super happy with its dependency management. All of the problems started once I started getting into actual business logic. `redis` and `ioredis` `npm` packages don't work with Deno, even with the Node compat layer (I tried). So you have to use the Deno driver for Redis. But you look up the library f…
I think the ecosystem just needs to be filled out
I'm hoping Deno is such a dramatic improvement on the foundation vs Node that it's enough to convince library authors to jump over; the jury's still out on whether that flywheel will get started
Re: Deno.js in production
#86The title is very misleading. Deno is not written in JavaScript and is never referred to as Deno.js in any official sources. Deno is written in Rust.
Node isn't written in JS either, but people call it Node.js. They used the wrong name, but it's a pretty huge leap to call it "misleading".
Re: Deno.js in production
#87I've been using Deno for a large compiler project I've been working on over the last couple years, and for the most part it's been a dream
Of course that's not the most representative example, because a compiler can almost entirely dodge the ecosystem problem, but I thought I'd offer it anyway
Re: Deno.js in production
#88The security model is a big one for me. If they could extend the permissions system to work for individual dependencies, they could solve one of the biggest security issues facing developers right now. Especially if policies could also be applied to node packages. Are there any plans to move in this direction? It seems like if you can do it for the full app, you should hypothetically have the capability to make it li…
Checkout node policies as well: https://nodejs.org/dist/latest/docs/api/policy.html
Re: Deno.js in production
#89I hoped this article would provide more info than it actually did. For me, a javascript developer that mainly use Node.js for work, Deno is interesting and I want to use it but the hosting part is what prohibits me from using it. In node it's easy to run production code with pm2, you can cluster it and it's super easy to configure it so that it will run one node process per available core. With Deno, you can't do thi…
You can totally use pm2 with Deno! Just needs an extra flag.
pm2 start index.ts --interpreter="deno" --interpreter-args="run --allow-net --allow-write"
Re: Deno.js in production
#90node.js nowadays is a total disaster. I've been able to hold down the fort with turbo repo, but even then it's been a touchy strategy. I want to switch to Deno, and I'm interested in articles like this. Either that, or, because of the state of nodejs/NPM modules, and it's ever-increasing surface area of doom and resume driven development node modules, either somehow switch to deno or go back to just HTML and vanilla…
Node.js is a mature framework and never had problems with it. I also write my own code and avoid installing useless packages. Truth is everyone likes fresh projects like Deno but their ecosystem is doomed. I mean all I need is Redis and it doesn't work the way supposed to.