1. 15
  1.  

  2. 18

    I’d sum up this to: if you don’t know a programming language well enough to know the design choices, the do/don’ts and what would you gain/lose when using it. Then there is a great chance that you’re don’t know what you’re doing…

    You don’t pick something based on zero-knowledge, don’t even try to understand it and then start a flame war just after on how wrong you were. (Especially because you didn’t understand it).

    1. 15

      I gave it 5 full days

      It took me two days to feel comfortable in Go. After almost 18 years of making websites, and I guess of those years using PHP, it is easy to pick up a new language. The concepts are universal, you only have to learn the new syntax.

      In theory the concepts are universal, however there’s so much learning involved in any stack that it’s naive to think you can jump from one to the other in a number of days (and be equally as productive). Serious bias in his comparisons - he seems so familiar with the PHP tooling that he’s looking for interchangeable features in Go. Sorry, it doesn’t work like that.

      For anyone bored or dissatisfied by their current development tools/platforms, by all means try others. But start small. Build something limited in scope that gives you a feel for the language, runtime, packaging, deployment, tooling, community etc. And don’t make a big deal about it if it doesn’t work out.

      1. 8

        I gave it 5 full days

        and

        Focus on your single main.go file. Coming from higher level languages, it is very tempting to start thinking in “namespaces” and sub-directories but that is a fool’s errand.

        I am loath to say anything unkind, however; this person does not begin to understand the concepts in Go enough to make decisions on whether it is a good tool for their project.

        I used PHP a good deal in my previous gigs, and have found that Go works well enough as PHP would for my current projects.

        1. 7

          Well what can I say there is already a reply article http://blog.breakthru.solutions/re-moving-from-php-to-go-and-back-again/

          1. 11

            I find arguments of the style “why did Facebook do X if there weren’t issues” (in this case build HHVM) or “Uber uses it for service development” very useless. It is interesting from the perspective of someone building an ecosystem, it’s not interesting for users that don’t build the next Facebook or Uber.

            Facebook is - on the scope of all software development happening - a fringe thing. Their practices and decisions are hard to apply to smaller scales, even if their tech speakers say otherwise.

            1. 4

              Yeah his analysis of go as a language revealed a highly limited understanding of the language. I suspect he kept trying to write OO PHP and then got frustrated when it didn’t work the way he thought it did.

            2. 6

              It took more time to write this blog post than trying to learn Go, so no surprise here

              1. 4

                I’m unsure that 5 days is enough to get into the headspace of any language beyond, perhaps, brainfuck.

                1. 1

                  I think 5 days is enough to write a brainfuck interpreter. Many more days are required to write brainfuck :P

                2. 3

                  Writing code has to be pleasant experience. Writing code is like painting or sculpting. You have to have a passion for it. You have to love it. Otherwise, what’s the point? You’d be better off working behind an assembly line for some car manufacturer.

                  No. I am so sick of seeing this type of nonsense. Writing code doesn’t have to be anything, and no one needs passion for it to do it. It’s absolutely nothing like painting or sculpting. His argument is that if you don’t love it and have passion for it every day, you should work in an assembly line? What kind of ridiculous train of thought is this?

                  After reading the full article, it’s obvious he’s one-dimensional and doesn’t take the time to research other things, and that’s fine. But does it mean he’s passionate enough to work in code? Maybe he should work behind an assembly line for a car manufacturer. ;)

                  1. 3

                    Most people write code for one reason: the enormous amounts of money they get paid.

                    Some of us also enjoy it

                  2. 2

                    I got really tired of this style of writing. There were tonnes of forewarning about not writing clean OOP and trying to stay in that mindset will result in failure, but I never felt like the author ever explained why. There was little substance. It sounds a lot like “I had a difficult time reproducing what I’ve already done, but in another language.”

                    Note: I did not read the whole article because I wasn’t attracted to the style of writing.

                    1. 2

                      From what I’ve read there’s a misconception on how Go should work. Definitely working with PHP and Go will be different and far from design specifications, PHP was made specifically for web development while Go wasn’t so the workflow/usage itself should be different. If you tackle Go as a web dev language and try to use it from that background, you ARE going to have some troubles getting a hold of it.