3 ms·

With Go, you never spend hours/days debugging broken builds due to poorly documented gradle plugins. As an example :) You really, truly, just run.

pjmlp 3y ago
That is the problem right there, using Gradle without having learned why no one uses Ant any longer. As for Go, good luck doing just run when a code repo breaks all those URL hardcoded in source code.
- philosopher1234 3y ago
  That’s not a real issue: * the go module proxy ensures repos are never deleted, so everything continues to work * changing to a new dep is as easy as either a replace directive or just find and replace the old url
  - pjmlp 3y ago
    It requires work to keep things working, exactly the same thing.
    - philosopher1234 3y ago
      The module proxy is used by default and requires no work. I don’t think what you’re saying makes much sense.
      - pjmlp 3y ago
        So there is some magic pixie dust that will fix url relocations for the metadata used by the proxy, without having anyone touch its configuration?
        philosopher1234 3y ago
        I think I’m missing something, because I’m pretty sure you understand the go module proxy (having seen you around here before) but I really don’t understand what problem you’re talking about. If a module author deletes or relocates their module, the old module is not deleted or renamed from the module proxy. It is kept around forever. Code that depends on it to not break does not break. If they relocated and you want to update to the new location, perhaps for bug fixes, then you do have to do a bit extra work (a find and replace, or a module level replace directive) but it’s a rare event and generally a minor effort, in my opinion, so I don’t think this is a significant flaw. For most users most of the time they don’t need to think about this at all.
- badrequest 3y ago
  > good luck doing just run when a code repo breaks all those URL hardcoded in source code You're on a tear in this thread being wrong about how Go works, but I'm really curious what extremely specific series of events you're imagining would have to happen to lead to this outcome. If I use a dependency, it gets saved in the module proxy, I can also vendor it. You would have to, as a maintainer, deliberately try to screw over anybody using your library to accomplish what you describe.
  - pjmlp 3y ago
    Not when one git clones an existing project, only to discover the hardcoded imports are no longer valid. Being a mantainer has nothing to do with some kind of gentlemens code of condut.

pjmlp 3y ago

That is the problem right there, using Gradle without having learned why no one uses Ant any longer. As for Go, good luck doing just run when a code repo breaks all those URL hardcoded in source code.

philosopher1234 3y ago
That’s not a real issue: * the go module proxy ensures repos are never deleted, so everything continues to work * changing to a new dep is as easy as either a replace directive or just find and replace the old url
- pjmlp 3y ago
  It requires work to keep things working, exactly the same thing.
  - philosopher1234 3y ago
    The module proxy is used by default and requires no work. I don’t think what you’re saying makes much sense.
    - pjmlp 3y ago
      So there is some magic pixie dust that will fix url relocations for the metadata used by the proxy, without having anyone touch its configuration?
      - philosopher1234 3y ago
        I think I’m missing something, because I’m pretty sure you understand the go module proxy (having seen you around here before) but I really don’t understand what problem you’re talking about. If a module author deletes or relocates their module, the old module is not deleted or renamed from the module proxy. It is kept around forever. Code that depends on it to not break does not break. If they relocated and you want to update to the new location, perhaps for bug fixes, then you do have to do a bit extra work (a find and replace, or a module level replace directive) but it’s a rare event and generally a minor effort, in my opinion, so I don’t think this is a significant flaw. For most users most of the time they don’t need to think about this at all.
badrequest 3y ago
> good luck doing just run when a code repo breaks all those URL hardcoded in source code You're on a tear in this thread being wrong about how Go works, but I'm really curious what extremely specific series of events you're imagining would have to happen to lead to this outcome. If I use a dependency, it gets saved in the module proxy, I can also vendor it. You would have to, as a maintainer, deliberately try to screw over anybody using your library to accomplish what you describe.
- pjmlp 3y ago
  Not when one git clones an existing project, only to discover the hardcoded imports are no longer valid. Being a mantainer has nothing to do with some kind of gentlemens code of condut.