StealthyCoder

So these days it seems there are too many choices, and the wrong simplification is being applied. Since everything in the frontend and backend is being consolidated to a singular language/framework to solve the entire issue.

So I see more and more these past months that everything should be done again in the backend. Meaning that there should be no more frontend interactivity.

So this has been the case for many a year now, that everything in JavaScript land or in this day and age, TypeScript land, is targeting the fact that the developer can use one codebase for everything frontend and backend.

You would think this takes place in the early days of computing, but no this takes place in 2023. I needed to share some files to help my brother to launch a new website.

I love thinking back on my childhood and the PCs we had then. The new tech that got released then into our lives that made it feel like we were an instant part of the sci-fi movies and series we were watching. Something about that moment where there was made a distinction between analogue past and digital future felt definitive, surreal and invigorating.

I quite like keeping old things alive, longer than they were meant for maybe, but also repairing things that got broken. For example toys my children play with.

I just wanted to find out if a directory was writable for the user, and it turns out it is quite difficult to get that information in Golang. How difficult could it be?

I was going down an avenue of seeing if we could implement a better and easier caching for Docker registry utilizing Google Firestore.

I was put in charge to write some extra tests in our framework covering our Docker registry endpoints. We created a framework around Locust.