I’ve written programs in C. I’ve written programs in assembly, for x86 and for microcontrollers. I’ve designed digital logic and programmed it into an FPGA. I’ve built digital logic circuits with transistors.

I’ll still take Go over C any day of the week. If I’m doing embedded, I’ll use TinyGo.

[–] crispy_kilt@feddit.de 1 points 7 months ago (3 children)

Try Rust

[–] AnUnusualRelic@lemmy.world 3 points 7 months ago

Have you tried putting some WD40 on it?

[–] AMDIsOurLord@lemmy.ml 3 points 7 months ago

Not everyone is on the Rust bandwagon

[–] firelizzard@programming.dev 1 points 7 months ago (1 children)

Why? I see no reason to go through the hassle of learning yet another language when Go serves my purposes perfectly and I'm happy with it.

[–] crispy_kilt@feddit.de 1 points 7 months ago (1 children)

Same reason as learning anything. It makes you better at what you do and broadens your horizons.

[–] firelizzard@programming.dev 1 points 7 months ago (1 children)

I’d rather spend my free time doing something I enjoy

[–] crispy_kilt@feddit.de 1 points 7 months ago (1 children)

You don't enjoy learning?

[–] firelizzard@programming.dev 1 points 7 months ago

Programming languages are tools. I couldn't care less about learning a new tool just for the sake of learning. My interest in learning tools is exclusively practical - if they help me do my work better.

I find functional languages interesting, but that's because I find the underlying theory interesting and worth learning for its own sake, not because I actually care about the specific language it's written in. Even then these days I'd rather learn about woodworking (which is currently my main hobby) than a programming paradigm I'm probably never going to use.