Surprisingly, this post made me really appreciate Go. I thought it explored solid design decisions towards simplicity, such as UTF-8 only.
I want off Mr. Golang's Wild Ride (2020)
31–38 of 38 posts
Re: I want off Mr. Golang's Wild Ride (2020)
#32Earlier quoted context omitted.
As a systems developer with 20 years of experience in a variety of languages, I share your general frustration with Go. But I don't agree with any of the changes you suggested in GoFY.
Hey I saw a post you made about dmt and tinnitus. Same thing happened to me a few weeks back so I was researching to see if it gets better. Does it ever get quieter or will I have to hear through a ringing forever???
Interesting. Certainly it doesn't bother me anymore a couple years later, but I don't think it completely went away.
I was still never sure the dmt caused it so I would be interested to hear your story. Maybe email me? dev@doubly.so
Re: I want off Mr. Golang's Wild Ride (2020)
#33> Computers, operating systems, networks are a hot mess. They're barely manageable, even if you know a decent amount about what you're doing.
No, they are not. It is extreme incoming flow of poorly trained workforce with no relevant experience making it so.
You don't need to know a lot about networking if you don't use microservices, but you just cannot build a decent future proof monolithic system with adequate deploy cadence if you have a team of 50 python devs fresh from coding bootcamp.
You can abstract your OS away and actually don't need a file system at all if you follow 12-factor methodology.
I can rant forever about this, but all this boils down to one thing: fundamental and systematic knowledge of CS and software engineering beats any new fancy tech. While again and again investing one's thousands of hours into new languanges and frameworks — one is doomed to just repeating one's mistakes.
Re: I want off Mr. Golang's Wild Ride (2020)
#34Surprisingly, this post made me really appreciate Go. I thought it explored solid design decisions towards simplicity, such as UTF-8 only.
The issue highlighted, at least for UTF-8, is that Go just _assumes_ everything is UTF-8. It makes seemingly no effort to actually _enforce_ UTF-8, leading to silent mistakes like with the file path.
Re: I want off Mr. Golang's Wild Ride (2020)
#35Surprisingly, this post made me really appreciate Go. I thought it explored solid design decisions towards simplicity, such as UTF-8 only.
Yes, that _is_ surprising! The points made by the OP are exactly the opposite. I believe the language itself is redeemable, but it's the implementations of many features that are just so faulty.
To take your example, yes it's great that it makes UTF-8 as the primary encoding for strings, but then the implementation in the core and in the ecosystem completely fails in enforcing or honoring that.
Edit: please see the filename example in the post to see the failure around adhering to UTF-8.
Re: I want off Mr. Golang's Wild Ride (2020)
#36Surprisingly, this post made me really appreciate Go. I thought it explored solid design decisions towards simplicity, such as UTF-8 only.
Yes, that _is_ surprising! The points made by the OP are exactly the opposite. I believe the language itself is redeemable, but it's the implementations of many features that are just so faulty. To take your example, yes it's great that it makes UTF-8 as the primary encoding for strings, but then the implementation in the core and in the ecosystem completely fails in enforcing or honoring that. Edit: please see the f…
[deleted]
Re: I want off Mr. Golang's Wild Ride (2020)
#37Earlier quoted context omitted.
Anecdotal, but I've found rust much easier to grok and become comfortable to work in than I have with Go - partially due to the docs, but largely because of the perceived complexity in explicitly typing and handling of options and results. With rust, I very rarely feel like the code I'm writing might not be correct for a technical reason, whereas with Go, I find myself very often having to think too much about how be…
Isn’t having to check for integer overflows in rust an example of the exact opposite of your example, or is this something that requires extra effort in go as well?
You don't have to check for overflows in rust? It does by default in debug and not in release and has five explicit adding methods for any of the ways it could behave
Re: I want off Mr. Golang's Wild Ride (2020)
#38I have turned this comment into a blog post: https://news.ycombinator.com/item?id=25618264 It is a well written and in-depth look at the rot inside the Golang ecosystem. Make sure to read to the end and notice that the rot started at the core contributors level. Golang's tagline, from their [repository][0], is "Go is an open source programming language that makes it easy to build simple, reliable, and efficient softw…
Are you particularly proud of this GoFY episode? I mean, being all talk and no follow-through is ten-a-penny.