Hello Taher, Taher Alkhateeb <slidingfilame...@gmail.com> writes:
> No opinion for or against, but I'd like to mention that the majority > of our code base is xml, and the emphasis is on switching to groovy > for everything. so the return on value from linting java might not be > very high, especially since our problems in java are not primarily > formatting issues, but rather design and architectural issues. Sure I agree that linting is not very important compared to design and architecture. What is nice about automating trivial stuff such as linting is that it allows to focus on the essential parts when doing code reviews and not on the irrelevant details (indentation, naming conventions, ...). > There are many great ideas for things to improve. The question is what to > prioritize and bring to the top of your to do list. The question I have is what is on top of your todo list Taher? :-) Thanks for your input. -- Mathieu Lirzin GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
