🔗 A love letter to Golang

I've been writing Go for some time now, close to 7 years. But it wasn't where I originally started out in my tech career.

My first job was at a place where their core competency where backend and databases. Bootstrap, the defacto fronted library for multiple years at the time, was something completely new to them.

UI/UX was mostly an afterthought but since the clients were large accounting companies, it didn't matter. The clients were happy with the colour blue and lots square of boxes.

I also don't have a traditional background in computer science and have been self-taught all the way which probably was also why I ended up in frontend to begin with. It was the safer place to put me.

So I started learning the same way I do for everything else, typing "how to learn frontend" into Google.

React was just breaking away, in terms of popularity, from Angular at the time and was still in the good 'ol pre hook days. I eventually became proficient with React and would mainly write it (and JS/TS) for the next couple of years.

But, something kept happening. Everything seemed consistently out of date as new tools/libraries/frameworks were being shipped every day that you just had to use and keep up with.

As React grew, which it did immensely over the last ~10 years, they seem to think that every requirement known to man must be covered. The move away from classes and redux to functional components and hooks felt awesome, in the beginning. Now you need a PhD to efficiently use them and either manage a large state object being passed around or an alarming number of useState in each component.

I, thankfully, don't write much React anymore and have gone back to the roots: plain old HTML which. And thanks some guy from Montana I still get 90% of the interactivity you get with a SPA app.

So, let me explain why I think you should use Go and why I fell in love with it.

continue reading on mortenvistisen.com

⚠️ This post links to an external website. ⚠️