Why would people welcome some robot into their home as well let alone off some strange user online.

What do you all think? Would you rely on a bot android from someone you don’t know?

I’ve heard tech giants like Zuck, Bezos, and Standard Unions are building a marketplace for this, although I don’t know if I would trust these businesses in my personal space.

“The key point here is that our programmers are not researchers. They are, as a rule, very young, they come to us after their studies, perhaps they studied Java, C / C ++ or Python. They can’t understand an outstanding language, but at the same time we want them to create good software. That is why their language should be easy for them to understand and learn.”

The one thing far worse than a junior programmer is an arrogant one. And golang was created by 3 pricks.

you are contradicting yourself here, writing abstractions is a fundamental way to organize your code. in fact, it’s essential to manage increasing complexity.

As for the productivity chart, I would argue that for a static(ally typed) language, it’s more like a flat line. You probably won’t feel really productive in the beginning, but you would stay at roughly the same level, or at least lose a lot less momentum as your codebase grows. Somehow I don’t think you get magically more productive when there’s a huge codebase under you to maintain.

Go channels performance: If you happen to have some time to experiment, I guess you’ll still see that for the same task (100000 tasklets) Go is always beaten by Stackless Python, at the core of its own game. Not indicating the performance of real programs, but still funny enough.:)

I wouldn’t try Go unless I really had to, and so far I really disliked the look and feel of Go code I stumbled across. On top of that, I have the impression that the situation would be similar to Java’s, which I think is a very unfair language. Java forces you to be an OO extremist, using classes for everything like a golden hammer, meanwhile the system taking its own shortcuts, not eating its own dog food. (Maybe less so in >=8, but I’d bet it’s not really hard to find cases like that.)

As far as I can see, one of GO’s main features is a set of tools for concurrency (multi tasking).

I think your iterator routine is an example of how not to use the range keyword
If using ‘ range ‘ forces you to launch a goroutine , Then perhaps you should use a for-loop instead, I don’t know GO,
But the launching of new threads shouldn’t be done willy nilly inside of sub routines.