4 ms·
One reason I don't like Ruby is because of the numerous ways to do things - stylistic consistency makes code easier to read and gofmt gives you a universal base
by siliconc0w 3y ago
One reason I don't like Ruby is because of the numerous ways to do things - stylistic consistency makes code easier to read and gofmt gives you a universal baseline for that consistency. So I guess this is a good thing but yeah it's weird argument. I guess the key is that this is provided as optional take-or-leave situation vs the tyranny of gofmt.
Maybe in the future we can just check-in the AST and a LLM will show us the code in whatever style it knows we like best.
- lcnPylGDnU4H9OF 3y ago> I guess the key is that this is provided as optional take-or-leave situation It's a bit more than take-or-leave. Rubocop is configurable so individual projects could have their own style, no enforced style, or the default style.
- jjgreen 3y agoIt is, but how much time do you want to commit to setting it up "just right"? I don't like it because the defaults are so authoritarian -- if it can be proscribed it is -- one of the few times that Python beats Ruby hands-down, pycodestyle/pep8 is a linting Amsterdam to RuboCop's North Korea.
- wiseowise 3y agoSorry, there’s only one true formatter in Python and that’s Black.
- scruple 3y agoThat Go proverb comes to mind: "gofmt's style is nobody's favorite, but gofmt is everybody's favorite." And I don't like gofmt's output, personally, but I immediately saw the benefit to community-wide adoption specifically because of my experiences with Ruby and RoR and every project having it's own specific little (typically also totalitarian, very teapot dictator in my experience) set of StyleCop configurations. Frankly, there's a high level of bikeshedding that can open yourself up to with configurable linters that I'm too old to give a shit about. edit/ I have no horse in this race, either... I use neither of these languages today professionally.