> 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

> 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).