Well now. My primary exposure to Go would be using it to take first place in my company's 'Advent of Code' several years ago, in order to see what it was like, after which I've been pleased never to have to use it again. Some of our teams have used it to provide microservices - REST APIs that do database queries, some lightweight logic, and conversion to and from JSON - and my experience of working with that is that they've inexplicably managed to scatter all the logic among dozens of files, for what might be done with 80 lines of Python. I suspect the problem in that case is the developers, though.

It has some good aspects - I like how easy it is to do a static build that can be deployed in a container.

The actual language itself I find fairly abominable. The lack of exceptions means that error handling is all through everything, and not necessarily any better than other modern languages. The lack of overloads means that you'll have multiple definitions of eg. Math.min cluttering things up. I don't think the container classes are particularly good. The implementation of pointers seems solely implemented to let you have null pointer exceptions, it's a pointless wart.

If what you're wanting to code is the kind of thing that Google do, in the exact same way that Google do it, and you have a team of hipsters who all know how it works, then it may be a fine choice. Otherwise I would probably recommend using something else.

I used it for a while and I think it's been one of the best languages I've tried. C for example is too barebones for modern desktop apps. Apps written in Rust are great but most of the time, it's just not worth the effort. And stuff like Python, JS is... uhh.. where do I even begin

I think Go hits the sweet spot between these. Unlike C, it at least has some simple error/panic mechanism, GC so you don't have to worry about memory much and some modern features on top of that. And unlike Python it can actually create reasonably snappy programs.

In any programming language, there will always be multiple cases where you need to link C libraries. CGo, although people don't seem to be adoring it, is actually... okay? I mean of course it does still have some overhead but it's still one of the nicer ways to link C libraries with your code. And Go being similar to C makes writing bindings so much easier

Multithreading in Go is lovely. Or as I read somewhere "you merely adopted multithreading, I was born with it"

Packaging is handled pretty nicely, pulling a library from the net is fairly trivial. And the standard directory structure for Go, although I'm not used to it, makes organizing stuff much easier and is easy to adopt

As you would've guessed from the amount of times I mentioned C in this comment, I basically see Go as the "bigger C for different situations"

Go code is always an abomination.

Enough of that crazy talk - plainly WheeledDeviceServiceFactoryBeanImpl is where the dependency injection annotations are placed. If you can decide what the code does without stepping through it with a debugger, and any backtrace doesn't have at least two hundred lines of Spring boot, then plainly it isn't enterprise enough.

Fair enough, though. You can write stupid overly-abstract shit in any language, but Java does encourage it.

Does Lua rank far below python for you? I have so much rage against it. At least with Python I don't have to do a bunch of steps to just get it to do something. May take me a while to get through bad Python code, but Lua makes my eyes bleed and I begin to regret my life choices in trying to understand wtf these people wrote.