If you're learning to write code in 2024, learn Go. That's all you'll ever need. You could try another language like Rust once you get good at Go but Go is so good that you don't need anything else.

Reply to this note

Please Login to reply.

Discussion

Go < Python

I hope this is sarcasm otherwise this is the biggest L take of 2024.

I am a Rust maxi. Go is the inferior systems language. If ibkust prototype, I reach for Python or Typescript. Go is basically Google's C#.

People don't like Go because it's incredibly stupid and has no features. That's exactly the point of Go.

Go is fast, type safe, compiles to a binary, is dumb and simple.

I would never build a game or native app in Go. It’s too dumb of a language and it has a GC which is a no-go when it comes to performance.

Go has a GC but I think it's the fastest of all GC languages and having a GC doesn't matter for most stuff.

When it comes to game dev or app dev, people have always used other languages. That isn't really my point here.

one of go's main inventors, Rob Pike, devised a language called Newsqueak, which had the subtitle "a language for mice"

it was written specifically for user input and GUIs

it is this feature that makes it so good for handling highly dynamic loads on networks, and once you learn to use concurrency, you feel like a disabled person trying to work with shitty single threaded, and parallel processing languages

the cases where you need the things that Go doesn't do well are very uncommon cases, and the go runtime has got so good that it nearly beat a java bulk text file processing algorithm recently

it is only google who have spent zero on marketing go because it is so popular already, and does what they need it for - fast, scalable network server systems

and i am ashamed of you nostr devs who don't get it why fiatjaf's reference implementations were in Go

go is like bitcoin

once you go, you can't go back

We have a Go maxi. Lfg!

dumb, like a razor blade and a sledgehammer

useful for their purpose

but i promise you once you have become familiar with using concurrent processes to implement algorithms it wlil be hard for you to go back

for whatever reason, the rest of language universe hasn't cottoned on to concurrency

you will, and you will become one of us