31–40 of 94 posts
What's up with the memory consumption of C# .Net Core? It looks like it has dethroned Java as the memory bloat champion. http://benchmarksgame.alioth.debian.org/u64q/csharp.html
However in CoreCLR there are multiple efforts to reduce memory consumption, mostly driven by the ports to other architectures (e.g. ARM, ARM32), see https://github.com/dotnet/coreclr/search?q=memory+consumptio...
Earlier quoted context omitted.
Point taken. We have some improvements to make on this front.
I know you are in the .NET team but we have critical issues with Microsoft (we are MSDN subscribers) that are not addressed. The most critical issue is the impossibility to pass automated tests and sign a network device driver because of a Windows 10 bug! If you can help routing this inside the organization would be great. More info about the issue here: https://social.msdn.microsoft.com/Forums/SharePoint/en-US/b1...
Every time I try to get a quick feel of .NET on Linux, I allocate an hour to it and that hour is always spent wandering around various guides on microsoft.com and never getting anything done. There are terms like .NET Core, .NET Platform, .NET Framework, .NET SDK all mixed up on nearly every page, multiple versions of "Getting started" and "Quick start" guides, massive navigation menus and options on every page so yo…
I gave a talk at the London .NET user group earlier this year on why it's all so hard to understand. Maybe it will help clarify some things, however it was before the 2.0 announcement: https://unop.uk/on-asp-net-core-and-moving-targets/
Every time I try to get a quick feel of .NET on Linux, I allocate an hour to it and that hour is always spent wandering around various guides on microsoft.com and never getting anything done. There are terms like .NET Core, .NET Platform, .NET Framework, .NET SDK all mixed up on nearly every page, multiple versions of "Getting started" and "Quick start" guides, massive navigation menus and options on every page so yo…
Point taken. We have some improvements to make on this front.
Always interesting timing by technology companies. Here's a post to developers by Microsoft the day AFTER Apple's State of the Union presentation to developers. Microsoft touting performance improvements the day after Apple amps up performance on pretty much every aspect of the Apple developers infrastructure (Xcode, Swift, APIs, processor and GPU utilization, etc). Must be a coincidence...
I have no way of knowing for sure, but I doubt a blog post that long, published on an official M/S blog (i.e. probably requiring sign-off) could be written that quickly!
Always interesting timing by technology companies. Here's a post to developers by Microsoft the day AFTER Apple's State of the Union presentation to developers. Microsoft touting performance improvements the day after Apple amps up performance on pretty much every aspect of the Apple developers infrastructure (Xcode, Swift, APIs, processor and GPU utilization, etc). Must be a coincidence...
for (int i = 0; i Shouldn't your compiler completely fold this? There are no side effects, it's single-threaded. This should take microseconds, not 86 milliseconds.
> For example, SortedSet ‘s ctor was originally written in a relatively simple way that didn’t scale well due to (I assume accidentally) employing an O(N^2) algorithm for handling duplicates. Now that's a gross oversight.
> In other cases, operations have been made faster by changing the algorithmic complexity of an operation. It’s often best when writing software to first write a simple implementation, one that’s easily maintained and easily proven correct. However, such implementations often don’t exhibit the best possible performance, and it’s not until a specific scenario comes along that drives a need to improve performance does that happen. For example, SortedSet‘s ctor was originally written in a relatively simple way that didn’t scale well due to (I assume accidentally) employing an O(N^2) algorithm for handling duplicates.
You'll never get anything done if you want to get it perfect the first time round. Or as they say, first make it work, then make it right, then make it fast.
Every time I try to get a quick feel of .NET on Linux, I allocate an hour to it and that hour is always spent wandering around various guides on microsoft.com and never getting anything done. There are terms like .NET Core, .NET Platform, .NET Framework, .NET SDK all mixed up on nearly every page, multiple versions of "Getting started" and "Quick start" guides, massive navigation menus and options on every page so yo…
I see. 4 steps too hard. I bet you're a Go code monkey?
Microsoft keeps getting better. Open sourcing so many things.
C# and Visual Studio is a breath of fresh air compared to the bloated, aging and vexing obfuscation called Java (work in both).
Since 1991 Microsoft Research keeps making contributions.