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

Deno 1.6 supports compiling TypeScript to a single executable

github.com

Post reply on HN
Print view View original

181–190 of 284 posts

Re: Deno 1.6 supports compiling TypeScript to a single executable

#181

Post by DougBTX »

zelly wrote: post #134
Hokusai wrote: post #21

Earlier quoted context omitted.

> A lot of languages are doing single static binary deploys now As a developer for more than 30 years, I find that statement quite interesting. When I was a kid I was very happy to find a way to compile Basic to an executable like I was doing in Pascal and C++. For me is the standard way of thinking about applications. Is it a common experience to actually have to ship many files for one application? I thought that i…

Containers changed the game. 99% of Deno/Go/Rust server software will be running on containers in practice. You're no longer deploying to a system running other programs which may share pages. It's a container, not a process. Dynamic linking in a container is just a vestigial useless step.

Interesting, that’s the opposite of my experience. Containers allow bundling up lots of dynamic dependencies together so that they can be installed as a single unit. Static binaries can just be deployed as a single file, no need for containers.

Re: Deno 1.6 supports compiling TypeScript to a single executable

#182

Post by z3t4 »

cjonas wrote: post #155
jjnoakes wrote: post #70

Earlier quoted context omitted.

What I do is generate a random token, pass it to the browser I spawn, and only accept requests that include the token.

Wouldn't proper CORS be enough? I guess you would have to avoid putting any sensitive data in GET requests

One problem is that we developers are lazy and use Access-Control-Allow-Origin: * (wild star) instead of actual hostname. (eg. allowing all origins to access the backend)

No modern browser allows access to localhost without that header.

But it's still possible to forge a request using curl or whatever to bypass CORS. So as the parent post suggest - use a token of some sort.

I also recommend using a strict Content-Security-Policy to stop X-site injection attacks. (eg someone adding an image to your page/app with src="/api/cmd=rm -rf /"

Re: Deno 1.6 supports compiling TypeScript to a single executable

#183

Post by hombre_fatal »

bobthebuilders wrote: post #147
nikisweeting wrote: post #84

Earlier quoted context omitted.

I think go is the perfect example of how not to do module source distribution. Because of their URL dependency system Golang projects work great as static binaries, but they're almost impossible to distribute as source builds via system package managers. A lot of my arguments for why this is a bad thing are already laid out here: https://docs.monadical.com/s/against-curl-sh (I don't know how many more replies we have…

I think what Deno is great because it lets me be decentralized. We did so much with open source only to throw it all away with npm and go back to a centralized corporate entity :(

package.json supports urls, git urls (and branch + commit ids), even local file paths. If you wanted that, what's stopping you?

Re: Deno 1.6 supports compiling TypeScript to a single executable

#184

Post by gouggoug »

pjmlp wrote: post #33
Hokusai wrote: post #21

Earlier quoted context omitted.

> A lot of languages are doing single static binary deploys now As a developer for more than 30 years, I find that statement quite interesting. When I was a kid I was very happy to find a way to compile Basic to an executable like I was doing in Pascal and C++. For me is the standard way of thinking about applications. Is it a common experience to actually have to ship many files for one application? I thought that i…

Same here, the static linking hype feels real strange, given that was the only option we used to have back in the day, and having access to dynamic linking on 16 bit platforms felt like liberating.

I imagine dynamic linking solved a problem for a long time that no longer is: binary size.

With internet speeds of today and immense storage sizes, the main attractiveness of dynamic linking vanished.

Re: Deno 1.6 supports compiling TypeScript to a single executable

#185

Post by mark_and_sweep »

nikisweeting wrote: post #109
mark_and_sweep wrote: post #101

Earlier quoted context omitted.

> I just wish they also supported importing from local npm packages installed in node_modules without needing to specify a URL/full path. Import maps allow you to do that, see: https://deno.land/manual/linking_to_external_code/import_map...

Ah cool, that helps a ton. The existence of this feature as the linchpin for compatibility with npm is not clear from the rest of the Deno docs though. Perhaps it could be linked to from this page: https://deno.land/manual@v1.6.0/examples/import_export . Also, it seems as though ./node_modules/ being the default could be assumed automatically though, no? "imports": { "moment": "/node_modules/moment/src/moment.js", "l…

> Also, it seems as though ./node_modules/ being the default could be assumed automatically though, no?

No, there is no magic node_modules directory in any other JS environment, other than Node. Deno aims to be compatible with web standards. Import and import maps are web standards, require and node_modules aren't.

> Deno would be a drop-in replacement and we could move our whole codebase over to it overnight

The reason that you cannot move your existing codebase to Deno tonight is essentially the poor web compat of the existing Node ecosystem.

Re: Deno 1.6 supports compiling TypeScript to a single executable

#186

Post by Mulpze15 »

z3t4 wrote: post #180
Mulpze15 wrote: post #167

Earlier quoted context omitted.

I am trying to do this too. But I would like to make it work on MacOS as well. The problem there is Safari does not let you connect to localhost over http. So if Safari is the preferred browser of the user, you need to convince them to change, which is hard. Or is there à better way there?

I can connect to localhost on Safari Version 14.0.1 Make sure you also load index.htm from the same host! (localhost) so you need a little web server in your app that serves that file. One problem is however that there is no easy way to get Safari to run in chromeless/app mode (without browser/url bar etc), which you can do in most other browsers using --app=url flag

Thank you, I will try. I was actually trying to mix web app (https:// mydomain.com) and connecting to localhost. And yes, a localhost URL in the bar looks ugly... Trade-offs...

Re: Deno 1.6 supports compiling TypeScript to a single executable

#187

Post by qeternity »

ameliaquining wrote: post #170
205g0 wrote: post #144

Earlier quoted context omitted.

> then in many scenarios it'd be a lot easier to deploy It's not. Most advanced deployments nowadays use container orchestration where deploying is as easy. For simple deployments (eg SSGs) there're enough products on the market. Integrating the build step hides it at the same time (good for beginners) but creates many other problems in the long run if we just talk about repackaging the run-time.

I think you're underestimating the diversity of environments out there. Not everyone's using cutting-edge deployment tech; lots of folks are just SSHing or RDPing into a physical or virtual server, copying stuff there, and running it. Certainly, that's how things were done at my last job. And it can get worse; some of these environments are locked down in some way or another, by security policies that limit what you…

I’m not sure this should be encouraged...

Re: Deno 1.6 supports compiling TypeScript to a single executable

#188

Post by mark_and_sweep »

mpoteat wrote: post #65
bartlomieju wrote: post #53

Earlier quoted context omitted.

Deno is a JavaScript runtime much like Node. For the reasons on why creating Deno I recommend "10 Things I Regret About Node" by Deno's author [1] Deno is different than Node in several aspects; most notably: - Deno supports only ES modules, there's no built-in support for CommonJS modules - Deno's APIs are all promised based - Deno does not use NPM, instead it can pull code from any URL, much like browsers do - Deno…

Personally I appreciate being able to choose my linter, compiler, dialect etc. I also tend to prefer distributed solutions. Deno running the entire environment is a negative for me, at least for now. To me, it just shows an approach of ignoring what already exists and reinventing the wheel. I've tried to get Deno to work before in production, but it had so many compatibility issues last I tried it would take weeks or…

> Personally I appreciate being able to choose my linter, compiler, dialect etc. (...) Deno running the entire environment is a negative for me, at least for now.

Nobody forces you to use the deno dev tools. You can still run eslint, prettier and closurescript, if that's your sort of thing.

Personally, I prefer deno lint over eslint and deno fmt over prettier since they are much faster. I'm even using dprint (which is a standalone project for code formatting, https://dprint.dev/) in Node projects.

Similarly, before deno test, I created my own deno testing tool. Now I use deno test instead since it's just better - not because anyone's forcing me to use it.

The integrated dev tools are a convenience feature. I hope that's kinda obvious.

Re: Deno 1.6 supports compiling TypeScript to a single executable

#189

Post by [deleted] »

zelly wrote: post #134
Hokusai wrote: post #21

Earlier quoted context omitted.

> A lot of languages are doing single static binary deploys now As a developer for more than 30 years, I find that statement quite interesting. When I was a kid I was very happy to find a way to compile Basic to an executable like I was doing in Pascal and C++. For me is the standard way of thinking about applications. Is it a common experience to actually have to ship many files for one application? I thought that i…

Containers changed the game. 99% of Deno/Go/Rust server software will be running on containers in practice. You're no longer deploying to a system running other programs which may share pages. It's a container, not a process. Dynamic linking in a container is just a vestigial useless step.

[deleted]

Re: Deno 1.6 supports compiling TypeScript to a single executable

#190

Post by pjmlp »

gouggoug wrote: post #184
pjmlp wrote: post #33

Earlier quoted context omitted.

Same here, the static linking hype feels real strange, given that was the only option we used to have back in the day, and having access to dynamic linking on 16 bit platforms felt like liberating.

I imagine dynamic linking solved a problem for a long time that no longer is: binary size. With internet speeds of today and immense storage sizes, the main attractiveness of dynamic linking vanished.

Not everyone is blessed with such connections, without data caps.
Post reply on HN