From the ecosystem-independent ones I use and highly recommend
- `vscode-file-nesting-config` for decluttering your project folder
- `ni` to not care which of npm alternative project uses
- `eslint config` that has fine defaults for basically every framework (do note that it uses his eslint-style rather then prettier by default), which has TS JSDoc and autocompletion for rules and hides fixable rules in VSCode by default
- `taze` to check deps for updates. May be less good then pm-specific ones but works for every pm.
- `unocss` which is Tailwind clone you can actually understand - it works on regexes. Or can't because it allows to set tw classes in attributes and group them in weird ways.
I've seen only the JavaScript community where people make thousands of different libraries. This goes to show that how shallow each of these libraries are. In other languages like C++ or Rust, usually people maintain a few libraries at max.
Not to say Anthony is not a smart individual.
there are underlying differences between C++, Rust, JS. The aim of libraries are re-usability. To call a small library shallow, its your choice. If you want to drag a helpers folder with you anywhere its your choice. JS does not have the fate to have language updates as C, Rust. Code lives in many envoirements and is in many cases polyfilled/transpiled.
You are welcome to shape your point of view in this free world.
Checkout slidevjs, that may also look shallow to you. The eco-system is very open. It will never be as C++ or Rust. I believe everyone is happy where they are.
His projects are very good
From the ecosystem-independent ones I use and highly recommend
- `vscode-file-nesting-config` for decluttering your project folder
- `ni` to not care which of npm alternative project uses
- `eslint config` that has fine defaults for basically every framework (do note that it uses his eslint-style rather then prettier by default), which has TS JSDoc and autocompletion for rules and hides fixable rules in VSCode by default
- `taze` to check deps for updates. May be less good then pm-specific ones but works for every pm.
- `unocss` which is Tailwind clone you can actually understand - it works on regexes. Or can't because it allows to set tw classes in attributes and group them in weird ways.
- Vitesse theme is fine
Holy, this guy (?) is like the Stephen King of coding.
I've seen only the JavaScript community where people make thousands of different libraries. This goes to show that how shallow each of these libraries are. In other languages like C++ or Rust, usually people maintain a few libraries at max. Not to say Anthony is not a smart individual.
there are underlying differences between C++, Rust, JS. The aim of libraries are re-usability. To call a small library shallow, its your choice. If you want to drag a helpers folder with you anywhere its your choice. JS does not have the fate to have language updates as C, Rust. Code lives in many envoirements and is in many cases polyfilled/transpiled.
You are welcome to shape your point of view in this free world.
Checkout slidevjs, that may also look shallow to you. The eco-system is very open. It will never be as C++ or Rust. I believe everyone is happy where they are.