Re:Oden: experimental, statically-typed functional language,...
by KirinDave on Saturday February 27, 2016 @10:59AM
(#11187427)
> Docker does not make anything crossplatform; it just enables you to package your dependencies such that you can easily run on any other linux-amd64 machine.
Which IS the primary use case for nearly all of Go's interesting use cases. The exceptions are CLIs for API access? But you're going to have some trickiness with testing in these cases that warrant a non-trivial build-test cycle anyways. If that works well for you that's wonderful.
A good packaging of Go with some helper shell commands is also quite nice, for other reasons.
> I've never used a language with an ecosystem that so adamantly abided by one standard format. PEP8 comes somewhat close, but there are still fights over different linters etc...
You say this like it's a good thing. I see only the downsides. I'm not much of a fan of Python's contemptuous ecosystem either.
> The vendor directory introduced in Go 1.6 (and usable in Go 1.5) has addressed the versioning issue with `go get`.
It most assuredly has not addressed this issue. All it's done is decreased the confusing filesystem zigguraut so that a single repo checkin doesn't look patently ridiculous. Pretty important when GitHub is the primary code distribution mechanism.
But so long as the maintainers of Go pretend that everyone will always keep master up to date and never make breaking changes, Go projects are still at a disadvantage compared to every other civilized combiled build+deps tool.
I had high hopes for Go vendoring, but examinations in 1.5 really reinforced to me that the maintainers and designers of Go are interested in the (less compliant) real world issues everyone runs into, don't care about shipping reusable code to a wide audience over a long period of time.
Languages with contempt for programmers as a central tenant often have problems like these.
> Go projects do not decay if you've vendored your dependencies.
Hope you don't have a library with bugs. I sure found many in the libraries I pulled and if I put down a server for a month to work on something else, then tried to grab a security update? It was never not a headache.
> Am I crazy that I prefer having a race detector over a REPL?
I only refer to situations and inanimate objects as crazy. Anything else is disrespectful. You awknolwedge interactive development is necessary but don't want first class support for it. I just don't understand why you wouldn't want to actually have something that could integrate into a real workflow. Sharability is something we already can get with trivial pastebin/gist integration.
Which IS the primary use case for nearly all of Go's interesting use cases. The exceptions are CLIs for API access? But you're going to have some trickiness with testing in these cases that warrant a non-trivial build-test cycle anyways. If that works well for you that's wonderful.
A good packaging of Go with some helper shell commands is also quite nice, for other reasons.
> I've never used a language with an ecosystem that so adamantly abided by one standard format. PEP8 comes somewhat close, but there are still fights over different linters etc...
You say this like it's a good thing. I see only the downsides. I'm not much of a fan of Python's contemptuous ecosystem either.
> The vendor directory introduced in Go 1.6 (and usable in Go 1.5) has addressed the versioning issue with `go get`.
It most assuredly has not addressed this issue. All it's done is decreased the confusing filesystem zigguraut so that a single repo checkin doesn't look patently ridiculous. Pretty important when GitHub is the primary code distribution mechanism.
But so long as the maintainers of Go pretend that everyone will always keep master up to date and never make breaking changes, Go projects are still at a disadvantage compared to every other civilized combiled build+deps tool.
I had high hopes for Go vendoring, but examinations in 1.5 really reinforced to me that the maintainers and designers of Go are interested in the (less compliant) real world issues everyone runs into, don't care about shipping reusable code to a wide audience over a long period of time.
Languages with contempt for programmers as a central tenant often have problems like these.
> Go projects do not decay if you've vendored your dependencies.
Hope you don't have a library with bugs. I sure found many in the libraries I pulled and if I put down a server for a month to work on something else, then tried to grab a security update? It was never not a headache.
> Am I crazy that I prefer having a race detector over a REPL?
I only refer to situations and inanimate objects as crazy. Anything else is disrespectful. You awknolwedge interactive development is necessary but don't want first class support for it. I just don't understand why you wouldn't want to actually have something that could integrate into a real workflow. Sharability is something we already can get with trivial pastebin/gist integration.