3 ms·
Those tools could just fix style, instead of just whining about it. I'm not even sure why code editor can produce code that does not obey agreed upon stylistic
by scotty79 12y ago
Those tools could just fix style, instead of just whining about it.
I'm not even sure why code editor can produce code that does not obey agreed upon stylistic rules. Oh, wait. It's because it's not a code editor, just a text editor. Why don't we have cod editors yet?
- andreasklinger 12y agoRegarding your first point: Most good linters enforce as many "best practices" as they enforce "style suggestions". Imho: It's important you know why / what they recommend. Regarding the second: 100% Agree.
- tessierashpool 12y ago> Why don't we have cod editors yet? I was going to snark that we do, they're called IDEs and they're horrible, but then I realized something. In between an IDE and a text editor, there could totally exist a bona fide code editor, an in-between kind of system, but we (devs) tend to cluster our solutions under two categories, namely text editors (raw, simple, direct) and IDEs (complex, featureful, enormous). This reminds me of a weird thing about testing frameworks - staggering numbers of testing frameworks get written, yet nearly all of them tend to either use "assert"-style syntax or "should/expect"-style syntax. There could totally exist other families of syntax, but there don't. (Actually, there probably do, but if so, I'm not aware of them, and it could be because they're far from the mainstream.) So with both these examples, you have this incredible diversity of implementations which can be divided really easily into just two basic categories. So even though there's an enormous amount of diversity at a very granular level, just one conceptual level up, there's almost no diversity at all. So because of all this I have to say that I think your question is actually a much better question than I initially thought.