Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Acceptable linter execution time #180

Closed
Ingramz opened this issue Aug 18, 2014 · 2 comments
Closed

Acceptable linter execution time #180

Ingramz opened this issue Aug 18, 2014 · 2 comments

Comments

@Ingramz
Copy link

Ingramz commented Aug 18, 2014

Let me make myself clear first: I don't have any issues with existing linters. I'm only trying to implement one of my own.

Since AtomLinter has already a bunch of plugins for supporting different tools, it would be interesting to know how do the linters stack up against eachother when it comes to execution time. I understand that some linters are more feature-packed then others and some languages are more difficult to parse than the others. But as a small survey I would want to know what kind of speed do you consider as acceptable? Notable examples or any clever solutions applied for performance reasons would be great too.

I've tried some of the linters and when trying them both on smaller and larger files (up to 5000 lines of code), my observation is that they happened all to have execution time of under a second - some consistently faster than others though.

Also I think there should be a feature in "lint debug" that would give some feedback regarding how long the execution of that process roughly took, for time being I hacked two new Date().getTime() statements between the process execution but I'm sure there are more elegant ways to achieve this.

What are your thoughts?

@dmnd
Copy link

dmnd commented Aug 18, 2014

Seems like a reasonable idea to me 👍

@batjko
Copy link

batjko commented Aug 18, 2014

I think it's a reasonable idea for any and all packages. That kind of statistic would be helpful for developers, even just to remind and motivate them to give consideration to performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants