Go is better for the backend

preview_player
Показать описание
In this video, I demonstrate how Golang's strong typing prevents common runtime errors found in JavaScript. We'll compare code examples in both languages, showing how JavaScript’s flexibility can lead to unexpected issues, while Go catches these errors at compile time. Watch to see why I switched to Go for backend development!

#golang #go #javascript #GoVsJavaScript #backend #programming #softwaredevelopment #coding #nodejs #typescript
Рекомендации по теме
Комментарии
Автор

Choose go when your primary concern is concurrency. Otherwise, choose one with better ecosystem for your app

hansay
Автор

Bro, I'm not bad at JavaScript, but I get confused with Express.js and Node.js. Do you think I should ignore them and switch to GoLang?

Salah-YT
Автор

i don't think type safety should be a reason to switch, because even without typescript, jsdoc is production ready for years...
however shooting your self in the foot is definitely still be easier with javascript, regardless of types, due to it being way too flexible...
go can fix it because it is rather strict to how you write your code... therefor you can always get almost same code logic, even if you write code for the same problem weeks apart, and it's good thing...

but until wasm get direct access to DOM, the status quo for JS frontend web dev is not going anywhere... mainly for SEO...

hakim_jazuli
Автор

Go guarantees that everything will work after compilation - say it to null pointer
u even can't know optional or not is the field
I'de prefer go where is cuncurrency is really necessary

snatvb
Автор

Can you share your nvim config in github

nabinsaud
Автор

They’re different tools for different things

oliversaxon
Автор

All is good for Go until you realise that a client needs a VPS of a cloud server. Most of the clients still prefer a shared hosting. 😅

phat
Автор

everything with a decent standard library is better than JavaScript - meaning literally everything

bjarne