I've become rather scared to rely any of the google services and apis, because before you know it, they'll just deprecate things.
I'm use to building systems that should run for years and years without ever being touched, but since using google services, I have to revisit everything quite often.
I also see other comments about Go. I was the first one to get excited when Go was launched to the public. Yes, Go is fast, concurrency and channels are super good. But the rest of the ecosystem including the documentation is pretty bad.
Compared to Python, developing in Go feels like you're walking through glue, you'll get stronger, but it'll take longer.
My day job is designing and developing websites, but in my off time, I like to build all kinds of things, including Ruby gems, iPhone apps, and Alexa skills.
Yes! Documentation is another huge problem with using the "latest and greatest." It might be the best language or tool out there but if you can't learn how to use it or figure out how to solve the basic errors it becomes almost unusable.
I think that good documentation includes examples too. (for everything)
It just makes it so much easier if you can reference the docs, see straight away a piece of code that does what you need, and carry on with the job.
Go documentation is an exercise in figuring out what they meant and how to use the code. But there is hope.
As technologies mature, the documentation does seem get better.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes, yes, and yes.
I've become rather scared to rely any of the google services and apis, because before you know it, they'll just deprecate things.
I'm use to building systems that should run for years and years without ever being touched, but since using google services, I have to revisit everything quite often.
I also see other comments about Go. I was the first one to get excited when Go was launched to the public. Yes, Go is fast, concurrency and channels are super good. But the rest of the ecosystem including the documentation is pretty bad.
Compared to Python, developing in Go feels like you're walking through glue, you'll get stronger, but it'll take longer.
Yes! Documentation is another huge problem with using the "latest and greatest." It might be the best language or tool out there but if you can't learn how to use it or figure out how to solve the basic errors it becomes almost unusable.
I agree 100%
I think that good documentation includes examples too. (for everything)
It just makes it so much easier if you can reference the docs, see straight away a piece of code that does what you need, and carry on with the job.
Go documentation is an exercise in figuring out what they meant and how to use the code. But there is hope.
As technologies mature, the documentation does seem get better.