Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
According to StackOverflow Update: 560M Pageviews A Month, 25 Servers, And It's All About Performance (perhaps getting its information from Marco Cecconi The Architecture of Stack Overflow at 29:00),
Some coding is in IL, not C#.
I am not asking about anything specific to Stack Overflow site, but, generally speaking, when would IL-written code be faster than C#-written code?
My understanding, from reading the posts of Eric Lippert, most of the optimizations in .NET are done when JIT'd:
We let the jitter team worry about optimizing the heck out of the code when it is actually spit into machine code; that’s the place where you can get real wins. — What does the optimize switch do?
What sort of optimizations can be made from hand-coded IL?
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Given the fact that I need in specific parts of my projects,
to interop / interact a .net c# code with a code that's within a dll produced by an unmanaged language:
which language other than c\c++ has good compatibility and is as fast or preferably faster?
I have searched and found few ( looks promising) less popular names I couldn't decide on any of them as I have no clue how to if it's possible at all to interact with their dll.
Haskell, Rust, D, Fortran, Nim... and more..
Did you try to implement this approach with any of them?
Use C++/CLI. This give you an bridge with managed and unmanaged in the best performance possible.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I have a question about c# programming language, when a method returns an object, and for example I'm forced to return null, which is not clean code, what is the best practise to handle this? I dont want to return null.
EDIT
This was a question because it started as discussion on a software engineering class after reading Clean Code - Robert C. Martin 's book and it really came to my mind that trying to avoid this added unnecesary complexity to the design.
In case to signal "failed to create object" C++ class constructs throws exceptions for this purpose.
Some languages / projects prefer to use exceptions more to keep happy-pass happier while others may not.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm struggling with WCF over engineering. It seems to me like a strange code layer, that do something useful, like giving you the possibility to call methods over http.
But in other hands, it increases useless code, useless methods calls, and so on.
Its like buying a japanese car, you will pay cheaper, but it will cost you more than you imagined.
Joking aside, I would like to know if I'm missing the real point here, or there is a better solution ?
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
In 2013, Microsoft added new feature to the .NET framework to help handling asynchronous tasks: async/await.
How does this feature affect the readability of the code?
Here are few disadvantages that I found:
It is the same as using return in the middle of the method: it makes it hard to catch the flow of the code.
It reminds of GOTO in C: it makes it hard to catch the flow of the code.
async/await are not easy to understand, but once you get the principle of synchonization context capture/restore, it's relatively easy to follow the code flow.
The main issue with this feature IMO is the async all the way problem, i.e. once you're writing an asynchronous piece of code, all your code tends to become asynchronous too.
I recommend this excellent article on MSDN Magazine for a good understanding of the whole async topic.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
One of my colleagues told me something like that over a year ago. I was wondering if there is something like this available now or will be in the future?
I think it was gonna have a separate GC core, and some memory management thing but I am fuzzy about it.
Any clues?
Some microcontrollers support a Jazelle instruction set which implements part of Java in hardware, it's not .NET but it is managed code and the same could be done for .NETMF.
There's the http://netduino.com/netduino/ that supports the .net micro framework.