4 ms·

6 months? that's a lot of time.

by 2_listerine_pls 10y ago

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.
      - thewhitetulip 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? No, the thing is, while I was studying Django, I wasn't learning how to write webapps, I was learning the framework. As I said earlier, I might have gone in the wrong way to learn. I didn't find a book which taught me what I wanted to learn, they all either were too abstract or taught a framework, thus, I started to write my guide, which assumes no background knowledge. > the invention of ONE new python framework Did I say that? >Imagine if you were starting with Go now, and you learned something like Revel The whole point behind my tutorial was to teach newcomers how to write webapps without using a framework. > Also, from perusing the introduction to your Golang book, it seems like you were lacking knowledge of HTTP and other standards I don't claim to know each and every aspect of HTTP and other standards, my book was about the journey I had while learning webdev and Go without using a framework, everyday there are new programmers trying to write webservers in Go, and I felt that there was a need of a book which taught by example. > 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. True, with Go, it was no hassle to write webapps because Go has built in http library and it is a compiled language, thus my shift from Django to Go.
        chickenfries 10y ago
        > Did I say that? No, not exactly, but you complained that "for 6-7 months, I was still reading tutorials, and every 6 months a new version of framework would come up," can you explain what you meant by this? You say you were learning Django, why did you not stick with that? What new frameworks came out that made you stop learning Django? > True, with Go, it was no hassle to write webapps because Go has built in http library and it is a compiled language, thus my shift from Django to Go. See, these are the kind of statements I take issue with. interpreted languages are incredibly popular in web development because of how much easier they are to get started with than compiled languages. Not that I think AOT compilation makes a language bad for web development, but you seem to be asserting that Go is better for web dev and easier to learn because it is compiled and has a built in http library (python has one too! (https://docs.python.org/2/library/httplib.html https://docs.python.org/2/library/httplib.html) and if it's too low level for you, the documentation even points you to the open source requests library, which is the standard in the python community). > As I said earlier, I might have gone in the wrong way to learn. Yes, this is the point I'm trying to make. You're comparing apples to oranges when you say that Go makes web development easy to pick up compared to Python when you didn't really try to learn web development in Python, you tried to learn a high level framework without knowing anything about HTTP, a recipe for disaster in Python OR Golang (the point I was trying to make by referencing Revel).
Strom 10y ago
6 months isn't anything. I've been programming in Go professionally for over 6 years and I still learn new things on a regular basis. There's a great essay by Peter Norvig on this subject called Teach Yourself Programming in Ten Years. http://norvig.com/21-days.html http://norvig.com/21-days.html

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.
    - thewhitetulip 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? No, the thing is, while I was studying Django, I wasn't learning how to write webapps, I was learning the framework. As I said earlier, I might have gone in the wrong way to learn. I didn't find a book which taught me what I wanted to learn, they all either were too abstract or taught a framework, thus, I started to write my guide, which assumes no background knowledge. > the invention of ONE new python framework Did I say that? >Imagine if you were starting with Go now, and you learned something like Revel The whole point behind my tutorial was to teach newcomers how to write webapps without using a framework. > Also, from perusing the introduction to your Golang book, it seems like you were lacking knowledge of HTTP and other standards I don't claim to know each and every aspect of HTTP and other standards, my book was about the journey I had while learning webdev and Go without using a framework, everyday there are new programmers trying to write webservers in Go, and I felt that there was a need of a book which taught by example. > 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. True, with Go, it was no hassle to write webapps because Go has built in http library and it is a compiled language, thus my shift from Django to Go.
      - chickenfries 10y ago
        > Did I say that? No, not exactly, but you complained that "for 6-7 months, I was still reading tutorials, and every 6 months a new version of framework would come up," can you explain what you meant by this? You say you were learning Django, why did you not stick with that? What new frameworks came out that made you stop learning Django? > True, with Go, it was no hassle to write webapps because Go has built in http library and it is a compiled language, thus my shift from Django to Go. See, these are the kind of statements I take issue with. interpreted languages are incredibly popular in web development because of how much easier they are to get started with than compiled languages. Not that I think AOT compilation makes a language bad for web development, but you seem to be asserting that Go is better for web dev and easier to learn because it is compiled and has a built in http library (python has one too! (https://docs.python.org/2/library/httplib.html https://docs.python.org/2/library/httplib.html) and if it's too low level for you, the documentation even points you to the open source requests library, which is the standard in the python community). > As I said earlier, I might have gone in the wrong way to learn. Yes, this is the point I'm trying to make. You're comparing apples to oranges when you say that Go makes web development easy to pick up compared to Python when you didn't really try to learn web development in Python, you tried to learn a high level framework without knowing anything about HTTP, a recipe for disaster in Python OR Golang (the point I was trying to make by referencing Revel).

Strom 10y ago

6 months isn't anything. I've been programming in Go professionally for over 6 years and I still learn new things on a regular basis. There's a great essay by Peter Norvig on this subject called Teach Yourself Programming in Ten Years. http://norvig.com/21-days.html http://norvig.com/21-days.html