▲ | IshKebab 8 hours ago | |||||||||||||
1. Terrible performance. 2. Terrible installation UX. The number of issues we've had with pre-commit because it's written in Python and Python tooling breaks constantly... In fairness, the latter point may be finally solved by using `uv` and `uv tool install`. Performance is still a major issue though. Yamllint is easily the slowest linter we use. (I'm tempted to try rewriting it in Rust with AI.) | ||||||||||||||
▲ | mcswell an hour ago | parent | next [-] | |||||||||||||
> 1. Terrible performance Performance only matters if you're doing something compute- or disk-intensive, and then only if the libraries you're using are Python all the way down. (AI programming, at least the kind that most of us do--I don't know about places like OpenAI) is generally done with Python using libraries that use some compiled language under the hood. And in this case--a linter--performance is almost certainly never an issue. | ||||||||||||||
▲ | turtlebits 2 hours ago | parent | prev | next [-] | |||||||||||||
Then remove it? There's always tradeoffs adding tooling - I'm assuming you have it in your workflow to catch downstream issues because it saves more time in the long run. | ||||||||||||||
▲ | viraptor 7 hours ago | parent | prev [-] | |||||||||||||
It definitely is a problem when the tool you're going to use a few times a week takes an extra hundred milliseconds compared to a native solution. Especially when you need to process huge data files like hand crafted makefiles. I can totally feel your pain - extra effort would've been made to avoid that at the cost of development speed. /s | ||||||||||||||
|