Conversation

Lucy [hiatus era] 𒌋𒁯

i really like go
2
0
2

@lucy is it a nice language to work with?

1
0
0
@lucy I love Go's standard library, concurrency, and tooling, I just wish the language weren't completely retarded
1
0
1
@Erpel very yes. for backend and actually frontend as well.
1
0
0
@scathach the only retarded thing is it complains about unused variables and imports, also "go get".. but as far as languages reinventing package managers go it's far better than any of the usual suspects
2
0
2

@lucy if I ever get the time again, maybe I will take a look, but the nmx has a lot of stuff to do…

Or I make it a trainee project to develop a self learning course for it neocat_think_anime

0
0
1
@lucy The type system manages to be even more retarded than C
1
0
1
@scathach what? nah. it's like if C had a good type system.
1
0
0

Lucy [hiatus era] 𒌋𒁯

@Johann150 the programming language
0
0
0
@lucy No sum types, even C has enums and unions ffs
1
0
1
@scathach unions are terrible you haven't seen the horrors i had to witness lainstress
go has enums, every custom type can be used as such, it works just like in C they just didn't use a keyword for it.
1
0
1
@lucy My understanding is it's not enforced by the type system though

C unions are ick but actual tagged unions is by far the best way to do polymorphism imo
1
0
0
@scathach create an enum in C and assing any other integer value in range, without that value having a name in the enum :3 it works. because enums are a spook.

i don't like polymorphism but i acknowledge that point
0
0
2
@phnt @scathach you can either deal with it, forward the error or even better: erros.Wrap it and deal with it later without losing context
1
0
1

@phnt @scathach also in general i like this bettern more:

if foo, err := bar(); err!=nil {
  // failed, deal with err
} else {
  // succeeded, use foo
}
0
0
1