zlacker

[parent] [thread] 4 comments
1. guappa+(OP)[view] [source] 2025-08-22 11:52:06
> The type system is most of the time very convenient

In what universe?

replies(1): >>theshr+a1
2. theshr+a1[view] [source] 2025-08-22 12:00:39
>>guappa+(OP)
In mine. It's Just Fine.

Is it the best or most robust or can you do fancy shit with it? No

But it works well enough to release reliable software along with the massive linter framework that's built on top of Go.

replies(1): >>diarrh+o81
◧◩
3. diarrh+o81[view] [source] [discussion] 2025-08-22 18:11:44
>>theshr+a1
> massive linter framework

I wonder why that ended up being necessary... ;)

replies(1): >>theshr+Rr3
◧◩◪
4. theshr+Rr3[view] [source] [discussion] 2025-08-23 15:24:19
>>diarrh+o81
All languages have linters, Go just has a proper ecosystem of them due to the way the language is built.
replies(1): >>diarrh+FK3
◧◩◪◨
5. diarrh+FK3[view] [source] [discussion] 2025-08-23 17:58:14
>>theshr+Rr3

    $ golangci-lint linters | wc -l
         107
That is a long list of linters (only a few enabled by default however). I much prefer less fragmented approaches such as clippy or ruff. It makes for a more coherent experience and surely much higher performance (1x AST parsing instead of dozens of times).
[go to top]