Great article! I wish I’d found this article earlier as it could save me so much time poking around golang!
I’ve recently been trying to transfer some work done in js into golang and I’ve found that the major obstacle when it comes to switching between js and golang is on how you model your data.
For example, one of the very common use case is if I wanted to store different data in an array. You can do this very easily in js and even in some other static type language like java thru class inheritance. However, golang doesn’t fully support inheritance, which could drastically impact how we design our data model. Though you might want to add this in as personally felt that this is quite important.
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.
Great article! I wish I’d found this article earlier as it could save me so much time poking around golang!
I’ve recently been trying to transfer some work done in js into golang and I’ve found that the major obstacle when it comes to switching between js and golang is on how you model your data.
For example, one of the very common use case is if I wanted to store different data in an array. You can do this very easily in js and even in some other static type language like java thru class inheritance. However, golang doesn’t fully support inheritance, which could drastically impact how we design our data model. Though you might want to add this in as personally felt that this is quite important.