A software engineer interested in solving real problems, developer productivity & learning languages for fun. Primarily working on Node.js, React & databases. Current Interest: Rustlang
Loved the Article. The conclusion is true.
I've used typescript for quite sometime & java long ago. So I'm comfortable with typed languages. There should be a nice balance between standards & customisation.
Go takes away the customisation part, so it looks kind of monopoly to people white from other languages where there are multiple ways to do the same thing.
Go targets for eventual consistency than absolute consistency. It's better & easy to onboard developers as you don't need to explain them your entire webpack setup & the bunch of lint rules that you use.
So that's a win for me as someone who talks to lot of onboarding engineers in our organization.
Even as the article is amazingly written, I think anyone who doesn't know about go well, might be little skeptical to complete as it's a big list of things that you've put on. I'm not suggesting to write smaller articles but an article with so much information may not be well understood by people who are new due to amount of technicality involved.
Bookmarking it right away.
Cheers 👍
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.
Loved the Article. The conclusion is true.
I've used typescript for quite sometime & java long ago. So I'm comfortable with typed languages. There should be a nice balance between standards & customisation.
Go takes away the customisation part, so it looks kind of monopoly to people white from other languages where there are multiple ways to do the same thing.
Go targets for eventual consistency than absolute consistency. It's better & easy to onboard developers as you don't need to explain them your entire webpack setup & the bunch of lint rules that you use.
So that's a win for me as someone who talks to lot of onboarding engineers in our organization.
Even as the article is amazingly written, I think anyone who doesn't know about go well, might be little skeptical to complete as it's a big list of things that you've put on. I'm not suggesting to write smaller articles but an article with so much information may not be well understood by people who are new due to amount of technicality involved.
Bookmarking it right away.
Cheers 👍
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. 👍