deno-cliffy VS zig

Also with Deno, it become very easy to write typed cli. .ts file can be run as script very easily with permission access defined on top of the script such as:

#!/usr/bin/env -S deno run --allow-net

Then one can just run ./test.ts if the script has +x permission.

Also project such as https://cliffy.io has made writing cli way more enjoyable than node.

It is a good idea to beware of the VC. So it is good idea to support project such as Hono (projects conform to modern web standard, and is runtime agnostic for JS).

import * as hoipoiCapsule from "https://deno.land/x/[email protected]/mod.ts"; const commitMessageTemplate = `{{type}}({{scope}}): {{summary}} {{body}} BREAKING CHANGE: {{breakingChange}}`; hoipoiCapsule.useCase.fillInCommitMessage.run({ commitMessageTemplate, questionList: [ { /** * The answer applies to the {{type}} part of commitMessageTemplate. */ target: "type", /** * Pre-prepared questions. */ q: hoipoiCapsule.preset.fillInCommitMessage.conventionalcommits.qMap.type, /** * Thus, you can also create your own questions. */ // q: typeQ, /** * Modify the commit message. * Use this function when a message is unanswered, for example. */ fixCommitMessage: (p) => { if (p.answerMap["type"] === "???") { return p.commitMessage.replace(/\r?\n{2,}/, "\n").trim(); } return p.commitMessage; }, }, ], }); /** * Please check here. * https://github.com/c4spar/deno-cliffy */ const typeQ = () => hoipoiCapsule.userInterface.prompt.Select.prompt({ message: "Select type.", search: true, options: [ { name: "Build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)", value: "Build", }, { name: "CI: Changes to our CI configuration files and scripts (examples: CircleCi, SauceLabs)", value: "CI", }, { name: "Docs: Documentation only changes", value: "Docs" }, { name: "Feat: A new feature", value: "Feat" }, { name: "Fix: A bug fix", value: "Fix:" }, { name: "Perf: A code change that improves performance", value: "Perf" }, { name: "Refactor: A code change that neither fixes a bug nor adds a feature", value: "Refactor", }, { name: "Test: Adding missing tests or correcting existing tests", value: "Test", }, ], });

Just wanted to add that v0.0.6 has been released. I changed to a more refined CLI library using https://github.com/c4spar/deno-cliffy/ so that it can be more easily maintained. Still works just the same, but more refined and clean code since when it may have been previously looked at.

There is an issue proposing this approach: https://github.com/ziglang/zig/issues/4284

https://github.com/ziglang/zig/issues/224

e.g.:

> > When debugging/prototyping, it's useful to comment out a line without having to refactor, e.g.

When writing code in a scripting language, sometimes you need that extra bit of performance (or maybe an async feature from Zig).

NodeJS is by no means a slow runtime, it wouldn’t be so popular if it was. But compared to Bun, it’s slow. Bun was built from the ground up with speed in mind, using both JavascriptCore and Zig. The Bun team spent an enormous amount of time and energy trying to make Bun fast, including lots of profiling, benchmarking, and optimizations.

ntdll.dll!RtlUserThreadStart()

There are valid reasons to use APIs from NTDLL. Where I disagree with zig#1840 is the idea that it is always better to use NTDLL versions of API. Every other software ecosystem uses the standard Win32 APIs and diverging from that without a good reason seems like a good way to have unexpected behavior. One concrete example is most users and programmers expect Windows to redirect some file system paths when running on WOW64. But this is implemented in Kernel32, not ntdll.

https://github.com/ziglang/zig/issues/11894

Zig also has an IRC channel on libera (#zig) that is moderated by Andrew Kelley.[1]

[1] https://github.com/ziglang/zig/wiki/Community