5 ms·
Do you generally pylint an entire codebase at once though? Why not just the file you are actually working on? Based on the homeassistant results (10.3 hours to
by voidUpdate 4mo ago
Do you generally pylint an entire codebase at once though? Why not just the file you are actually working on? Based on the homeassistant results (10.3 hours to lint 17.5k files), it only takes about 2 seconds to pylint a file, which doesn't really feel like enough of a wait to need an entirely new linter
- deviation 4mo agoThey may instead be targeting folks that run it in CI.
- psd1 3mo agoA delay of two seconds in my commit hook pushes my blood to the hydraulic pressure of a 70-ton digger.
- voidUpdate 3mo agoThen have it run asynchronously when you save
- lelanthran 3mo ago> A delay of two seconds in my commit hook pushes my blood to the hydraulic pressure of a 70-ton digger. Why though? Surely you have it set up to lint as you edit? I know my neovim installation does that and I see the results in the editor as I type. If it's a rule that linting needs to be in the commit hook, maybe the linter should write a hash of the files linted somewhere. The commit hook script then only lints those files that have changed since the last lint took place.
- psd1 3mo ago[dead]
- odiroot 3mo agoCommit hooks just don't make that much sense. Push hooks are much better idea. Once you're done with all your work, linting, last minute adjustments and whatnot, push it and get the checks result. If something goes wrong, your push is blocked.
- andai 3mo agoIn user experience land, 2000ms is not tiny, it's catastrophic. In interactive software, a single dropped frame is noticeable and irritating. Programming is an interactive experience.
- flyingbeaver09 3mo agohopefully I never have to work with you if you think 2 seconds for libting is fine
- voidUpdate 3mo agoand hopefully I never have to work with you if you think that every single second must be spent coding, no seconds allowed for stuff to process in the background when you save a file
- wiseowise 3mo ago2 seconds is an eternity for a check since the last edit. I expect IDE to respond real time as I type.
- wiseowise 3mo ago2 seconds is bonkers to check a single file.
- jkercher 3mo agoHa. I'm probably in the more anti AI camp, but if it could free us from the plague that is Python thinking, I might change my tune. 2 seconds might feel negligible in the real world, but it is damn near an eternity in the supercomputers we're all running.