8 reasons developers love Go-and 8 reasons they don't
Briefly

8 reasons developers love Go-and 8 reasons they don't
"In 2007, some of the programmers at Google looked at their options for writing software and didn't like what they saw. They needed to manage millions of lines of code that would be constantly storing and shipping data for the world wide web. The code would juggle thousands or maybe millions of connections on networks throughout the globe. The data paths were full of challenges from race cases and concurrency."
"The existing programming languages weren't much help. They were built for games or managing desktops, or many of the other common tasks from a world before the web browser. Their rough edges and failure modes drove coders at Google crazy enough to start asking if there might be a better way. Was there something that could handle the I/O chores in just a few lines with all of the safety and security that Google needed?"
Go originated at Google in 2007 when programmers sought a better language for managing millions of lines of code, massive network connections, and concurrency challenges. The designers created a simple, C-like language with built-in support for concurrency and streamlined I/O. Public releases began in 2009 and version 1.0 shipped in 2012; Google continues active investment and stable releases (latest 1.22.5). The language powers core Google infrastructure and gained wide external adoption, reaching the Tiobe top ten. Design choices emphasize ease of learning, predictable rules, strong standard library, explicit error handling, and small executables—features that generate both praise and criticism.
Read at InfoWorld
Unable to calculate read time
[
|
]