@yoklmn.bsky.social
c# -> golang. Day 2
1) Don't implement Error() error or String() string otherwise you won't have ability override these functions.
Now I miss c# explicit interface implementations.
2) variable.(Type) syntax is ... (let's be polite) unique.
1) Don't implement Error() error or String() string otherwise you won't have ability override these functions.
Now I miss c# explicit interface implementations.
2) variable.(Type) syntax is ... (let's be polite) unique.
January 22, 2026 at 2:07 AM
c# -> golang. Day 2
1) Don't implement Error() error or String() string otherwise you won't have ability override these functions.
Now I miss c# explicit interface implementations.
2) variable.(Type) syntax is ... (let's be polite) unique.
1) Don't implement Error() error or String() string otherwise you won't have ability override these functions.
Now I miss c# explicit interface implementations.
2) variable.(Type) syntax is ... (let's be polite) unique.
c# -> golang. So far I'm missing `Linq`, sugar like `?.`, `??=` and LanguageExt lib. Simplicity? I see more verbosity than simplicity. .NET seem more mature? Going to revisit as I get along with it.
Ah, yes, default formatting hurts my OCD
Ah, yes, default formatting hurts my OCD
January 19, 2026 at 6:09 PM
c# -> golang. So far I'm missing `Linq`, sugar like `?.`, `??=` and LanguageExt lib. Simplicity? I see more verbosity than simplicity. .NET seem more mature? Going to revisit as I get along with it.
Ah, yes, default formatting hurts my OCD
Ah, yes, default formatting hurts my OCD
кто здесь что куда?
January 12, 2026 at 1:30 AM
кто здесь что куда?