Go's module and vendoring system sure was kind of a rocky transition. It left a lot of older projects in the lurch in terms of adaptability without having to ta

Go's module and vendoring system sure was kind of a rocky transition. It left a lot of older projects in the lurch in terms of adaptability without having to take extra time for reworking a few things, especially if they used some third party system like dep or whatever and just never got updated after, which kind of crunched against the design goals of forward compatibility. I think they just kind of aimed to keep it as simple as possible in line with other design goals of the language and tooling, which is fine for its use case. It would have helped a lot if they had done this from the start, though. I don't really think that Go was intended to be a systems level programming language, I've never used it that way personally. I think of it as specialized towards being an excellent applications level programming language with rich-enough system level interfaces where necessary. People who do stuff like programming a bootable OS in go aren't doing it because they intend to develop it into something everyone will use, it's done more like an exercise.