New style to help readers identify the best libs or fw about awesome-dotnet-core HOT 7 CLOSED

If this is used I think its way easier to use something like https://shields.io/#/examples/social

But I think the discussion should be about what the best metrics are. Do people really star/fork repos they think are awesome? In my case, the answer is no...

from awesome-dotnet-core.

They should be cached after the first request (on Shield.io's end) - as they use Cloudflare. It's still not awesome, but at least it doesn't hit some home-grown server setup.

Personally. This setup would annoy me a lot. I like the simplistic nature of the list, and I expect that all projects on the list are "awesome", in a sense that I don't need to evaluate if one project is "better" than another in terms of stars.

If it really must be, I would suggest a lighter layout, where (markdown permitting) the metrics are printed after the description. Like this:

• autorest - Swagger (OpenAPI) Specification code generator featuring C# and Razor templates. Supports C#, Java, Node.js, TypeScript, Python and Ruby. 4.5.x or above -- 424 forks | 2.109 stars | 964 watchers

The new metrics should be as small and non-intruding as possible.

from awesome-dotnet-core.

I think we can do that but does it really need for the repo ?

from awesome-dotnet-core.

Shields.io appears to provide an easy solution. All metrics are imperfect. In the spirit of release-early, release-often I've hacked a bash-based command line to run at the root directory of the repository:

 TEMPLATE=$(
     for FACET in github/forks github/stars github/watchers
     do echo -n "![\1 $FACET](https://img.shields.io/${FACET}/\3.svg) "
     done
         )
 echo "$TEMPLATE"
 [[ -e README.md.orig ]] || cp -v README.md README.md.orig 
 sed < README.md.orig "s|\[\([^]]*\)\](\([^)]*//github.com/\)\([^()]*\))|${TEMPLATE}[\1](\2\3)|g" >README.md

It prefixes any link to a github repository with shields badges. Thus, it turns:

* [autorest](https://github.com/Azure/autorest) - Swagger (OpenAPI) Specification code generator featuring C# and Razor templates. Supports C#, Java, Node.js, TypeScript, Python and Ruby. `4.5.x or above`

into

* ![autorest github/forks](https://img.shields.io/github/forks/Azure/autorest.svg) ![autorest github/stars](https://img.shields.io/github/stars/Azure/autorest.svg) ![autorest github/watchers](https://img.shields.io/github/watchers/Azure/autorest.svg) [autorest](https://github.com/Azure/autorest) - Swagger (OpenAPI) Specification code generator featuring C# and Razor templates. Supports C#, Java, Node.js, TypeScript, Python and Ruby. `4.5.x or above`

which yields, before:

• autorest - Swagger (OpenAPI) Specification code generator featuring C# and Razor templates. Supports C#, Java, Node.js, TypeScript, Python and Ruby. 4.5.x or above

after:

• autorest - Swagger (OpenAPI) Specification code generator featuring C# and Razor templates. Supports C#, Java, Node.js, TypeScript, Python and Ruby. 4.5.x or above

Still not sure if it's a good idea, because current README.md causes 1767 requests to img.shields.io.

from awesome-dotnet-core.

A flatter style and a bit of coloring makes it less intrusive. Still I agree with @LordMike

• autorest - Swagger (OpenAPI) Specification code generator featuring C# and Razor templates. Supports C#, Java, Node.js, TypeScript, Python and Ruby. 4.5.x or above

from awesome-dotnet-core.

In all the examples here, the line height is doubled. :/
Below are some styles from Shields.io.

flat:

• - Swagger (OpenAPI) Specification code generator featuring C# and Razor templates. Supports C#, Java, Node.js, TypeScript, Python and Ruby. 4.5.x or above

flat-square:

• - Swagger (OpenAPI) Specification code generator featuring C# and Razor templates. Supports C#, Java, Node.js, TypeScript, Python and Ruby. 4.5.x or above

plastic:

• - Swagger (OpenAPI) Specification code generator featuring C# and Razor templates. Supports C#, Java, Node.js, TypeScript, Python and Ruby. 4.5.x or above

from awesome-dotnet-core.

After a long time to investigate, I come up with not changing the current style of readme because of performance when we did a lot of requests to calculate and pull statistic. Keep it for now. Thank you all for your enthusiasm for making this repo more and more popularly.

from awesome-dotnet-core.