Re: Future directions for C# and Visual Basic
@bcooley:>"i don't know anything about the internal politics of MS, but I actually do think that the internal teams would probably have preferred to use C# for both Windows components and...
View ArticleRe: Future directions for C# and Visual Basic
@niall:> While the lack of generic support for numeric types isn't a great thing, this is definitely not a performance issue.Agreed. It's a nasty papercut. But issues like these really do put off...
View ArticleRe: Future directions for C# and Visual Basic
@Jedrek:4 hours ago.net has one fundamental problem: MSIL.I think that original design of .net was based on Java. JRE runs on multiple platforms so there is a need for some intermediate layer. However...
View ArticleRe: Future directions for C# and Visual Basic
.net has one fundamental problem: MSIL.I think that original design of .net was based on Java. JRE runs on multiple platforms so there is a need for some intermediate layer. However .net runs only on...
View ArticleRe: Future directions for C# and Visual Basic
The async functionality in C# 5.0 and VB 11.0 look really nice. The only thing that really disappoints me is that it completely ignores IObservable<T> which is a shame as it appears that it...
View ArticleRe: Future directions for C# and Visual Basic
5 hours agoIf you want to make a high-performance numeric library, you'll often need to use the basic characteristics of the data type. [...] For performance, you need to use type-specific algorithms...
View ArticleRe: Future directions for C# and Visual Basic
@bcooley:Whoops, while I was composing my message you edited yours, so my answer looks a bit messy (I can't edit).posted by niall
View ArticleRe: Future directions for C# and Visual Basic
@bcooley>“There are many cases where how memory is managed for large mutable datasets gives native code a very wide margin of performance advantage.”I am aware of some of these cases, they can...
View ArticleRe: Future directions for C# and Visual Basic
I'll also point out that the above list looks very different for Mono, proving that "it didn't have to be this way".posted by bcooley
View ArticleRe: Future directions for C# and Visual Basic
Here is a comparison of iOS/Objective C and .NET in terms of what Objective-C supports that .NET does not that makes it work for Apple -> in the primary dev language role -- the role that .NET has...
View ArticleRe: Future directions for C# and Visual Basic
"Yep, with a lot of work, that few percent performance overhead C# currently has over C++ could have been almost completely removed. They chose to improve other areas that they considered more...
View ArticleRe: Future directions for C# and Visual Basic
It indeed looks like the development of C#/VB has slowed down since they began working on Roslyn, but it makes sense. They obviously can't finish a much more sophisticated compiler than the one they...
View ArticleRe: Future directions for C# and Visual Basic
@bcooley:“There's really so much that could be done to improve managed performance.”Yep, with a lot of work, that few percent performance overhead C# currently has over C++ could have been almost...
View ArticleRe: Future directions for C# and Visual Basic
Is the demo source code available? Thanks.posted by Nick
View ArticleRe: Future directions for C# and Visual Basic
There is famous quote by Otto von Bismarck "88 Professoren, Vaterland, du bist verloren" (i.e. "88 professors: Fatherland, you are lost":) ).I see that at Microsoft there are a lot of people from the...
View ArticleRe: Future directions for C# and Visual Basic
+5 Roslyn ProjectPaste As Visual Basic and Paste As C# SWEET!@LINQPad Lovers: This should allow us to have Intellisense for VB.NETLINQPad UserVoice AutoComplete for VB.NETposted by Airn5475
View ArticleRe: Future directions for C# and Visual Basic
There is nothing new! You can already use this "compiler as a service" feature byMicrosoft.CSharp.CSharpCodeProvider CreateCompiler method.I really don't understand MS why they force HTML, JavaScript,...
View ArticleRe: Future directions for C# and Visual Basic
If Anders talks, smart people listen. He's always over-the-top. He's a hero since Delphi - a strong advocate for developers and business productivity. The only concern is that the lead soldier is...
View ArticleRe: Future directions for C# and Visual Basic
Will the MetroMovieFinder applications be available for download?posted by Chuck
View ArticleRe: Future directions for C# and Visual Basic
Comment removed at user's request.posted by Deactivated User
View Article