I often see articles that say, "The programming language 'C++' is hated".

However, if you go to a large bookstore, you can see the number of C/C++ books is overwhelming.

Half of the books related to programming languages are often C/C++ books.

Well, C/C++ is chosen because of its "low-level interface that maximizes hardware performance."

and,

C/C++ is disliked because of the "fear of system downtime caused by memory leaks."

I think that.

Languages in which garbage collection is implemented are naturally slower to execute.

It is precisely because of the wildness that can be implemented with impunity, without worrying about such troublesome things, that C/C++ continues to reign as the fastest language to this day.

-----

While on assignment in the U.S., I found a workaround for this problem of memory leaks that I was experiencing locally in a "commercial library".

I remember presenting it at a meeting and receiving (I think) rave reviews from the members.

I remember being surprised that 'engineers in this country tolerate memory leaks.

Incidentally, at our company at that time, the engineer who implemented memory leak had to keep hanging his head, with hearing "you are an idiot, a moron, and should die".

-----

I heard that "Google will use the C++ mechanism as a foundation to develop Carbon, which is compatible with C++."

"Google Idiot"

"I don't want that! "

Instead of developing something like that, release an extended version of C++ from the get-go! with

(1) Scalable lightweight threads (goroutine's), and

(2) Additional channels are implemented

I want to say that.

By the way, I am O.K that "memory leaks" is 'dumb engineer proof'"

Garbage collection is not a good idea because it makes it impossible to know the exact program execution time.

-----

Well, anyway, I plan to make Golang the last programming language of my life, so, well, I don't care what language comes out now.