Deno 1.14

Post by [deleted] » Thu, Sep 16, 2021, 9:42 PM UTC

gavinray wrote: post #61

eins1234 wrote: post #57

One of the most exciting opportunities IMO that Deno opens up, compared to most traditional server-side frameworks, is the possibility for simple url-based live-reload workflows in production. I'd love to be able to develop backend services by pushing source code to some url as I develop, and then have the production instances of the service notified of the changes and reload themselves immediately for a super-tight…

This is a really old concept with interpreted languages, Capistrano in Ruby came out in 2006 for this sort of workflow: https://en.wikipedia.org/wiki/Capistrano_(software) 10 year old gist for this exact thing: https://gist.github.com/rchampourlier/1281506/a22148264c457ebb69259261f117548569be6bef Same exists in Node, using PM2 process monitor via rsync/ssh: https://pm2.keymetrics.io/docs/usage/deployment/ Run a comma…

Post by oauea » Thu, Sep 16, 2021, 10:09 PM UTC

dgb23 wrote: post #43

oauea wrote: post #35

Earlier quoted context omitted.

Who doesn't love being removed even further from the platform they're running on?

One of Deno's value props is to have a tighter and more explicit trust model. And this is not a obscure need. There are cloud providers who let you run JS on a specialized and restricted API. However, there is nothing stopping you from using Node or integrating V8 and go wild with it! (In fact I would argue that this is a solid strategy for some types of projects, where you can get the best of both (static/dynamic) w…

Post by galaxyLogic » Fri, Sep 17, 2021, 12:09 AM UTC

aikah wrote: post #14

Love Deno and using it as a node replacement. Fantastic work. I encourage anybody who has npm packages to move everything to deno.

Post by galaxyLogic » Fri, Sep 17, 2021, 12:21 AM UTC

WorldMaker wrote: post #45

qsort wrote: post #2

Only tangentially related, but what's the point of a static class block? What problem does it solve that's not covered by either the class constructor or a static const? Doesn't it introduce a weird (stateful!) computation that's hard to reason about? There's probably a use-case I'm missing, because intuitively I'd automatically classify it as bad a practice.

Another perspective on static blocks is what they replace/help migrate away from. Static blocks are one of the last pieces of the puzzle holding some projects (or at least some particularly old legacy objects in those projects) from migrating to the new class syntax. For better or worse the classic Constructor Function pattern of building objects in JS was full of static initialization code (as it was an easy thing t…

   module.exports =  
   class MyClass
   { // ...

     static init ()
     { // ... do something, like create and 
       // cache a Singleton etc. 
       return this;
     }
   } . init();

Post by kbenson » Fri, Sep 17, 2021, 2:00 AM UTC

galaxyLogic wrote: post #94

kbenson wrote: post #34

Earlier quoted context omitted.

I also tried it out recently, because I wanted to make a small utility for myself and liked the idea of it providing a single executable (and bypassing the node/NPM ecosystem for learning a JS/TS based system appealed to me). It delivered on that beautifully, as all I did is switch from running "deno run" as I was for testing to "deno compile" and it delivered to me exactly what I was looking for. A bit large at 57 M…

Does the fact that you didn't need Npm mean that Deno has a suffciently large built-in library that a thing like Npm is in most cases not needed?