4 ms·

I agree that Go makes programming simple, in a matter of less than 6months, I learned how to write a webapp in Go just by using the standard library, later, I w

I agree that Go makes programming simple, in a matter of less than 6months, I learned how to write a webapp in Go just by using the standard library, later, I wrote a guide to teach how to write webapps in Go without using a framework, using an example based approach https://github.com/thewhitetulip/web-dev-golang-anti-textbook/ https://github.com/thewhitetulip/web-dev-golang-anti-textboo...

camus2 10y ago
> Go makes programming simple Go is simple for simple tasks that fit Go type system, and yes the single formatting standard and the linting helps with readability. Go is a pain in the ass for complex tasks that don't fit go type system, like de-serializing polymorphic data or working with XML. But at the end of the day, the lack of polymorphism in the language makes complex things way more complex than they should be. Finally, Go relies way to much on runtime behavior for a statically typed language.
- why-el 10y ago
  These are quite unsubstantiated claims. Go is used in many a non-trivial program, such as Kubernetes, Docker, Google internal projects, and so on, and the one denominator among these is the plethora of data formats they need to work with.
  - PopsiclePete 10y ago
    His claim isn't necessarily wrong, and neither is yours. I find dynamically-typed languages easier to work with when dealing with (de)serialization, it's just that Go isn't too horrible at that to warrant abandoning it and losing out on its other niceties in favor of a different stack. I mean, everything sucks at something, and Go's type-system isn't....great....but it's "good enough" to where you just kind of curl your lips in slight disapproval sometimes instead of tearing your hair out.
xiaoma 10y ago
> "I agree that Go makes programming simple, in a matter of less than 6months, I learned how to write a webapp in Go just by using the standard library" I've met non-technical people who were able to make a webapp in PHP after 6 days with just the standard library and the O'Reilly Head First book.
2_listerine_pls 10y ago
6 months? that's a lot of time.
- thewhitetulip 10y ago
  It isn't if you add learning web dev from scratch. I had never ever worked with webdev before
  - chickenfries 10y ago
    So then you have nothing to compare it to, and you can't say that Go made things simpler or faster than if you had started making web apps in say, python.
    - deleted 10y ago
      [deleted]
    - thewhitetulip 10y ago
      I had tried my hand with Django and flask, just read the tutorials, and for 6-7 months, I was still reading tutorials, and every 6 months a new version of framework would come up, and I'd be upgrading stuff. I would write views without understanding what they really mean. Maybe I learned Python webdev in a wrong way, so, compared to that, Gonwas a cakewalk.
      - chickenfries 10y ago
        So you don't think the background knowledge you gained about web dev in 6-7 months of studying python helped you pick it up faster in Go? > for 6-7 months, I was still reading tutorials, and every 6 months a new version of framework would come up So, according to you, the invention of ONE new python framework caused you to rewrite everything you had been working on? What frameworks did you switch between? Why? Golang is a popular language now, and there are going to be frameworks coming out all the time. There are already lots of Golang webdev frameworks. Imagine if you were starting with Go now, and you learned something like Revel (https://revel.github.io/ https://revel.github.io/) before learning how to make web apps with the standard library. Or imagine you spent 6 months learning a framework and then decided to jump to a new one when another one came out. Also, from perusing the introduction to your Golang book, it seems like you were lacking knowledge of HTTP and other standards. I find that it's very difficult for anyone to learn web development without at least understanding a little bit about HTTP first. Only once you understand how all web development is the same, can you evaluate the ways that different languages do the job of writing HTTP servers.

camus2 10y ago

> Go makes programming simple Go is simple for simple tasks that fit Go type system, and yes the single formatting standard and the linting helps with readability. Go is a pain in the ass for complex tasks that don't fit go type system, like de-serializing polymorphic data or working with XML. But at the end of the day, the lack of polymorphism in the language makes complex things way more complex than they should be. Finally, Go relies way to much on runtime behavior for a statically typed language.

why-el 10y ago
These are quite unsubstantiated claims. Go is used in many a non-trivial program, such as Kubernetes, Docker, Google internal projects, and so on, and the one denominator among these is the plethora of data formats they need to work with.
- PopsiclePete 10y ago
  His claim isn't necessarily wrong, and neither is yours. I find dynamically-typed languages easier to work with when dealing with (de)serialization, it's just that Go isn't too horrible at that to warrant abandoning it and losing out on its other niceties in favor of a different stack. I mean, everything sucks at something, and Go's type-system isn't....great....but it's "good enough" to where you just kind of curl your lips in slight disapproval sometimes instead of tearing your hair out.

xiaoma 10y ago

> "I agree that Go makes programming simple, in a matter of less than 6months, I learned how to write a webapp in Go just by using the standard library" I've met non-technical people who were able to make a webapp in PHP after 6 days with just the standard library and the O'Reilly Head First book.

2_listerine_pls 10y ago

6 months? that's a lot of time.

thewhitetulip 10y ago
It isn't if you add learning web dev from scratch. I had never ever worked with webdev before
- chickenfries 10y ago
  So then you have nothing to compare it to, and you can't say that Go made things simpler or faster than if you had started making web apps in say, python.
  - deleted 10y ago
    [deleted]
  - thewhitetulip 10y ago
    I had tried my hand with Django and flask, just read the tutorials, and for 6-7 months, I was still reading tutorials, and every 6 months a new version of framework would come up, and I'd be upgrading stuff. I would write views without understanding what they really mean. Maybe I learned Python webdev in a wrong way, so, compared to that, Gonwas a cakewalk.
    - chickenfries 10y ago
      So you don't think the background knowledge you gained about web dev in 6-7 months of studying python helped you pick it up faster in Go? > for 6-7 months, I was still reading tutorials, and every 6 months a new version of framework would come up So, according to you, the invention of ONE new python framework caused you to rewrite everything you had been working on? What frameworks did you switch between? Why? Golang is a popular language now, and there are going to be frameworks coming out all the time. There are already lots of Golang webdev frameworks. Imagine if you were starting with Go now, and you learned something like Revel (https://revel.github.io/ https://revel.github.io/) before learning how to make web apps with the standard library. Or imagine you spent 6 months learning a framework and then decided to jump to a new one when another one came out. Also, from perusing the introduction to your Golang book, it seems like you were lacking knowledge of HTTP and other standards. I find that it's very difficult for anyone to learn web development without at least understanding a little bit about HTTP first. Only once you understand how all web development is the same, can you evaluate the ways that different languages do the job of writing HTTP servers.