Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Deno 1.0

deno.land

Post reply on HN
Print view View original

481–490 of 598 posts

Re: Deno 1.0

#481

Post by Cthulhu_ »

fsloth wrote: post #377
bgdam wrote: post #111

The dependency management is highly questionable for me. Apart from the security concerns raised by others, I have huge concerns about availability. In it's current form, I'd never run Deno on production, because dependencies have to be loaded remotely. I understand they are fetched once and cached, but that will not help me if I'm spinning up additional servers on demand. What if the website of one of the packages I…

Why can't you download all the packages you use actually with your source code? That's how software has been built for decades... I'm a desktop developer so I understand I'm the dinosaur in the room but I've never understood why you would not cache all the component packages next to your own source code. Since this is straighforward to do I presume there is some tradeoff I've not thought about. Is it security? Do you…

For Node, the main tradeoff is number and size of files. Usually the distribution of a node module (that which is downloaded into node_modules) contains the source, documentation, distribution, tests, etc. In my current project, it adds up to 500MB already.

They would do well to have an option to optimize dependencies for vendoring.

Re: Deno 1.0

#483

Post by leetrout »

baxuz wrote: post #420
nojvek wrote: post #393

> TSC must be ported to Rust. If you're interested in collaborating on this problem, please get in touch. This is a massive undertaking. TSC is a moving target. I occasionally contribute to it. It’s a fairly complex project. Even the checker + binder (which is the core of TS) is pretty complex. One idea that comes to mind is to work with Typescript team that they are only using a subset of JS such that tsc can be com…

I see the sass / node-sass fiasco all over again...

This is referring to lib-sass being in C?

Re: Deno 1.0

#484

Post by wincent »

I tried it briefly on a side project a couple of months ago. I like some of the ideas in it, but my editor tooling (which is TypeScript-ready but not Deno-ready) wasn't ready for it. I might revisit in a year or two.

Re: Deno 1.0

#485

Post by fanf2 »

regularfry wrote: post #405
half-kh-hacker wrote: post #268

Earlier quoted context omitted.

Both the network and disk access permissions are granular, which means you can allow-write only to your logs folder, and allow net access only to your DB's address.

So it's reimplemented chmod and iptables?

A bit more like OpenBSD pledge() and unveil()

Re: Deno 1.0

#486

Post by lenkite »

petercooper wrote: post #33

If you're getting into Deno and want to keep up with new stuff from the ecosystem on a regular basis, we're now publishing https://denoweekly.com/ .. issue 2 just went out minutes after the 1.0 release. I've been doing JavaScript Weekly for 487 issues now, so this is not a flash in the pan or anything :-D Of course, Deno has an official Twitter account as well at https://twitter.com/deno_land :-)

Root certificate not trusted for https://denoweekly.com/ on both chrome and firefox.

Re: Deno 1.0

#487

Post by weeksie »

cdata wrote: post #95
weeksie wrote: post #83

This is super effing awesome. You know what would be extra amazing? Incorporating (at some point in the future) all of the very smart stuff that the unison people have been doing. That would be _tremendous_ for code re-use and guarantees about remote packages. What I wouldn't give for a JS vm that could do all that. . . . * https://www.unisonweb.org/docs/tour

I like that Deno prefers URLs as module specifiers. Need immutable/content-addressed dependency graphs? Publish and consume modules via IPFS.

Maybe I’m missing something but the reason why the concept behind unison is so neat is that identifying libraries by AST allows for the kind of code re use that Joe Armstrong was talking about. It’s not about urls as identifiers, that’s superficial.

What’s the relevance of IPFS?

Re: Deno 1.0

#488

Post by MrBoomixer »

HeavyStorm wrote: post #447
jeswin wrote: post #309

Earlier quoted context omitted.

> That combined with the 'download random code from any url and run it immediately', means it's going to be much less secure than the already not-that-secure NPM ecosystem. What deno does is move package management away from the framework distribution. This is great - one thing I hate about node is that npm is default and you get only as much security as npm gives you. (You can switch the npm repo, but it's still the…

But if Lib itself imports from "unsecure-location.com" deno will access that location and get that file.

The idea of the above example is to show a controlled distribution can be made that would verify all levels of imports if needed, which is very promising.

Re: Deno 1.0

#489

Post by genezeta »

DougBTX wrote: post #477
genezeta wrote: post #472

One question. > The browser provides APIs for accessing cameras and microphones, but users must first give permission. Deno provides analogous behaviour in the terminal. I read this and I started looking around for the camera API or maybe for the Audio API. And the thing is that I can't seem to find anything about it. I can't see anything about it in "The Manual" or in the API reference. Then I thought that there may…

I don't see it listed in the docs, but try running `deno run -h` to see the command line help. It should produce output like: -A, --allow-all Allow all permissions --allow-env Allow environment access --allow-hrtime Allow high resolution time measurement --allow-net= Allow network access --allow-plugin Allow loading plugins --allow-read= Allow file system read access --allow-run Allow running subprocesses --allow-wri…

Thanks.

Re: Deno 1.0

#490

Post by genezeta »

inglor wrote: post #476
genezeta wrote: post #472

One question. > The browser provides APIs for accessing cameras and microphones, but users must first give permission. Deno provides analogous behaviour in the terminal. I read this and I started looking around for the camera API or maybe for the Audio API. And the thing is that I can't seem to find anything about it. I can't see anything about it in "The Manual" or in the API reference. Then I thought that there may…

Confirming that there is no media API in Deno.

Thanks.
Post reply on HN