181–190 of 215 posts
Earlier quoted context omitted.
How are you using Deno with minified code? Do you mean importing a minified script like https://cdn.jsdelivr.net/npm/react/cjs/react.production.min.... ?
I meant bundling your code for production.
I love the idea of deno over Node. Is it getting traction though?
Earlier quoted context omitted.
Please purchase Deno the company before dismantling their only source of income through deno deploy--deno the tool is too nice to lose!
To be fair, CF workers is much older than Deno by a few years. I don’t see us as dismantling anything - do you blame the wind mill or Don Quixote for tilting at them? This is a very competitive space too. Cloudflare is but one player and I don’t think the ones who do well will focus just on the serverless infrastructure piece. It’s more about having a very complete product story that solves pain points better than an…
Can you explain more? Deno doesn't use typescript in the runtime. It is rust and pure js (for globals and wrapping bindings). I don't expect their current architecture to be any less efficient from what I know but it may have changed.
Earlier quoted context omitted.
No. It failed because JVC saturated the market with incompatible and inferior VHS before Beta could get there.
It failed because the porn companies all went for VHS (for licensing reasons iirc). Porn companies have decided basically every format war (including pioneering streaming).
Earlier quoted context omitted.
No. It failed because JVC saturated the market with incompatible and inferior VHS before Beta could get there.
My understanding was that Betamax had inferior licensing terms, and that it was Sony’s greed that sunk Betamax.
I'm sorry but all those examples and Deno's documentation in general should be in JavaScript. I respect the devs right to choose which ever language they want, but Deno seems to want to be the standard bearer for the power of scripting and web standards [1]. If that's the case, then they are causing more harm than good by focusing exclusively on TypeScript, which isn't a language as much as a set of macros on top of…
I do wonder about a future where JavaScript gets non-enforced optional type annotation syntax[1] which is and if said syntax will be slightly incompatible with TypeScript. That would be a little awkward for Deno, wouldn’t it. However I hope that if JS gets type annotation syntax that it would be a strict subset of TypeScript—or at the very least future compatible—for this very reason. 1. https://github.com/giltayar/p…
Edit: I should perhaps listen before I speak -- the proposal linked above talks about JSDoc and why it does not fulfill their needs, which may be the case. I have not run in to these limitations myself.
Earlier quoted context omitted.
I meant bundling your code for production.
Why would you need to do that for code running on Deno? It doesn't need to be sent over the wire.