zx VS deno

The top-level await feature for ES modules makes it easy to use await in CLI scripts (e.g., with .mjs sources and zx), and for dynamic imports and data loading. It extends the await functionality into the module loader, which means that dependent modules will wait for async modules (with top-level await) to be loaded.

Yeah, there's no reason not use Node for scripting work on the server. Google's zx library (https://github.com/google/zx) makes it easy to to do bash-like things using Node.js. You can get pretty fancy with promises and async/await to run things in parallel.

For scripting you should have a look at: https://github.com/google/zx It's nodejs but with some nice syntax sugar for scripting.

Umm, for any complex script configuration you can use https://github.com/google/zx other than that it depends on your environment and how are you supplying the value to the script

This talks a bunch about the "good run" of current scripting languages, including for example JavaScript.

But JavaScript, as an actual scripting language, has been pretty primitive but finally starting to become a real candidate for actual scripting. There's imo crufty not very great options like shelljs[1]. But adding a tagged-template string for system(), for calling things, and a little bit of standard library has made JS a much more interesting & competent scripting language. Those efforts are being done in ZX[2].

I like the idea of the topic, exploring it. But the author feels off in a number of places.

> What TypeScript showed is that you could join together the idea of a flexible lightweight (and optional!) type system onto an existing programming language, and do so successfully. . . .The question then is - what if you created a programming language from the start to have this kind of support?

Personally I just don't think languages matter very much. They're very similar, by & large. They have different tooling, packaging, somewhat different looks/feels for executing code, and their standard libraries are different. But TypeScript is popular & fast at least 90% because it is JS, because it works with JS things. Arguing that we should try to recreate TypeScript apart from JS sounds like a mind blowing waste of time. Also, Deno has good integrated TypeScript support.

On the topic of easy parallelism, JavaScript promises are imo quite easy to stitch together & use & quite available.

One of the main issues I see with easy-parallelism is that it's too easy: there's too many cases for uncontrolled parallelism. Throwing tarn.js or other worker-pools at problems seems all too common. But one is still left stitching together each pool/stage of work. I'd like to see SEDA[3] like architectures emerge, and perhaps get added to something like ZX standard library.

[1] https://github.com/shelljs/shelljs

[2] https://github.com/google/zx

[3] https://en.wikipedia.org/wiki/Staged_event-driven_architectu...

A fourth twist is to take off the functional hat and instead use an obscure corner of OOP: multiple inheritance. This isn't natively supported in JS, but some libraries use the technique in the wild (e.g. zx monkeypatches Promises with a facade over the ChildProcess interface). This differs from union types because it's two things simultaneously (rather than one OR the other), and it's up to the consumer to then await it or map over the functor if it needs to, or just access properties synchronously.

I haven't tried it myself, but zx looks like a really simple way to get up and running.

2. Runs anywhere where JavaScript does: TypeScript code converts to JavaScript which can then be run in a browser, on Node.js or Deno, and in your apps.

One recent frustration I ran into with Node's DNS is that it doesn't seem to resolve whatever.localhost to 127.0.0.1, unlike my browser.

Not entirely sure which is doing the right thing by the spec here, but I much prefer the browser behavior, because I would really like to not have to add a hosts entry for everything I reverse proxy from Caddy for doing local HTTPS/HTTP2 development, for production parity.

Oh, and I also found out that Node also isn't able to use the system-wide certs store (which local HTTPS in Caddy adds to) [1], so in the end even adding a hosts entry didn't work, and I had to revert to plaintext HTTP1. Deno is looking more attractive every day [2].

Really curious to hear how other folks are doing local HTTPS/HTTP2 setups in node these days.

[1] https://github.com/nodejs/node/issues/3159

[2] https://github.com/denoland/deno/pull/11491

import { serve } from "https://deno.land/std/http/server.ts"; import { dirname, fromFileUrl, join, } from "https://deno.land/std/path/mod.ts"; import { refresh } from "./mod.ts"; // Create useful file path variable for our code. const __dirname = fromFileUrl(dirname(import.meta.url)); const clientFilePath = join(__dirname, "./client.js"); const indexFilePath = join(__dirname, "./index.html"); // Construct the refresh middleware. const refreshMiddleware = refresh(); // Start a server on port `8000`. serve((req: Request) => { // Handle custom refresh middleware requests. const res = refreshMiddleware(req); if (res) { return res; } // Handle requests for the client-side refresh code. if (req.url.endsWith("client.js")) { const client = Deno.readTextFileSync(clientFilePath); return new Response(client, { headers: { "Content-Type": "application/javascript" } }); } // Handle requests for the page's HTML. const index = Deno.readTextFileSync(indexFilePath); return new Response(index, { headers: { "Content-Type": "text/html" } }); }); console.log("Listening on http://localhost:8000");

Deno’s permission system is broken, you shouldn’t rely on it. Deno developers consistently ignore security issues, high priority bugs take months to fix.

https://github.com/denoland/deno/issues/11964

https://github.com/denoland/deno/issues/9750

API-based access control can’t possibly work because it’s nearly impossible to predict the effect of any single permission. For example, “permission to run specific command” makes no sense without checking the integrity of the binary, controlling the environment for LD_PRELOAD-like hacks and evaluating the code of this command for possible escape hatches. If you want to isolate a program, you need to do it on the OS level.

Deno is a modern JavaScript runtime, competing with Node.js, that promises features like secure I/O and built-in TypeScript support. Ryan Dahl, Node.js' original creator, created Deno, building it in Rust.

Deno Land Inc. | Head of Growth | Remote | Full-time | https://deno.com | https://deno.land

Deno Land is a startup founded by creators of Node.js, the runtime used by millions of developers that laid the foundations for the modern web. We are continuing to innovate with our new runtime called Deno, which is already one of the most popular projects on GitHub [1].

By repurposing web browser technology for the server software, we aim to accelarate a new generation of extreme low-latency edge applications. Our nascent commercial product [2] is cloud service for hosting software built with Deno; it is one of just a couple implementations of serverless at edge in existence. Our software is being used across the industry by companies like Slack.

Head of Growth: https://deno.com/jobs/growth

Apply at [email protected]

[1] https://github.com/topics/deno

There's already such a system: Deno

zeno 🥇 ⏰ 🏃‍♂️ - Fuzzy completion and utility plugin powered by Deno.

BTW, are you aware of Deno?