News for hackers. Stuff that matters.
Re:Performance Improvements in .NET Core by jacques_chester on Wednesday June 07, 2017 @06:25PM (#14510342)
Speaking of names and versions -- while working on Cloud Foundry Buildpacks we frequently turned our brains into pretzels trying to manage what components were versioned how. We even had custom logic to parse a YAML file where we maintained a mapping to keep things straight.

Especially since some components embedded different versions of other components.

I don't know if the situation has improved since I rotated off, but a bog-ordinary semver scheme would've saved a world of pain.

Failing that, a single page with components (SDK? Runtime?) and available version numbers that gets updated.

Because we mostly wound up working what was what from forensic readings of scattered blog posts, Github release and I think comments on Github issues.

In any case, I am sure the team would be glad to give you feedback on their experiences since then -- my email is in my profile if want me to pass anything along.

Re:Performance Improvements in .NET Core by runfaster2000 on Wednesday June 07, 2017 @06:46PM (#14510449)
Re:Performance Improvements in .NET Core by jacques_chester on Wednesday June 07, 2017 @06:51PM (#14510478)
Thankyou! I will ping my colleagues tomorrow.
Re:Performance Improvements in .NET Core by runfaster2000 on Wednesday June 07, 2017 @06:55PM (#14510505)
BTW: Your friends can also contact me -> rlander@ms
Re:Performance Improvements in .NET Core by jacques_chester on Wednesday June 07, 2017 @07:38PM (#14510745)
The thankyous keep rolling. I also remembered I can point you at the Slack instance where they live -- https://slack.cloudfoundry.org/, in the #buildpacks channel.