tinykeys VS yeoman

Hey this looks handy. I have been looking at https://github.com/jamiebuilds/tinykeys so I might have to do a comparison.

Thanks for the sharing! Just a couple of suggestions: i would prefer Ramda or lodash instead of underscore. I would additionally recommend the following libraries: - Deal with git stuff: isomorphic-git (https://github.com/isomorphic-git/isomorphic-git) is a pure JavaScript reimplementation of git that works in both Node.js and browser JavaScript environments. - Generate app from templates: yeoman (https://github.com/yeoman/yeoman) is a robust and opinionated set of tools, libraries, and a workflow that can help developers quickly build beautiful, compelling web apps. - Lint and format a code: prettier (https://github.com/prettier/prettier) is an opinionated code formatter. It enforces a consistent style by parsing your code and re-printing it with its own rules that take the maximum line length into account, wrapping code when necessary. - Deal with schemas: zod (https://github.com/colinhacks/zod) is a TypeScript-first schema declaration and validation library. I'm using the term "schema" to broadly refer to any data type, from a simple string to a complex nested object. - Deal with react state elegantly: valtio (https://github.com/pmndrs/valtio) turns the object you pass it into a self-aware proxy. - Add keybindings: tinykeys (https://github.com/jamiebuilds/tinykeys) - a tiny (~400 B) & modern library for keybindings.

Drag and Drop Visual Programming Language, the click of a button is interpreted as a source of an object stream. Think packet oriented programming, of reactive functional programming, or RxJs, or Node-RED.

To answer your question: you evaluate a low-code builder by the ease with which it can generate entire website applications. And by generate, I mean code generation as well, because you want these programs to emit beautiful code that is indistinguishable from hand made code. For code generation see yeoman, especially AST parsing and that nifty var function: https://yeoman.io/

And of course any one of the 5 above is a good test, but all 5 in harmony are better.

As to non-visual/tui tools, its bash. shells are low code tools take a look:

AT&T Archives: The UNIX Operating System:

Plop js actually allows us to create the structures that we have previously created templates on cli via command. It does this in a very simple way. I can give hygen and yeoman as an alternative to plop js. I plan to write content about these libraries in the future.

You use them to install Yeoman and the VS Code Extension Generator. This generator creates a frame (scaffold) for your extension so you don't have to write everything from scratch. If you elect to build your project using TypeScript (recommended for this blog), it's recommended that you install the TypeScript + Webpack Problem Matcher to make it easier to find and match coding errors.

Nice, reminds me of https://yeoman.io/ which was popular couple years ago

Before we can start building the extension, we need to gather and prepare the necessary tools. In this case, the needed tools are node, git, yeoman and generator-code. For a newcomer like myself, this basic tutorial is perfect. I recommend going through it to learn the fundamentals.

If you wanted something much more advanced for some actual syntax highlighting and not just word highlighting, you can you use the built-in tools to create your own language syntax highlighter. You can define words, expressions, and grammar that gets formatted and colored and more across a specific type of file (you could enable it for .txt files if you really wanted to). You'd want to install Yeoman and the VScode Extension Generator.

Maybe recheck the name ? https://www.npmjs.com/package/yo https://yeoman.io/

If you are wondering about performance cost please take a look here, especially the last comment. https://github.com/yeoman/yeoman/issues/810 . With the advent of http2 and http3 the tcp connection is never reset and in http 3 the browser can always stop and resume the image loading without throwing the current progress away. FB, Google, Shopify, Reddit and many others are all using webp which doesn't support progressive rendering and I am sure at their scale they have at least million site visits with slow network and they are doing fine.