Depends on how you learn. Some learn by being around others, social interaction, asking questions and absorbing knowledge. It's clear you fall into the latter category which likes to learn by diving right into the code, so here it is:

.NET CLR Managed Runtime - https://github.com/dotnet/coreclr

.NET Framework - https://github.com/dotnet/corefx

.NET Compiler as a Service ("Roslyn") - https://github.com/dotnet/roslyn

.NET Orleans Actor Framework - https://github.com/dotnet/orleans

Mono Framework - https://github.com/mono/mono

Xamarin iOS, Watch, Mac Bindings and Framework - https://github.com/xamarin/xamarin-macios

Xamarin Android Bindings and Framework - https://github.com/xamarin/xamarin-android

Usually what I look for is a description of the project. I don't know what an "Orleans Actor Framework" is. The GitHub link gives me a README with a description and links to examples. The Gitter link is a bunch of people who already know about the project talking about details of it, which is harder to learn from I think. (Right now there are people comparing it with "SF". Not sure what that is.)

If there were something like Gitter that showed README.md and the chat room and not the code, then yeah, that's probably a better home page.

> Some learn by being around others, social interaction, asking questions and absorbing knowledge. It's clear you fall into the latter category which likes to learn by diving right into the code, so here it is

Props for how you dealt with negative feedback in this thread, and this positive re-frame.

Certainly you'd want to peruse the README before asking questions in a chat?

You seem to be dodging the question. The question is why -you- are linking to gitter.

He answered it, he linked to gitter because he assumed people wanted a social link instead.

He's not dodging the question at all, he answered it directly. He obviously likes gitter and chatting with others.

He's obviously a shill for big chatroom

Presumably, they prefer to learn by talking to people rather than browsing repos.

The .NET community was, until recently, decidedly not-open-source, so the learning workflow of "open the repo, read the readme, browse the code" might be a new thing for them.

Losen up, linking to something may be subjective. If it's not correct, HN mods can change the URL ;)

Perhaps it's not a bad idea for widening the community ( linking to gitter). I'm actually wondering if they ever used jabber, a not-well-known community for chatting about .net

I don't see that response as dodging anything. He did answer the question - he think that chatting is a decent way for newbies to learn.

You or I may not fully agree, but this is subjective. And it's an answer, even if it might not satisfy you!

> Why do you link to gitter when you should actually like to the repos instead ?

Before I clicked the link I imagined it to be some sort of annotated source code thing. (imagine the inline code with yellow "sticky notes" applied)

Turns out it's just an IRC type chat client. Still interesting.