>why is there no native error handling?
>why are there no stack traces?
>why is parsing dates so moronic?
>why can't you remove packages with the package manager?
>why weren't generics a thing until 3 months ago?
>why?
 |
 UFOs Are A Psyop Shirt $21.68 |
|
Why is the mascot so hideous? It's not even cute like the rust crab
The crabs name is ferrous and hes non-binary
>and hes non-binary
no way they actually did that
>they
Thank you for respecting Ferrous' pronouns 🙂
i wasn't referring to the crab, i was referring to the rustsisters. did they actually make the crab non-binary?
also it's ferris
Not only did they do that but also there was another uproar that non binary isn't inclusive to heterosexuals.
So now the crab is whatever you want it to be, OFFICIALLY. To me, Ferris is unabashedly male but the memes do write themselves.
What's the moronic gopher then? I don't see any genitals
>hes non-binary
>he
>non-binary
what did xe/xir mean
Kek I thought it was a joke, wtf
https://rustacean.net/
>Hello, crustaceans.
>I amFerristhe crab, unofficial mascot forRust.
>My pronounsare any--she/he/they/it are all great!
>I’m special, please be patient!
>they actually have the picture of the crab holding the troony flag on there
kek no way, i thought that was a meme too
>problem?
I personally love how stupid the mascot is, makes me laugh and keeps Black folk who only care about shit like a mascot away
cniles made it
because
>you don't need that, because we said so!
>muh simplicity!!!
They said the same about generics in the beginning, I still remember.
Dont care. Probably will use go.
>why is there no native error handling?
so it actually shows you the error info, and works, unlike many other languages
>why are there no stack traces?
there basically are
>why is parsing dates so moronic?
got me there, some moron thought it was a good idea to do what they did
>why can't you remove packages with the package manager?
you can
>why weren't generics a thing until 3 months ago?
because the language is actually thought about and optimized instead of just cramming random shit in constantly making compile times 300000x longer than they should be and causing tons of other issues (like java, c, c++, etc)
>why?
cuz it is ez
well they did cave in and add them so your point is moot
no it isn't, what part of "thought about and optimized instead of cramming random shit in constantly" did you not comprehend? They were working on it for like 8 years.
>why are there no stack traces?
>why is parsing dates so moronic?
>why can't you remove packages with the package manager?
you're lying fricking idiot. why is being a lying fricking idiot such a common thing with people who shitpost about go? it's uncanny, really.
ian lance taylor (the dude who made llvm and gcc so good) worked carefully on go generics for about a decade. the go generics system is formally proved; can your shit say the same? probably not.
Is it a lie that regular error objects don't maintain stack traces?
Is it a lie that Go's format for parsing dates is at the very least unconventional?
hate go
simple as
kek do gophags actually have to do the top one every time they call a function?
Yes.
My team at work mostly works in Java, Scala and python. One of our senior folks wrote a new service in Go and then promptly fricked off to a different team. Now we're stuck with it and all of our team hates go.
Literally half the lines are err checks and IntelliJ code folds them out of the way and it makes me laugh that the language is so shitty that the first thing an IDE does to improve it is hide half the lines in a program because impact readability so much.
Java/etc exception hell might be a bit ugly but at least it mostly stays out of your way and has plenty of info.
Go errors can technically be any type, but you know everyone just fricking passes around and cats strings together, both making the error unstructured (lmao @ string parsing your error to extract e.g. what host you failed to connect to or whatever.). Whereas in most languages with proper exception systems, even junior devs seem to see the value in writing a custom exception type when appropriate, and having it provide structured relevant info about the error.
Filtered. I've seen how sirs write exceptions in Java, atleast the ide folds err != nil, what it doesn't fold however is the 50 BrokerClientAuthorization*Exception.java files you got in src/domain/broker/exceptions after you let minijeet write his "custom" exception class everytime he felt it was necessary
>Go errors can technically be any type
oh good, another lying idiot
>try
>catch
>.then
>.then
>.error
other languages aren't better
Hierarchical exceptions are far better, also exceptions can be more efficient.
no they aren't and no they can't. an error variable can be used in any way (including your homosexual ways), and Go is faster than those shit languages.
>and Go is faster than those shit languages
Now do it using Echo or the standard net library, idiot
res <- someFunction
>why is there no native error handling?
Are you moronic?
Go was designed by delusional boomers for junior developers at Google.
I guess its ok for writing command line programs or something but for serious software you can't be bothered to waste time fricking around with all of Go's quirks and oddities.
>command line
it's built from the ground up for web shit, idiot
And it fails at it spectacularly
it's easily the best language that exists for it other than, arguably, C# which only rivals it. Development in Go is far faster than anything else.
go was designed for go's authors
lying idiot
>I guess its ok for writing command line programs or something
Even for that it sucks hard wiener. CLI programs should be short and sweet, and Go is so inexpressive that you end up with neither. You may as well just use plain C.
Go has a lot of improvements over C. It has GC, closures, array bounds checking, slices, maps, and concurrency with channels.
>why is there no native error handling?
the code itself is native error handling; errors are considered data just like any other. Throwing/catching exceptions isn't the preferred way for everyone, and arguably has more downsides
>why are there no stack traces?
I assume you mean when returning errors, not in case of panic; see previous point. If the error needs to be wrapped to be useful, then wrap it. If you need more insight into your program while it's running, use http/debug/pprof and go tool pprof
>why is parsing dates so moronic?
I don't know what is considered smart here, but I never need to open an external URL to figure out the formatting rules; I just need it to be consistent and nothing else
>why can't you remove packages with the package manager?
the flow is designed to be 1. remove all references from your code 2. run go mod tidy
>why weren't generics a thing until 3 months ago?
they were less of a priority since there were workarounds (code generation); the team is pretty careful about adding features to language that it doesn't absolutely require, but I think they caved to the community pressure. I welcome this change too, even though I very rarely need them
>why?
it's fun, simple, and fast, and it's written in itself - if that's not the biggest flex for a language, I don't know what is
I don't like the fact you have to declare the datatype of every key with struct. In nodejs it's automatic.
What's the point of that?
>why don't they hide errors from me
>why don't they show me where they hide the errors
>why do I not like this aspect
>why can't it assume I'm moronic and can't remove files from a filesystem
>why wasn't this thing, that no actual Go developer wanted and only discussed by idiots who're bashing the language, included.
I hate Go, I want everyone using some form of Scheme, but it's replaced Java and JavaScript in my life and for that I'll always be grateful.
go isnt the best at anything (except maybe concurrency) but its good all around
C++ has all of these but you're too moronic to use it and need to use a language made for morons instead
Go is used by people who larp as hardcore linux hackers, but aren't smart enough to use C/C++, so they have to use Go to satisfy their degenerate urge to only use backwards technology to impress friends they don't have with their hardcore programming tastes and sensibilities.
The language made by google is so edgy and hacker approved. Wow you must be a leet programmer if you write Go programs senpai.
Reminder that google is still mostly using Java over the language they made themselves, and Go is only used by SREs and shit like that
It's also used by people who do know how to use C. Ted Unangst seems to like it, and he authored sensitive OpenBSD code like doas. (He's non-dogmatic about it, which I appreciate. He also dabbles in Rust.)
It's not strange that a language made by Go's creators attracts Unix hardliners. You also get larpers, but larpers gonna larp.
i thought go was the certified wagie language
its full of boilerplate (if err !=nil and repetitive thing you need to do for database queries) which keeps wagies busy and which gives them the illusion that they are working a whole lot because small patches tak ton of lines
>Google uses Borg
>Borg written in C++
>Google wants you to use Kubernetes
>Kubernetes written in Go
Go and Kubernetes are literally just promotional content for Google Cloud. Imagine falling for literal Google propaganda.
>not using stackoverflowception for error handling
why?
>why it gets BTFO by literal troony language
>no native error handling
SIR, why are you making error? Please fix code
I love Go's error handling so much.
Unchecked exceptions is the worst, like a safe GOTO statement.