I've lived enough of life to know this paper saved my career. Pragmatic industrial languages like Go come along once in a half generation or less. I'm glad it came my way.
119 plus ones
Shared publicly•View activity
View 3 previous comments
- well, he has a point in that (the selfish devs the golang-team is) they constructed a language that serves a purpose :)
just to put that into perspective:
* "to make the process more productive and scalable" (from the linked article)
* "Erlang was designed with the aim of improving the development of telephony applications"
* "The origin of C is closely tied to the development of the Unix operating system ... However B's inability to take advantage of some of the PDP-11's features, notably byte addressability, led to the development of C."
* "Java was originally designed for interactive television, but it was too advanced for the digital cable television industry at the time."
* " I was looking for a 'hobby' programming project that would keep me occupied during the week around Christmas" (python)
i would like to know which kind of motivation or reason to create a programming language will suffice your demands? and also: which kind of use is allowed of the so created languages? ah, i forgot: you are just trolling.Oct 27, 2014
- Starting to learn it.Oct 27, 2014
- I think one of the things this points towards is: it would be easy to say a language's job is just to be expressive and fast and provide a decent stdlib, and what happens above the language layer (code style, project structure, build/test process) is not the designers' problem.
I think the Go folks reject that, and are trying to do what they can to encourage sanity throughout the lifecycle, sometimes with language design (code style is necessarily more uniform with fewer options to sugar it up; no cyclic dependencies forces you to think about how to layer your app), sometimes with tools (fmt, doc, test, vet, build, get, golint, etc. are all first-party), sometimes with advice (Effective Go, code review comments, various talks and posts of a philosophical or practical bent). There's a lot of effort around introducing folks to it right, too (Tour, Playground, lending Gophers within Google, docs and talks). The amount of stuff written and code published can help you get a sense of what they go for in their own code (like, often, a preference for concreteness and explicitness and knowing what your code really does) even where it's not always stated.
Basically, it feels like there's attention to breadth, trying to do what they can about the many different tricky bits of writing and maintaining a lot of code, more than depth in any one thing (like, say, tuning code generation to the max like C(++) compilers do). I feel like most other recently-successful languages have a similar approach, trying to build a good car and not just a great engine. The result isn't perfect, but it's a solid, workable compromise for a lot of folks.Oct 27, 2014
- The article made me think of that stupid Quora thing. It answers every naysayer in it.
Go wasn't supposed to be fancy. It wasn't supposed to be cutting-edge academia work. It wasn't supposed to include everything and the kitchen sink.
It does what it set out to be. And I think it does that job very well thank you very much.
Go makes programming fun for me. I don't feel like I have to fight it all the time or that I'm overwhelmed by features and syntax. I just write what I want and find the libraries I need in the standard lib.
Is it perfect? No but it's close enough for me.
I just need to find an desktop application language I like as much...Oct 27, 2014
I don't want to argue about Go itself because it has no technical interest (it compiles fast? Wow, I'm super excited now!)
There have been quite a lot of languages with something of value to add recently (read: those last 30 years), I don't see the point of arguing about whether go or swift has the best flavor of semicolons. Consider rust, mercury, haskell, ATS, racket, OCaml, circa... Sadly, the only persons I've ever met that are excited by Go are people who've been stuck with a boring language for years and thus see Go as a corporate-approved way out (including at Google), while every body with a broader experience just shrug their shoulders at Go. That's why I commented on this post from Sylvain, because I'm surprised he shows some interest. Otherwise I wouldn't have commented, I usually do not interfere with fandom.
But yeah let say I'm trolling if that can comfort you.Oct 28, 2014
- you need to talk to more people, as your characterisation of Go users is not accurate in my experience.Oct 28, 2014