5 ms·

Go developer experience: * install the newest compiler * clone the code * go build Python developer experience: - clone the code - setup virtual env (otherwise

Go developer experience: * install the newest compiler * clone the code * go build Python developer experience: - clone the code - setup virtual env (otherwise you will break your system) - install very specific version of interpreter because lib x supports only Python from 2020, because Python breaks compatibility in minor versions - no, you can't just update lib x withut updating python and other deps - install deps (hopefully author of the code pinned everyting, otherwise you're fucked) - never update any deps or you will suffer

throwaway894345 3y ago
> Go developer experience: * install the newest compiler * clone the code * go build HN screwed up your formatting, FYI.
- TeddyDD 3y ago
  I'm clueless when it comes to HN formatting ¯\_(ツ)_/¯
  - dcow 3y ago
    use extra new lines liberally (when in doubt, add a newline) is good working advice
gen220 3y ago
As somebody who writes a lot of python, I'm going to quibble, but your statement isn't unfair. :) My quibble would be "don't use lib x". 99% of the time, you don't need an unsupported 3rd party library from 2020. In the worst case, you can copy the subset of lib x that you actually need, the copied code will typically just work, verbatim, in a later python version. In summary, the "common" path travelled by footgun-aware python programmers is not this bad. But yeah, it'd be nice if the language constraints meant you couldn't end up in a situation like this, and it'd be nice if we didn't have to learn-by-footgun as much in the python community. TBF, Python is just an old language that comes with early-mover advantages and disadvantages. Like an old house, we have just learned to live with (i.e. avoid) certain floorboards.
vlowther 3y ago
Why the extra "clone the code" step in the Go developer experience? Been using Go since 1.0, never had to do that.
- TeddyDD 3y ago
  Let's say I described steps to hack on some Go package. When installing libs/programs, go get/install is enough :)

throwaway894345 3y ago

> Go developer experience: * install the newest compiler * clone the code * go build HN screwed up your formatting, FYI.

TeddyDD 3y ago
I'm clueless when it comes to HN formatting ¯\_(ツ)_/¯
- dcow 3y ago
  use extra new lines liberally (when in doubt, add a newline) is good working advice

gen220 3y ago

As somebody who writes a lot of python, I'm going to quibble, but your statement isn't unfair. :) My quibble would be "don't use lib x". 99% of the time, you don't need an unsupported 3rd party library from 2020. In the worst case, you can copy the subset of lib x that you actually need, the copied code will typically just work, verbatim, in a later python version. In summary, the "common" path travelled by footgun-aware python programmers is not this bad. But yeah, it'd be nice if the language constraints meant you couldn't end up in a situation like this, and it'd be nice if we didn't have to learn-by-footgun as much in the python community. TBF, Python is just an old language that comes with early-mover advantages and disadvantages. Like an old house, we have just learned to live with (i.e. avoid) certain floorboards.

vlowther 3y ago

Why the extra "clone the code" step in the Go developer experience? Been using Go since 1.0, never had to do that.

TeddyDD 3y ago
Let's say I described steps to hack on some Go package. When installing libs/programs, go get/install is enough :)