dido:public:ra:xapend:xapend.b_stds:defact:google:go
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:google:go [2020/11/13 02:20] nick ↷ Page moved from dido:public:ra:xapend:xapend.stds:defact:google:go to dido:public:ra:xapend:xapend.b_stds:defact:google:go |
dido:public:ra:xapend:xapend.b_stds:defact:google:go [2021/11/09 15:41] (current) char ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Google: Go (software language) ===== | ===== Google: Go (software language) ===== | ||
| - | [[dido:public:ra:xapend:xapend.stds:defact:google| return to Google page ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:google:start| return to Google page ]] |
| **Source: [[https://golang.org/doc/faq#go_or_golang | The following is from the ''Golang.ord'' site ]]** | **Source: [[https://golang.org/doc/faq#go_or_golang | The following is from the ''Golang.ord'' site ]]** | ||
| Line 9: | Line 9: | ||
| : //Go was born out of frustration with existing languages and environments for the work we were doing at Google. Programming had become too difficult and the choice of languages was partly to blame. One had to choose either efficient compilation, efficient execution, or ease of programming; all three were not available in the same mainstream language. Programmers who could were choosing ease over safety and efficiency by moving to dynamically typed languages such as Python and JavaScript rather than C++ or, to a lesser extent, Java.// | : //Go was born out of frustration with existing languages and environments for the work we were doing at Google. Programming had become too difficult and the choice of languages was partly to blame. One had to choose either efficient compilation, efficient execution, or ease of programming; all three were not available in the same mainstream language. Programmers who could were choosing ease over safety and efficiency by moving to dynamically typed languages such as Python and JavaScript rather than C++ or, to a lesser extent, Java.// | ||
| - | : //We were not alone in our concerns. After many years with a pretty quiet landscape for programming languages, Go was among the first of several new languages—Rust, Elixir, Swift, and more—that have made programming language development an active, almost mainstream field again.// | + | : //We were not alone in our concerns. After many years with a pretty quiet landscape for [[dido:public:ra:xapend:xapend.a_glossary:p:programlang|programming languages]], Go was among the first of several new languages—Rust, Elixir, Swift, and more—that have made programming language development an active, almost mainstream field again.// |
| : //Go addressed these issues by attempting to combine the ease of programming of an interpreted, dynamically typed language with the efficiency and safety of a statically typed, compiled language. It also aimed to be modern, with support for networked and multicore computing. Finally, working with Go is intended to be fast: it should take at most a few seconds to build a large executable on a single computer. To meet these goals required addressing a number of linguistic issues: an expressive but lightweight type system; concurrency and garbage collection; rigid dependency specification; and so on. These cannot be addressed well by libraries or tools; a new language was called for.// | : //Go addressed these issues by attempting to combine the ease of programming of an interpreted, dynamically typed language with the efficiency and safety of a statically typed, compiled language. It also aimed to be modern, with support for networked and multicore computing. Finally, working with Go is intended to be fast: it should take at most a few seconds to build a large executable on a single computer. To meet these goals required addressing a number of linguistic issues: an expressive but lightweight type system; concurrency and garbage collection; rigid dependency specification; and so on. These cannot be addressed well by libraries or tools; a new language was called for.// | ||
| Line 21: | Line 21: | ||
| | Paradigm | Multi-paradigm: concurrent, functional,(( | | Paradigm | Multi-paradigm: concurrent, functional,(( | ||
| "First-Class Functions in Go". Retrieved November 14, 2018. Go supports ... a functional programming style in a strongly typed language. | "First-Class Functions in Go". Retrieved November 14, 2018. Go supports ... a functional programming style in a strongly typed language. | ||
| - | )) imperative, object-oriented (( | + | )) [[dido:public:ra:xapend:xapend.a_glossary:i:imperative | imperative]], object-oriented (( |
| Is Go an object-oriented language?". Retrieved April 13, 2019. Although Go has types and methods and allows an object-oriented style of programming, there is no type hierarchy. | Is Go an object-oriented language?". Retrieved April 13, 2019. Although Go has types and methods and allows an object-oriented style of programming, there is no type hierarchy. | ||
| ))(( | ))(( | ||
| Line 55: | Line 55: | ||
| | Website | https://golang.org/ | | | Website | https://golang.org/ | | ||
| </table> | </table> | ||
| + | |||
| + | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
| + | /* To add a discussion page to this page, comment out the line that says | ||
| + | ~~DISCUSSION:off~~ | ||
| + | */ | ||
| + | ~~DISCUSSION:on|Outstanding Issues~~ | ||
| + | ~~DISCUSSION:off~~ | ||
dido/public/ra/xapend/xapend.b_stds/defact/google/go.1605252035.txt.gz · Last modified: 2020/11/13 02:20 by nick
