How can you even hint at anything being fake? The repo is 6 (six!) months old and has one whole contributor, 2 issues and 1 PR. Cleary a large community of stargazers and a perfect language.
I had my first ever vacation abroad this week and was able to witness the parades in Oslo today. So lovely, the people. As a German I am really envious of your patriotism and love for your country.
In this git-lrc-review ad I struggle to understand their purpose. They bill themselves as an Ai powered code reviewer because AI agents make mistake, so review your AI written code using their Ai (actually they do not run AI, you have to bring your own Api key) to "fix that".
Why would I not simply use the AI agent I already have to do the review? Why inject another for-profit company into the value creation chain when all they do is leech off of other AI providers' free tiers?
This reads very much like an ad for their static code analyzer. There is no real advice, just examples for what their software caught. I wonder how many of these would also be caught by golangci-lint.
Seems like Mozilla is still too rich if they can afford complete redesign of their product every 3 years. Let's hope the lepton ui fix will continue to work, I might have to up my donation there..
Oh my god, FINALLY they seem to be getting the hint that Go's CLI is abysmally bad. Go is such an amazing language, but golly, whoever perpetrated this CLI design should never be allowed to code a command line tool ever again.
I hope that they finally make the CLI better, but the cynical asshole in me can already see the outcome: Nothing will change, since the CLI is now "established" and they would "fear we break too many things".
Nice article and all, but I'm not sure about the point the author tried to make. It read more like "random notes about case sensitivity in Go module URLs". I am still unsure what flexibility the author meant to highlight.
I must be an old, boring fart, but when I see blog posts with emoji spam in every single paragraph, I feel pandered to. It reads like an MLM post on Facebook about being your own GirlBoss.
Reads like 100% unfiltered AI slop. This typical marketing speak of "Does this. No a, no B, just C." sentence structure.
Unrelated, but the default link style makes all hyperlinks unreadable.
How can you even hint at anything being fake? The repo is 6 (six!) months old and has one whole contributor, 2 issues and 1 PR. Cleary a large community of stargazers and a perfect language.
/s
I gave up on that and actually flew to Norway just to buy some books and Blurays. 😬
I had my first ever vacation abroad this week and was able to witness the parades in Oslo today. So lovely, the people. As a German I am really envious of your patriotism and love for your country.
In this git-lrc-review ad I struggle to understand their purpose. They bill themselves as an Ai powered code reviewer because AI agents make mistake, so review your AI written code using their Ai (actually they do not run AI, you have to bring your own Api key) to "fix that".
Why would I not simply use the AI agent I already have to do the review? Why inject another for-profit company into the value creation chain when all they do is leech off of other AI providers' free tiers?
This reads very much like an ad for their static code analyzer. There is no real advice, just examples for what their software caught. I wonder how many of these would also be caught by golangci-lint.
Thanks 🙃
You're very welcome.
Thanks ☺️
No AI allowed at all? Good to know. 😎
Is this just a desperate AI ad with a cheap call to action to increase engagement?
Seems like Mozilla is still too rich if they can afford complete redesign of their product every 3 years. Let's hope the lepton ui fix will continue to work, I might have to up my donation there..
Oh my god, FINALLY they seem to be getting the hint that Go's CLI is abysmally bad. Go is such an amazing language, but golly, whoever perpetrated this CLI design should never be allowed to code a command line tool ever again.
I hope that they finally make the CLI better, but the cynical asshole in me can already see the outcome: Nothing will change, since the CLI is now "established" and they would "fear we break too many things".
Nice article and all, but I'm not sure about the point the author tried to make. It read more like "random notes about case sensitivity in Go module URLs". I am still unsure what flexibility the author meant to highlight.
Thanks for posting nonetheless.
InsertYourCommentHere!
"targets crypto wallet add-ons" -- OK so is regular sane folk are not at risk.
All true, but regarding #1: the size of the go.sum and all the indirect deps in the go.mod are also telling me a lot already :)
Is vendoring really going to help? Vendor or not, you need to review your deps' code.
Go's go.sum should already protect against malicious changes in upstream packages, no?
I must be an old, boring fart, but when I see blog posts with emoji spam in every single paragraph, I feel pandered to. It reads like an MLM post on Facebook about being your own GirlBoss.