4 ms·
There's a few facets to consider: 1. Does code written a particular way? 2. Does it need to be configured? 3. Does it conflict with other tooling? 4. Does i
by jfoster 4y ago
There's a few facets to consider:
1. Does code written a particular way?
2. Does it need to be configured?
3. Does it conflict with other tooling?
4. Does it have limitations that are too restrictive?
5. Does it cause bugs/issues that are difficult to resolve?
The ideal tool just does its thing, doesn't need any code written or configuration, works no matter what other tooling you're using, has no limitations, and will never itself cause a bug.
That might not be realistic to do 100%, but I think it's what all tools should be aiming for.