Learning Go as a Node.js Developer
nemethgergely.com
Learning Go as a Node.js Developer
1–10 of 82 posts
Re: Learning Go as a Node.js Developer
#2Oh boy, another learning ___ as a ____ developer blog post.
Re: Learning Go as a Node.js Developer
#3Why would this author feel compelled to write an article about this if they're just learning? That asynchronous Go code which is meant to be analogous to the handful of Node lines looks super verbose. Because the author has claimed a lack of expertise, I have no idea if that is actually the correct way to write something like that out...but it certainly doesn't make Go look good.
Re: Learning Go as a Node.js Developer
#4Oh boy, another learning ___ as a ____ developer blog post.
Counterpoint, I wish there were more resources for new languages that assume you already know how to program.
Professional Javascript for Web Developers[1] is a favorite of mine, because it doesn't waste time teaching you to program and teaching you the language. Instead it points out things that will surprise you if you come from C-like languages, and things you need to watch out for.
Now, since I effectively learned to program in C and later C#/Java, ___ for node developers isn't what I'm after, especially if it spends a bunch of time talking about static typing or fixed size arrays and such. But if you're going the opposite way as I did, learning the high level and transitioning to the low level, something like that could be very useful indeed.
[1]: https://www.amazon.com/Professional-JavaScript-Developers-Ni...
Re: Learning Go as a Node.js Developer
#5The biggest difference I see: the author immediately reached for a framework instead of checking out the standard library.
In Node, the standard library is effectively non-existent, so Node devs get trained and acclimatised to dependencies.
In Golang, dependencies are minimised. Everyone tries to stick to the standard library as much as possible. Because the standard library is so good, for most projects this is perfectly reasonable.
I'd say the first thing every Node dev should know when learning Go is that they don't need a dependency manager. If you can't do it with the standard library then you're probably doing it wrong (at least until you've got some experience with the library).
Re: Learning Go as a Node.js Developer
#6So I am trying to move away from NodeJs for my next project and I can't decide between Elixir and Go. Can't decide what to choose, any idea if there is any advantage for a noob to learn one or the other?
Re: Learning Go as a Node.js Developer
#7Oh boy, another learning ___ as a ____ developer blog post.
Counterpoint, I wish there were more resources for new languages that assume you already know how to program. Professional Javascript for Web Developers[1] is a favorite of mine, because it doesn't waste time teaching you to program and teaching you the language. Instead it points out things that will surprise you if you come from C-like languages, and things you need to watch out for. Now, since I effectively learne…
I know it’s not a popular opinion with some, but all code looks like to me anymore is math with whatever symbols the language in question needs to work
For example:
(singleton)
(tu,ple)
def func1(singleton):
def func2(tu,ple):
^ python function declarations
So after 20 yrs of this, I try to keep in mind the math and just look up the bits to wrap it in.
Also, I avoid custom frameworks and all this industry react/angular, or whatever is cool like the plague, by avoiding front end for a while now
But I do consulting which affords me the luxury. Many may not have the flexibility.
I’ve a set of macros in vim to scaffold boiler plate and go from there
Boom, programming in any language
Re: Learning Go as a Node.js Developer
#8Why would this author feel compelled to write an article about this if they're just learning? That asynchronous Go code which is meant to be analogous to the handful of Node lines looks super verbose. Because the author has claimed a lack of expertise, I have no idea if that is actually the correct way to write something like that out...but it certainly doesn't make Go look good.
> Why would this author feel compelled to write an article about this if they're just learning?
Why wouldn't they? They specifically claim lack of expertise, and that sets the expectations for the reader.
The author is just telling their story about learning Go coming from javascript/nodejs. Whether or not you like the book doesn't mean it shouldn't have been written.
Re: Learning Go as a Node.js Developer
#9The biggest difference I see: the author immediately reached for a framework instead of checking out the standard library. In Node, the standard library is effectively non-existent, so Node devs get trained and acclimatised to dependencies. In Golang, dependencies are minimised. Everyone tries to stick to the standard library as much as possible. Because the standard library is so good, for most projects this is perf…
> they don't need a dependency manager.
For not needing a dependency manager, Go sure has developed an amazing number of them!
https://github.com/golang/go/wiki/PackageManagementTools
https://github.com/avelino/awesome-go/blob/master/README.md#...
In fact, Go probably has the most package managers of any language I've ever seen.
Re: Learning Go as a Node.js Developer
#10So I am trying to move away from NodeJs for my next project and I can't decide between Elixir and Go. Can't decide what to choose, any idea if there is any advantage for a noob to learn one or the other?
I’d say it depends on what you want to build (disclaimer: I have written a lot of Go but have only read Elixir source). If full stack monolith, use Elixir because of Phoenix; if microservice arch, use Go with gRPC protobufs for messaging.
IMO, both languages seem to result in very readable source code; and many examples of how to do either exist on GitHub.