Signal feed
Post
Remote status
Context
1who has a better philosophy when it comes to software engineering?
Replies
11@scathach @genmaicha i have never really missed enums, consts of a bespoke type usually suffice. go is garbage collected c more than anything else.
what makes go good is having a rather sane ecosystem. the compiler is sane, cross-compiling (pure go) works out of the box, the module system with no central repository but checksums is how it should be everywhere.
it's not 100%, but a very good 80% language, especially for the things it was designed for.
gcc-go needs more love though.
@scathach @genmaicha i think i ignored D because of being quasi-closed-source for such a long time.
@scathach @genmaicha no, but i'm not going to learn another language for this problem-space. actually i like go because i can fit it in my brain and understand code if you wake me up at 3am. i'm not all that smart, after all :)
i think that all the features most languages now have are detrimental. i've seen so many bad "clever" constructs in other languages, it's nice of there isn't much wiggle room for this (even if there is much bad go code around now by people using it like java).
@scathach @genmaicha so, i'll certainly take the verbosity of go over something using only a third of lines but with crazy syntax and semantics. especially if i have to deal with other peoples code.
interestingly, this mainly depends on the size of the core language. i find it relatively easy to understand the very boiled down lisp-like languages pretty well. even if you can do meta-programming with them, in the end everything is just a function call, not something special.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
