@andrzejstachlewski3662
As a Go dev (but also JS/TS guy) it just makes me smile. Waiting for next part.
@calder-ty
Nice video. The times I used Go, it was an fun. There are some... Strangely opinionated design decisions, in my opinion, but I understand that some of that is changing. I also like the way newer languages like Rust and Go are providing a standardized ecosystem of tooling around the language.
@solitary-dude
Being DISGUSTED by TS performance is a wonderful start to the work week.
@jackmonkeyca
I really enjoyed this, being primarily a JS/TS front-end dev with some Go experience in the last few months I fully expected Go to be more performant. I didn't expect the difference to be as big as it was though and I kinda wish you'd delved into why that might be. Hoping to see a part 2
@Ev-xi5xp
Always love Go content! More comparisons and especially Go performance analysis is always great to see.
@kezzu5849
As a self proclaimed TS fan boy, I'll admit that you've convinced me to take a look at Go this weekend.
@rachit-sharma
Rather than making the scenario more complex, I'd like to see if a deno server fares any better. 🤔
@F4T4LFL4W
I would have loved to have seen the results as you scale up on instance size. GO (in general) has a smaller memory footprint and overhead compared to Typescript. Considering the instance size was so low, I would not be surprised if the Typescript application quickly hit the point where it could no longer keep what it needed in memory and had to start allocating/deallocating it's resources, causing a cascading slowdown. I have worked in GO for years and I would 100 percent say it is my favorite language 90 percent of the time; however, GO's loose similarities with C and comparatively sparse built in functionality (what do you mean there is no built in contains?!) still cause it to be seen by some as arcane and unapproachable. This use case does scream in GO's favor as a language designed to underpin Google Cloud where optimizations for cases like these with heave socket traffic etc is high up on priority.
@dd-v
As a full-on JS dev I loved this video. Got me really hyped to learn Go
@jamesvaci7382
every time i watch one of ThePrimeagen videos im like How the hell did it take me this long for find this guy? Quality superb, memes on point and most of all get some edu out of it xD
@jacobstamm
0:48 when your dog has peanut butter on his lips
@bartoszszatkowski1376
Great content Prime! You've inspired me to pick up Vim and continue learning coding. Last month I've got a job as a software developer in Amsterdam (without CS degree)! Thank you for everything!
@kalvinpearce
VERY INTERESTING! I would have assumed this outcome but wouldn't have guessed it was such a bloodbath. Thanks for doing this vid Prime, keen to see the other parts and maybe even more videos like it. Definitely makes me wonder if I should give Go a go for a cheeky rewrite of the work server to see if its viable before release 🤔
@xique9999
JS dev here. Thank you for making the video, it's an interesting way of comparing the performance of both runtimes. I noticed that in your JS server you're using a forEach function to iterate over the array of messages, this is generally considered a lot slower than loping over an array with a regular for loop. I don't think it would make Node outperform Go, but it would improve the performance of the Node quite a lot.
@towhidkhan2358
Holy moly dude.This is my first video here.And I'm never gonna go away from this channel xD
@abuk95
Great comparison! Thanks for taking the time and testing it. Please make the video about database async handling.
@ShakthiMonkey
need this content streamed directly to my brain
@ErmandDurro
This was really nice to watch. Thank you and keep doing a great job with these videos. Love them 😀
@PTM1008
Excited for the next parts! Subscribed! But please also update the description of this video with links to the newer parts.
@ThePrimeagen