Re:Deno 1.6 supports compiling TypeScript to a single execut...
by jay_kyburz on Wednesday December 09, 2020 @08:40PM
(#25368459)
Using URLs is like having an iframe to somebody else's website on your website.
[ Parent
| on HN ]
Re:Deno 1.6 supports compiling TypeScript to a single execut...
by wperron on Thursday December 10, 2020 @10:54AM
(#25374998)
Maybe... it depends on the amount of _trust_ that you put in the remote domain. My prediction is that the Deno ecosystem will aggregate around a few, large repositories that will have good guarantees araound immutability and good track records to addressing vulnerabilities.
For large projects like React, lodash, eslint whatever, I expect some of them will start hosting their libraries on their own networks, like it used to be when Javascript was only frontend and you would have a script tag importing jQuery directly from jQuery's CDN. The reason it worked was because jQuery was sidely known and trusted.
Re:Deno 1.6 supports compiling TypeScript to a single execut...
by Soremwar on Thursday December 10, 2020 @02:03AM
(#25370720)
Whot? How is that even comparable? It's third party code after all, the same happens when you use a library in any other language
Re:Deno 1.6 supports compiling TypeScript to a single execut...
by jay_kyburz on Thursday December 10, 2020 @07:59PM
(#25381001)
A library in any other language is saved local and built with your project.
My understanding is these are loaded from URLs if they are not in the cache. If a domain changes hands, you could be served anything.
Re:Deno 1.6 supports compiling TypeScript to a single execut...
by laurencerowe on Saturday December 12, 2020 @01:54PM
(#25400504)
Presumably you’d use deno bundle for a production build so you’re not directly using the source files.