Thanks, I've chosen to go with a long article because most blog posts I've seen talking about Go never go into enough details to really help make a decision.
A software engineer interested in solving real problems, developer productivity & learning languages for fun. Primarily working on Node.js, React & databases. Current Interest: Rustlang
That's true. We mostly find articles which are too short to decide if we can use a tool or not. Also, I would like to know your views on channels as I always see people talk that channels are great. But never saw an article that would demonstrate an example, where we will see What problems does a Channel solve.
I think you can probably go with a series of articles, which I have seen people doing a lot these days in dev,to to solve the issues of big articles. I personally feel that people tend to not read till end if they are too long. That's the reason I advised on the long article.
Oh yea I plan to start a small series of articles, it's just I don't have a common theme for them yet, I'd like to talk about types, references and interfaces, and concurrency patterns
A software engineer interested in solving real problems, developer productivity & learning languages for fun. Primarily working on Node.js, React & databases. Current Interest: Rustlang
I wanted to write something about how similar & different TypeScript & Go were. But it never took off as I didn't go deep into go.
That might be a good starting point that you can try. 👍
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.
Thanks, I've chosen to go with a long article because most blog posts I've seen talking about Go never go into enough details to really help make a decision.
That's true. We mostly find articles which are too short to decide if we can use a tool or not. Also, I would like to know your views on channels as I always see people talk that channels are great. But never saw an article that would demonstrate an example, where we will see What problems does a Channel solve.
I think you can probably go with a series of articles, which I have seen people doing a lot these days in dev,to to solve the issues of big articles. I personally feel that people tend to not read till end if they are too long. That's the reason I advised on the long article.
Oh yea I plan to start a small series of articles, it's just I don't have a common theme for them yet, I'd like to talk about types, references and interfaces, and concurrency patterns
I wanted to write something about how similar & different TypeScript & Go were. But it never took off as I didn't go deep into go.
That might be a good starting point that you can try. 👍