@opsnlops Hah. Yes. I first had to learn to use pointers when programming in PL/I in 1973. Looking back on it, I'm surprised it took me so long to "get it", given that I was already an inveterate machine language programmer.
Despite programming for five years, what I lacked was a good understanding of how useful they are and the fast-executing structures you can make using them. A bit more learning and I became a huge fan, which then influenced my machine language programming.
These days I'm learning golang and am feeling a bit hemmed in by the lack of pointers. On the other hand, I understand the need for safe programming languages, which will surely become mandated as time goes on. Pointers are powerful and fast, but dangerous unless you know what you're doing.
@opsnlops Yes, I like it. It took me a while to get my head around the mindset behind the language. It looks like C, but it's really different.
Now I have the right attitude about anything new. "What weird way does golang do this?" That's not a criticism because there are good reasons for why. You just have to learn what they are.
I'm still nervous about the lack of pointers, though. There are so many cool tricks I know that use pointers, I'll have to learn new tricks. Sigh.
@shuttersparks I work for a golang shop. It's a nice language, even if I feel hamstrung at times.
I thought about using it for this project (TinyGO is a thing, and there's gobot.io), but I didn't want to make things even harder on myself. I have enough to learn. :)