←back to thread

261 points david927 | 4 comments | | HN request time: 0s | source

What are you working on? Any new ideas that you're thinking about?
1. dietsche ◴[] No.43174883[source]
https://github.com/hamradiolog-net/adif

i’m learning golang and made this library that parses ham radio ADIF logs. my goal was to match the speed of the golang json parser. i managed to surpass it by about 2x!

i’m currently employed writing c#, but looking for a job elsewhere and golang seemed like a good way to level up :)

replies(1): >>43174965 #
2. neonsunset ◴[] No.43174965[source]
golang is a sidegrade at best, in many ways it's very last century when compared to C#

(even if poorly managed and overbloated enterprise codebases may lead you to believe otherwise, they are quite detached from what modern C# is supposed to look like)

replies(1): >>43175288 #
3. dietsche ◴[] No.43175288[source]
I would tend to agree, and yet there is something intellectually challenging about learning something new! I've been on the c# bandwagon since 2004; assembly and C before that. Go brings back some of that low(er) level feeling :)

I could tell you some horror stories about how my current employer does C#. It is very strange.... can't use var, nuget packages for _every_ class library... and it gets stranger from there on out... unfun!

replies(1): >>43176024 #
4. neonsunset ◴[] No.43176024{3}[source]
Honestly, this is a good argument and it should not even be made here but rather when discussing dire and completely self-inflicted state of affairs that a lot of products written with C# are in. It's not just that "the product you see no reason to rewrite in .NET 8" causes talent attrition. It's that it causes that said talent to leave .NET altogether, despite the fact that for greenfield products it's much better at 85% tasks being usually thrown at Go. It's an unfortunate predicament.