3 ms·

> Almost on the dot two years since those rewrites happened and nothing (to my knowledge) has broken. We have code in Java that's been running non-stop for two

> Almost on the dot two years since those rewrites happened and nothing (to my knowledge) has broken. We have code in Java that's been running non-stop for two years. Undoubtedly we have .net code that's been running just as long. However, it's possible that switching from .net to .net core incurs costs because they are quite separate projects. We'v been running on .net core. > Writing Swift Yes, Swift is an entirely different story, and it's... a weird story to say the least. > Longest record so far! You haven't lived through switching to the new modules structure then :) That's quite a big breaking change (and poorly executed in my opinion).

deleted 5y ago
[deleted]
hamburglar 5y ago
> You haven't lived through switching to the new modules structure then :) That's quite a big breaking change (and poorly executed in my opinion) Ugh. I was on the other side of this argument until you brought this out. It’s a great point. The actual language is very good at compatibility but the dependency management did go through a big painful change that some internal code bases I work with but do not own still haven’t worked up the motivation to deal with.
- dmitriid 5y ago
  This bit me really hard as I only come into contact with Go occasionally. First, I couldn't understand how GOPATH worked (many years ago :) ), then that changed, and recently (last year) I spent something like three days trying to figure out why some dependency wouldn't fetch (it was because modules). :) For a person who works with a language daily such changes are not as obvious.