ta20200202
Born on February 04, 2020•37 Karma
The same is true for other features, like channels and goroutines.
But goroutines? I see much less abuse there. And they're so damn handy.
With generics, reading and reasoning about code becomes [even] more challenging.
Personally for me, at this juncture I'm finding that for new projects I might just as soon spring for Java or maybe even prefer it to Go. For the straightforward mvn-style dependency management, if nothing else.
It's all moot now, though. There's no going back, this puppy is cooked!
However contracting pays well, so I don't care.
You might want to reflect on your reasons for jumping ship because your tooling gained a new feature. Sound's rather irrational to me.
Avoiding updating to a new version of OSX that stabs you in the face is a reasonable thing to do, despite it being a new feature.
- noone is forcing you to use generics in your go programs.
- if you are running outdated OS because you don't like some UX change, you might as well consider changing OS.
Sounds like it's just me.
Yes, the problem is similar. It can be considered worse, because in safe Rust you can do almost everything, but Elm is much more limited.
You can still use regular JavaScript with ports, but it is more complicated. It is something like a WebSocket channel, where the server is the JavaScript code.