41–49 of 49 posts
Deno is such a nice little scripting tool. I've been using it for devops glue and scripts lately. Native typescript, easy-as-pie dependency management. its great!
Personally I do not like the fact that it puts too much trust into DNS. DNS wasn't created with security in mind, so to say Deno is secure because it uses a permissions system while relying directly into DNS for imports to me sounds weird.
Earlier quoted context omitted.
It always did. That’s been a core feature / benefit from day 1.
so question - normally the thing I like about Node.js is not much context switching and ability to rerun code between backend and frontend. I can get the same thing with TS if I compile in both backend and frontend - if in Deno I don't compile and in the frontend I do are there any weird gotchas I would run into?
Deno is such a nice little scripting tool. I've been using it for devops glue and scripts lately. Native typescript, easy-as-pie dependency management. its great!
Personally I do not like the fact that it puts too much trust into DNS. DNS wasn't created with security in mind, so to say Deno is secure because it uses a permissions system while relying directly into DNS for imports to me sounds weird.
Deno is such a nice little scripting tool. I've been using it for devops glue and scripts lately. Native typescript, easy-as-pie dependency management. its great!
This is such a neat demo. I wrote up an annotated version of the code while I was figuring out exactly how it worked. https://til.simonwillison.net/deno/annotated-deno-deploy-dem...
I expect the demo works with or without the await on the listen promise because the listen code runs regardless (and prevents main from exiting).
Earlier quoted context omitted.
It always did. That’s been a core feature / benefit from day 1.
No, it never did, Deno always have converted TypeScript into JavaScript that then gets read and executed by the browser, at least according to their own docs but maybe that has changed lately? > At a high level, Deno converts TypeScript (as well as TSX and JSX) into JavaScript. It does this via a combination of the TypeScript compiler, which we build into Deno, and a Rust library called swc. When the code has been ty…
>Deno can run JavaScript or TypeScript out of the box with no additional tools or config required.
- https://deno.land/manual@v1.15.3/examples/hello_world
>Deno is a runtime for JavaScript/TypeScript which tries to be web compatible and use modern features wherever possible.
- https://deno.land/manual@v1.15.3/getting_started/first_steps
You can run any of their examples to see that `deno run` commands can execute typescript without requiring a separate transpilation step
Earlier quoted context omitted.
No, it never did, Deno always have converted TypeScript into JavaScript that then gets read and executed by the browser, at least according to their own docs but maybe that has changed lately? > At a high level, Deno converts TypeScript (as well as TSX and JSX) into JavaScript. It does this via a combination of the TypeScript compiler, which we build into Deno, and a Rust library called swc. When the code has been ty…
My answer wasn’t explicit enough. To clarify, I meant as a user of deno you do not need to perform any separate transpilation or build step. The runtime can read and execute typescript natively (again, from user perspective). >Deno can run JavaScript or TypeScript out of the box with no additional tools or config required. - https://deno.land/manual@v1.15.3/examples/hello_world >Deno is a runtime for JavaScript/TypeS…
No hard feelings though, context is important and many of us miss it at times :)