3 ms·
I am hesitant to try this because of the pricing. Maybe its just me, but paying 150 bucks per month for a gloried linter seems insane. Do people actually pay t
by mkoryak 12y ago
I am hesitant to try this because of the pricing. Maybe its just me, but paying 150 bucks per month for a gloried linter seems insane.
Do people actually pay this much for this product? I would love to see some testimonials on the site, because otherwise I cant see myself liking this 150/mo worth
my 2 cents
- ThePhysicist 12y agoSolo plans actually start at 29 $ / month, and the tool is completely free of charge for open-source projects. We also have a free trial that allows you to test-drive the product for two weeks, and right now we don't charge at all for private repositories since we're still in public beta.
- mkoryak 12y agodoes a solo plan lets me lint my own commits or all commits to the repo and only I get the emails?
- ThePhysicist 12y agoAll commits in as many projects as you'd like :)
- wyldfire 12y agoIf they'd have called it a "static analyzer" they might have had an easier time selling it. Businesses regularly shell out big bucks for C/C++/Java static analysis tools like Coverity, Klocwork, etc. Static analysis is less likely to yield fruit (design errors and not false positives) in a language like Python. So the bar's definitely higher for these guys than it is for the static analysis tools for static-typed languages.
- ThePhysicist 12y agoGood point! You're absolutely right when you say that static analysis is more difficult to do for dynamically typed languages like Python. This is why we develop our own type inference algorithms in order to generate additional knowledge about the code beyond its structure, which in turn allows us to detect more interesting and relevant problems.
- wyldfire 12y agoIf they'd have called it a "static analyzer" they might have had an easier time selling it. Businesses regularly shell out big bucks for C/C++/Java static analysis tools like Coverity, Klocwork, etc. Static analysis is less likely to yield fruit (design errors and not false positives) in a language like Python. So the bar's definitely higher for these guys than it is for the static analysis tools for static-typed languages.