4 ms·

Deno 1.5

81 points by lucacasonato 6y ago

fractalf 6y ago
This looks amazing. First time hearing about it, can't believe this hasn't gotten more tracktion.
- dirtnugget 6y ago
  I guess the biggest complaint after it was released was the lack of a packet manager. Not sure if that situation changed. However there was quite some buzz around it, here as well.
  - randtrain34 6y ago
    I think not having a package manager was pretty intentional and unlikely to change. I personally like the new import from url functionality, especially when combined with the ability to alias some of those away.
    - dirtnugget 6y ago
      Sooo after a quick look through their packages it turns out there is one: https://deno.land/x/trex@v1.3.1 https://deno.land/x/trex@v1.3.1 Though I gotta agree that not having to have one is pretty sweet. Just wondering how that would scale and age.
      - raxor53 6y ago
        Ryan Dahl has talked about how he regrets making npm the default package manager for Node. I think its smart to have some explicit separation between framework and package manager.
      - kamranjon 6y ago
        That's a 3rd party package
    - JMTQp8lwXL 6y ago
      Something about downloading dependencies at runtime, rather than build time, seems less safe, but in either case, you still have to download them, so maybe not.
nailer 6y ago
I accidentally deployed my personal site on deno 1.3 when testing it on Architect Serverless (I use TypeScript in the front end and wanted to have a go at using TS on the backend via Architect's deno support - https://arc.codes/reference/arc-config/runtime https://arc.codes/reference/arc-config/runtime, then forgot to change the runtime back to node before deploying). Deno works really well. There's not much to think about if you know node. This new release has top level await too: > Top level await support: you can now just await promises in the REPL without having to wrap your call in an async IIFE.
- dirtnugget 6y ago
  accidentally?
  - nailer 6y ago
    See the 'forgot' bit above.
randtrain34 6y ago
I wish this gained adoption faster but unlikely that it'll surpass Node.js anytime soon...
- sieabahlpark 6y ago
  It's security promises are snake oil until you have per-module security. Otherwise every demo app will run at the same level as node in practice. Except you gave a worse ecosystem and less to rely on long-term.

Deno 1.5

81 points by lucacasonato 6y ago

fractalf 6y ago

This looks amazing. First time hearing about it, can't believe this hasn't gotten more tracktion.

dirtnugget 6y ago
I guess the biggest complaint after it was released was the lack of a packet manager. Not sure if that situation changed. However there was quite some buzz around it, here as well.
- randtrain34 6y ago
  I think not having a package manager was pretty intentional and unlikely to change. I personally like the new import from url functionality, especially when combined with the ability to alias some of those away.
  - dirtnugget 6y ago
    Sooo after a quick look through their packages it turns out there is one: https://deno.land/x/trex@v1.3.1 https://deno.land/x/trex@v1.3.1 Though I gotta agree that not having to have one is pretty sweet. Just wondering how that would scale and age.
    - raxor53 6y ago
      Ryan Dahl has talked about how he regrets making npm the default package manager for Node. I think its smart to have some explicit separation between framework and package manager.
    - kamranjon 6y ago
      That's a 3rd party package
  - JMTQp8lwXL 6y ago
    Something about downloading dependencies at runtime, rather than build time, seems less safe, but in either case, you still have to download them, so maybe not.

nailer 6y ago

I accidentally deployed my personal site on deno 1.3 when testing it on Architect Serverless (I use TypeScript in the front end and wanted to have a go at using TS on the backend via Architect's deno support - https://arc.codes/reference/arc-config/runtime https://arc.codes/reference/arc-config/runtime, then forgot to change the runtime back to node before deploying). Deno works really well. There's not much to think about if you know node. This new release has top level await too: > Top level await support: you can now just await promises in the REPL without having to wrap your call in an async IIFE.

dirtnugget 6y ago
accidentally?
- nailer 6y ago
  See the 'forgot' bit above.

randtrain34 6y ago

I wish this gained adoption faster but unlikely that it'll surpass Node.js anytime soon...

sieabahlpark 6y ago
It's security promises are snake oil until you have per-module security. Otherwise every demo app will run at the same level as node in practice. Except you gave a worse ecosystem and less to rely on long-term.