I was referring another comment in the thread, sorry for confusion. The OP attacks both Go and microservices, although it's no Gos fault in the story.
Also I just hate Java too, and OOP in general.
Gremour
joined 2 years ago
According to votes, hating Java is bad, but hating microservices is good.
Well, that's the architecture problem, not the language.
Hiding the complexity behind nice interfaces makes it actually more difficult to understand programming.
This is a very important point, that most of my colleagues with OOP background seem to miss. They build a bunch of abstractions and then say it's easy, because we have one liner in calling code, pretending that the rest of the code doesn't exist. Oh yes, it certainly exists! And needs to be maintained, too.
Black Mirror season 7 (I think) has an episode about this. Surgery to fix a part of brain (not cheap) installing a chip. And after some time pay a subscription to get rid of ads. And subscription gets more expensive over time.
In Go, the recommended convention for variable name length is to be proportional to their scope. It is common to use one or few letters long variables if they are local to a few lines loop or a short function.
Well, every natural plant have seeds. They need to reproduce. Those without seeds go extinct in one generation.
In Go you can compare structure instances with == (by value). You can also compare pointers (in which case they can be different even if values are equal). You get what you ask for.
Also, I've never needed "Equals" method in Go.
Usually I load machine gun turrets manually. And use them mainly to clear nests early in the game. Later, when I get my hands on oil, I build perimeter with walls, flame and laser turrets. Connect pipes with oil and connect electricity. That do the trick.
That is convenient. This way you can explain anything you like. I think, Sam Harris said "it's like playing table tennis without a net".
view more: next ›
Which suspiciously reminds optimization. Like computer game with infinite procedural world, where map chunks only generated where player interacts with world, being just formula (algorithm) everywhere else.