Docs: [New Topic] Current state of development tools

[ShalokShalom]

[Idea] A sheet which shows all the available compilers, runtimes and frameworks including the support for the different languages and platforms, including notation of the licenses, maintainers and blocking issues.

[Edit] So, something like this:

I think this is important to get a simple overview.

[enricosada]

So, you pratically want the link to github projects for each component? there you can see releases, notes, issue open and closed, docs, etc

=> https://github.com/dotnet/core/blob/master/Documentation/core-repos.md

and https://github.com/dotnet/core/blob/master/release-notes/download-archive.md

You can start navigate docs from the readme of https://github.com/dotnet/core

[charlesroddie]

I think this is a good idea. Suggest putting an .md file similar to what you have a screenshot of on your own github where people can submit changes. Here it would require some group to approve it.

[hsorbo]

Its a good mixture of different stuff in that list. Perhaps it would be clearer if you further group them into Runtimes, Compilers, Frameworks etc?

[ShalokShalom]

Perhaps it would be clearer if you further group them into Runtimes, Compilers, Frameworks etc?

Yes, exactly this is my plan. To be honest: I am fresh to this whole infrastructure, so my information is based on a lot of opinions and some kind of half official statements.

This is why I hope for some contributions by deeply involved community members.

Suggest putting an .md file similar to what you have a screenshot of on your own github where people can submit changes. Here it would require some group to approve it.

I like to get it on the official documentation anyway. Currently, this is a .ods and I can port it to something compatible. Is there a template for something?

[BillWagner]

I'm waiting to assign this to a milestone for a couple reasons.

First, this is a great discussion, and I want to coalesce around what information should be in this topic.

Second, do you expect version information here as well? And, if so, to what detail (major version, minor version, build)?

[ShalokShalom]

Well, I think one fundamental question is, how we like to maintain this table.

Which is why I left 'current blockers' and such stuff out for now.
I also like to include links to the roadmap and active communitys.

So a full overview over the complete ecosystem.

To be honest:

This is something important in my sense while I see this as the job of somebody who is deeply involved.

So, two solutions:

a) Somebody maintains all this mutable stuff.
b) This list stays immutable.

Of course is it nice to present the whole thing in a manner that is super helpful.

[ShalokShalom]

@enricosada

I do not see the whole range of available products in Github.
To start with, since they are spread on several repos.

I do not see the current usability state of these products on Github.

I also cant see, which of the other products are working well with specific products.
So .NET Native is running usable on C# while not yet on F#, yes?

How to see this on Github?

[mairaw]

@richlander any thoughts on this?

[ShalokShalom]

I will upload the file for now:

ComparsionSheetMSdevtools.xlsx

[ShalokShalom]

Who feels responsible here?

[ShalokShalom]

See also this: https://stackify.com/net-ecosystem-demystified/

[ShalokShalom]

Why is it impossible to one of the largest companies in the world, to implement such a fundamental thing, while there is even an open source contribution which simply can get adopted?