3 ms·
> you probably didn’t know what you doing using C# Maybe. I was using a NuGet package recommended by the senior dev (that the team was very familiar with) but
by sibit 4y ago
> you probably didn’t know what you doing using C#
Maybe. I was using a NuGet package recommended by the senior dev (that the team was very familiar with) but with Go, I decided to write everything myself.
One could argue it's not a great comparison but I think it is. The main point of comparison was using solutions/languages that the team is familiar with versus exploring something new or different.
> I don’t mean to be rude
No offense take, I don't think I'm better or worse than any other average developer.
- metaltyphoon 4y agoIf u don’t mind, it peaked my curiosity, can you share what Nuget library that is? I want to try a sample data with C# and Go. What version of dotnet were you using? Did you try implementing what you did in C# just like Go?
- sibit 4y agoThe package was called iText on .NET 5. The goal of the project was to read millions of PDFs (something like 9.7 million) and pull some of the text content from every other page. > Did you try implementing what you did in C# just like Go? No, but I'd be willing to be that it would be about the same. In hindsight, I created a strawman argument benefiting Go since I've only used C# occasionally for the last 7(ish) years and I'd never used iText before. Regardless of whether people thought Go was "better" (which wasn't my intention) the team opened up to the idea of looking at other tools/languages. Not long after when we started a new projects people asked questions like "would this be better if we used C++ or Rust"?