I used Go once, for a single small project, two years ago. Recently, I was forced to update the single dependency (acme/autocert) in the project due to bugs in it. But Go also had broken backwards compatibility during the last two years, so my project didn't work with the newest version of Go.
My project is a single main.go file. The Go website claimed they wouldn't break compatibility, which is why I tried using Go for the project. Regret.
Wanted to do a 5 minute experiment with an unfamiliar API and was so absolutely and immediately beset by problems with codesigning, library compatibility with multiple architectures, auth tokens, and other environment setup things that I gave up before I even got to the first line of actual code.
Maybe I just got too old. None of this is fun any more.
A change in software over the last decade that I've noticed is the inability for the user to say "No". I maybe first noticed this with iOS updates where the options were to "Install Now" and "Later". Maybe it's just me imagining it but I feel like I experience this more and more where the choices a user has are 1. Do what we want now and 2. Do it later. Even worse is when they use the 'voice' of the user, as if the request comes from your preference like "Remind Me Later"
This paper is intended to continue the debate on the different uses of migration for the long-term preservation of digital materials.
Revel in the marvels of the universe. We are a collective of forward-thinking individuals who strive to better ourselves and our surroundings through constant creation. We express ourselves through music, art, games, and writing. We also put great value in play. A warm welcome to any like-minded people who feel these ideals resonate with them.