211–220 of 598 posts
Earlier quoted context omitted.
Sometimes it's ok to think "this project isn't for me" and just leave it be. The cynical-security-concern act is boring.
Security is literally the main selling point of this thing. Otherwise just use node.
Earlier quoted context omitted.
Ah, in this case, I would then have to commit my dependencies into my VCS to maintain reproducible builds. I'm not sure I like that solution very much either. I've seen node_modules in multiple GBs, and I'm sure Deno's dependency sizes are going to be similar.
True, but that's what people using Go have been doing for years without complaining much, so I guess it works fine for most workload. And before npm fixed things after the left-pad incident, the npm builds where not reproducible either (as demonstrated by the said left-pad incident).
Under-mentioned feature. I may migrate my personal site to Deno just for that latency drop.
Earlier quoted context omitted.
PM on part of Cloudflare Workers and someone who was in physical attendance for this talk here. They're not really directly comparable other than "A JavaScript runtime built on top of V8." Workers doesn't support TS directly, though you can compile TS to JS and run it, of course. (My team maintains a worker and this is what we do, and it works well) Deno has its own APIs, as does Workers. Worker's main API is the Ser…
> Workers is focused on V8 isolates as a means of achieving multi-tenency. I don’t believe Deno does anything specific here. Deno implements the web worker API, which launches different isolates. You could implement something kind of like CF Workers in pure TypeScript, but probably not replicate your resource enforcement. It's also a pretty good Rust v8 implementation. Before we (fly.io) abandoned our JS runtime we w…
Ah interesting! Did you abandon it for reasons other than “deno exists”? Would love to hear more about how it turned out, good or bad.
Earlier quoted context omitted.
In practice modules will be available from sources that will have similar reliability to npm: github.com, unpkg.com, cdn.pika.dev, jspm.io, etc.
it's better because there will be more choice.
How is that not "decentralisation"
And if you are importing single files from a remote url, I would question your sanity.
Earlier quoted context omitted.
Lua also has a smaller footprint I think.
It has a worse standard library than Javascript. And its static typing solutions don't compare to Typescript.
Earlier quoted context omitted.
> Workers is focused on V8 isolates as a means of achieving multi-tenency. I don’t believe Deno does anything specific here. Deno implements the web worker API, which launches different isolates. You could implement something kind of like CF Workers in pure TypeScript, but probably not replicate your resource enforcement. It's also a pretty good Rust v8 implementation. Before we (fly.io) abandoned our JS runtime we w…
Thanks for confirming, that’s what I meant by “specific”, I was guessing they implemented the spec. It’s just a very big focus of Workers, and I don’t think it’s a focus of Deno. Not good or bad, just a difference. Ah interesting! Did you abandon it for reasons other than “deno exists”? Would love to hear more about how it turned out, good or bad.
Deno’s existence gives me hope we can bring back the JS API, I'd love to have nginx-as-a-TypeScript-API.
I think Deno is a mistake at this point... Yes we thank Ryan Dahl for his huge contributions to integrating libuv and v8 outside of a browser to create node.js but a lot of work has been created by a huge ecosystem of developers after this. I think this de-facto fork of node.js will only serve to create fragmentation, and confuse product owners about which platform to use.
If We were all follow your rationale, We will be all programing in COBOL still. Accept the pain of experiment and growing up.
> error[E0433]: failed to resolve: use of undeclared type or module `proc_macro` --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/swc_ecma_visit_macros-0.1.0/src/lib.rs:25:20 | 25 | pub fn define(tts: proc_macro::TokenStream) -> proc_macro::TokenStream { | ^^^^^^^^^^ use of undeclared type or module `proc_macro`
error[E0433]: failed to resolve: use of undeclared type or module `proc_macro` --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/swc_ecma_visit_macros-0.1.0/src/lib.rs:25:48 | 25 | pub fn define(tts: proc_macro::TokenStream) -> proc_macro::TokenStream { | ^^^^^^^^^^ use of undeclared type or module `proc_macro`
error: aborting due to 2 previous errors
For more information about this error, try `rustc --explain E0433`. error: could not compile `swc_ecma_visit_macros`. warning: build failed, waiting for other jobs to finish... error: failed to compile `deno v1.0.0`, intermediate artifacts can be found at `/tmp/cargo-installFIkSV2`
Caused by: build failed