I currently have a class called software deployment where we're making web services with golang. My professor is pretty embedded in the industry. When he started with the company he works for he went and converted all their node.js applications to go resulting in a 700% performance increase compared to the node implementations. Given that these were also deployed on AWS this resulted in literally thousands of dollars in compute time saved. That is a huge implication if you're a small company just trying to get your start and rely on cloud services
Nodejs runs JavaScript code in a single thread, which means that your code can only do one task at a time. However, Node. js itself is multithreaded and provides hidden threads through the libuv library, which handles I/O operations like reading files from a disk or network requests.
Oh man!… nowadays we use only typescript for programming. We even have deno project to run typescript directly. That is like nodejs. Performance issues? JS engines do great optimizations and for most applications it is not the issue. In web servers JS cannot achieve the performance of golang, that is true, but that is not required for most projects! And if we talk about performance - you should see c++ frameworks or even rust based. Tired of you, experts, that make such comparisons! There is NO reason to migrate TS project if it works fine. It has types, it performs, the syntax of the language is so much richer, than golang! And that is very ez to work with it. Golang IS beautiful language! I do like start new projects on go, instead of TS, but I would never say TS will not work for usual server. I would instead ask requirements for project, bcs golang is compiled and we can have many metrics better. But if you have simple web app - that is ez to go full stack on TS. Here was my mistake.
I agree for the most part with one exception. If you are running in the cloud of your choice, Go can reduce the number of expensive resources need to run the application/api/internal processes and that can reduce costs. This does have to be offset by the increased expense and development time and may not reach the profitability lever until your application starts to hit the high six or low seven figures which is still not a large site. I personally think that some processes that are processor-bound ( where JS is at a severe disadvantage ) would benefit dramatically from Go. I currently work for a Blockchain startup and some processes are offloaded from Python to Go for that reason. I think your last statement shows some immaturity on your part. As a developer community, I suggest that we refrain from this kind of behavior and criticism and phrase comments in a more constructive manner.
@@jimmymac601 I personally would start project in go. What I do like, that I can run app in a very clean, basic machine. JS needs node/deno to run. My last statement is emotional, I agree. Sorry for that. My fault
@@stanislauyan3204 I would start a new project in Go as well. But TS for both front and backend is a strong case especially when considering easing FE developers into backend dev. No worries on the comment. Happens to all of us.
I thought JavaScript and Typescript are the two main frontend languages? So how can Go, which is for backend, going to replace them? Or do you mean Go is replacing Node.Js which is used for backend? Still a noob programmer so please correct any misunderstandings I have .
@@batu4605 I advise sticking with learning go, its syntax is not as bad as one might believe on a first glance. Look at rust or zig and u will appreciate the simpleness + performance provided by go.
Switching to Java from Golang, because in my org people come from Java background and write go code with Java mindset. Hence our org go code is heavily “javaised”
if you really care for performance there is Rust; if you dont, which in most backend apps its not a priority, TS is better (integrates better with frontend and access to more developers). Either way Go is niche use case
they are migrating from Node.js to Go. not from Javascript. Javascript is the king when it comes to frontend development and mostly people use Javascript for frontend. and there is no chance for Go to take place of Javascript.
How about the obvious? Javascript is a scripting language designed for manipulating the DOM in a browser and not writing servers. This is analogous to "when all you have is a hammer, every problem is a nail".
But doing Go with frontend is shooting yourself in the foot as it's tightly coupled then. I would like to use Go with NuxtJS and why RIP frontend if he is saying using Go instead of Node.Js 🤨
yeah, amount of expressive code that you can write even with typescript or ruby is much more easier than dumbed down golang. Trust me I have used it and don't want to go back, unless the scope is small and isolated.
