3 ms·
It's kind of hard for me to mentally square that with the amount/types of publications that exist for it, though of course it makes sense on further thought. W
by solarkraft 4y ago
It's kind of hard for me to mentally square that with the amount/types of publications that exist for it, though of course it makes sense on further thought.
What I mean is that I found it very hard to find "interesting" stuff built with it. You get the official documentation and that's it - for .Net Framework, anyway. Few blog posts about issues and their solutions, cool demonstrations or just general musings. It's like people don't care. And maybe they don't - it's just their job, after all, and they can't wait to go home to their wives and kids rather than think about some technology more than they have to.
As a newcomer (forced through an apprenticeship) who does think about technology more than he has to I found this bewildering and demotivating.
Microsoft seems to have realized this and seems to have put a reasonable amount of effort into building a community around the new .Net and making it seem exciting/interesting rather than something that's just in a really slow death spiral. Oh, and building things that one can easily get excited about. Non-nullable types come to mind.
- diarrhea 4y agoGreat observation. Search results for C# are awful. Full of 2000s style, for-profit, consultancy-selling, lukewarm-quality blogs. None of the high grade stuff enthusiastic users from other ecosystems put out. Not to beat a dead horse, but Rust is a good, contrasting example here. In the case of C#, user generated content is written during work hours. It is a worker’s language. In some other ecosystems, content is written on weekends, by enthusiasts (who might not be employed in that ecosystems as there’s no jobs available…).