Which is better and why?
Go vs JS for backend?
Jason Nelson
Henry Young
Go is faster, JS has an ecosystem.
I'd go JS, it's probably more than fast enough for your use case.
Christian Hernandez
they are the same
Hunter Howard
Golang is better for your (((employer))) but is JS with Typescript is much better for you as a developer
Nathan Ross
php
Luke Howard
It's already a disgrace to have to deal with JS in the frontend, but you have no other choice. Now why in the fuck would you deliberately pick JS for your backend?
Jason Ross
Whenever you have multiple options, pick the option that's not javascript.
Aaron Brooks
Unironically TypeScript
Logan Johnson
What is your usecase?
Cameron James
JS = shit language
TS = shit language with static typing slapped on top
Asher Gray
>for backend?
Can you not read? he's asking which language he should use for server side webshit.
Logan Bailey
how fast do you want to go retard? how many users expected?
small-medium = TS/JS
medium+ = Go
big= .NET Core
Elijah King
techempower.com
PLT in blue = low level sockets
MCR = microframework
FULL = server side rendering and other gud stuff
Cooper Anderson
Node is just a Javascript wrapper around a C++ implementation. It uses callbacks that queue on an single threaded event loop for concurrency.
Go implements everything in Go, uses real multithreading
Carson Hernandez
>uilib?
The fuck?
Never head of those.
Joseph Sanders
>Which is better and why?
Based János. Giving commies hell before it was cool
Joshua Stewart
tldr is its retarded, most brainlets using these frameworks wont check the actual impl, some even alloc full 128gb of server memory, some use pre-calc'd headers, some are raw socket impls, etc, but it gives u a good measurement whats possible if u know what to compare and look at how its implemented
Nicholas Turner
go api backend + javascript frontend
Connor Baker
what a stupid question
go
Josiah Clark
unironic js(ts) endorsement here