Golang be like

If it is a pure value, I'd assume yes, but if it is tied to a side effect (E.g. write its value to a file), then it would be not used but still could break your app if removed.

I'm not familiar with rust language specifically, but generally that's what could happen

Yeah that should be looked for in a CI line check, not a compilation requirement

Yeah any compiler should support environments or config files. Our CI would never work with without --env “stage”

Some people simply ignore warnings, that's the main issue. Trust me, I saw this way too often.

If you cannot compile it than you have to fix it, otherwise just mark unused variables as 'not an error' via _ = someunusedvar.

The language was designed to be as simple as possible, as to not confuse the developers at Google. I know this sounds like something I made up in bad faith, but it's really not.

The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt. – Rob Pike

"It must be familiar, roughly C-like. Programmers working at Google are early in their careers and are most familiar with procedural languages, particularly from the C family. The need to get programmers productive quickly in a new language means that the language cannot be too radical. – Rob Pike

The infamous if err != nil blocks are a consequence of building the language around tuples (as opposed to, say, sum types like in Rust) and treating errors as values like in C. Rob Pike attempts to explain why it's not a big deal here.

a desperate fear of modular code that provides sound and safe abstractions over common patterns. that the language failed to learn from Java and was eventually forced to add generics anyway - a lesson from 2004 - says everything worth saying about the language.

As far as C++ goes, that's probably the only sane way to use the language.

Never really coded in Go outside of trying it out, but as far as I know it's a hard error.

I'm with you, exceptions sound good but are a bug factory.

There's nothing sane and readable about how Go insists you format dates and time. It is one of the dumbest language features I've ever seen.

Yeah, insisting on things like a variable being used will result in people using work arounds. It won't result in people not doing it.

Then, because people trust the language to police this rule, the work-arounds and debug code will get committed.

 go

    
func main() {  
    test := true  
}  

  

Oops, golang doesn't like that.

 golang

    
func main() {  
    test := true  
    _ = test  
}


  

Perfectly cromulent code.

If they really wanted to avoid people having unused variables, they should have used a naming convention. Any variable not prefixed by "_" or "debug" or whatever has to be used, for example. Then block any code being checked in that still contains those markers.

I agree that golang is being dumb when you don't even have the option to tell it that this is a testing env or something. But the thing about syntax highlighting is not the same. One is about handholding the developer so much that it makes it even more difficult to develop, and the other is a completely optional feature that is so uselful and non intrusive that even wizardly editors like emacs use it.

I concur, it is a problem with that workplace. (In this case, OP is just sharing a funny meme. I wouldn’t suggest this meme means they’re a problem. I could have made this meme and I love the feature.)

Developing on a team at a company is like the “Wild West.” What’s considered to be acceptable will not only vary from workplace to workplace, but it can also fluctuate as developers and managers come and Go. Each of them have their own unique personality with their own outlook on what “quality” code looks like. (And many of them do not care about code quality whatsoever. They just need to survive 1-2 years there, make management happy with speedy deliveries, and then they can move on to the next company with a 30% pay bump.)

Having experienced working with developers who frequently filled with code base with unused code while having no control over who will leave or join as a contributor to the code base, I think features like this make for a more sane development experience when you’re developing with a team of seemingly random people that you never personally invited to contribute to the code base.

will not merge your PR unless the stricter rules are met.

This doesn’t fly when you work in big corporate and the boss doesn’t care about the code meeting stricter rules. “A working prototype? No it’s not- that’s an MVP! Deploy it to production now and move onto the next project!”

It is VERY annoying when you're hunting for a bug. For example, when you comment out a function call to debug an issue, the compiler might suddenly complains about unused variables, so you'll need to comment them out as well. Repeat several times and you'll start having an urge to smack the monitor.

🫡

Which is have been able to use since we switched to C++17 ... a couple of months ago.

That's why I said ESLint

It's a Linter for JavaScript. Some people might not know what ESLint is that's why I put it in brackets