eslint-plugin-unicorn VS picoc

XO. This feels like the Black of Typescript linting. XO has styles for everything and is very opinionated. This can be nice, because it takes a lot of code style decisions off of your plate. But beware it can be cumbersome to implement in the middle of a project because it will require extensive reformatting. In lieu of XO, I found Unicorn opinionated enough and more immediately useful.

Recently, we chose to add the Unicorn plugin, which contain dozens of ESlint rules. It can feel overwhelming at first because it triggers hundreds of errors. Fortunately, we discovered eslint-nibble: a command line tool that helps adding rules one by one with a graphical interface.

I recently scanned out codebase with https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/prefer-set-has.md and found many instances of potential "accidentally quadratic" uses of array.includes instead. gas a nice autofix to convert to set. there are some fun and sometimes useful lint rules out there...

There’s an ESLint rule for that (albeit in a plugin)

Many popular eslint configs have even introduce rules to warn on its usage for these very reasons.

eslint-plugin-unicorn

I find eslint-plugin-unicorn package pretty useful for updating old code. With IE11 dead and NodeJS v12 LTS sunsetting soon, it's a brave new world.

and picoc, but it also features interactive shell

I would like to try this C REPL: https://github.com/jpoirier/picoc

You can. People have written an interpreter for C, and you could write a compiler for Python.

Yeah, I would not choose to learn the C-shell simply because it shares a letter with the compiled language. You might be better served learning Pike or PicoC.

But don't get caught up in the VM definition, the whole act of compiling to VM bytecode and then to native is just another step in the chain. For example here is a C interpreter that lets you do the same thing, without intermediate bytecode.

Can we please cut the bullshit. By that logic no language is compiled. Because behold, a C interpreter: https://github.com/jpoirier/picoc

Languages can have a compiler, an interpreter, or both. Just because a language is commonly thought of as 'compiled' doesn't mean you can't write an interpreter for it, or vice versa. There's even C interpreters for crying out loud https://github.com/jpoirier/picoc .