Re: Future directions for C# and Visual Basic
It was some time ago but I have definitely managed to write a dynamic code application in C# before however, I don't think it had a nice API and certainly didn't have IntelliSense.I would be interested...
View ArticleRe: Future directions for C# and Visual Basic
nice but saw this "Interactive C#" stuff with F# don syme. But yes, nice stuff.posted by Praveen
View ArticleRe: Future directions for C# and Visual Basic
Funny that Windows Metro won't officially support 3D graphics directly from C#, while Sony is making C# the language of the PlayStation Suite SDK, that'll be available for Android tablets (plus...
View ArticleRe: Future directions for C# and Visual Basic
The Roslyn project is great and I love the Cut/Paste between C#/VB... the .NET languages are finally co-evolving now!posted by mxj1009
View ArticleRe: Future directions for C# and Visual Basic
can we have irec library that can do what html5/javascript do in .net.I hope c#5.0 would fulfill all requirements & dominate over other languages.posted by crnet
View ArticleRe: Future directions for C# and Visual Basic
F*cking aweswome. Finally someone took the Erlang modell and done it right in traditional programming. Thanks Anders, C# really needed it!posted by McHalls
View ArticleRe: Future directions for C# and Visual Basic
Excellent hitech stuff. I believe this CaaS is going to go great heights.posted by VivekRagunathan
View ArticleRe: Future directions for C# and Visual Basic
so could roselyn be used for obfuscating code?posted by mashumafi
View ArticleRe: Future directions for C# and Visual Basic
Got so many apps in vb @ work. Just want to study text trans in notepad with convert thingy. Still got the feeling that the C world is moving to vb, verses the opp.Dim All as PEOPLE.GOODposted by old...
View ArticleRe: Future directions for C# and Visual Basic
This is really awesome. I love Ander's humorous style.posted by liux0229
View ArticleRe: Future directions for C# and Visual Basic
It was a great session, I am very impressed and wrote a summary of Roslyn demo.http://uhs.doorblog.jp/archives/52960107.htmlposted by mozu
View ArticleRe: Future directions for C# and Visual Basic
Hi all,Does anyone know if the netflix example is available online?Cheers!posted by Sam
View ArticleRe: Future directions for C# and Visual Basic
Umm... is there any way to contact Mr. Hejlsberg? :)posted by cont
View ArticleRe: 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 ArticleRe: Future directions for C# and Visual Basic
@Jedrek as @Onur pointed out Mono's compiler is written in C# that makes it cool. What is cooler in Roslyn that it gives you intermediate results such as AST so that you can manipulate it. Mono's...
View ArticleRe: Future directions for C# and Visual Basic
I agree with bcooley. This is not metaprogramming. This is IDE programming. @Andrey REPL is not something difficult to implement@Jedrek they are very similar in deed. Whole Mono compiler is written...
View ArticleRe: Future directions for C# and Visual Basic
Andrey: First presentation of Compiler as a Service comes from PDC 2008 (http://channel9.msdn.com/Blogs/pdc2008/TL16)after that presentation Miguel de Icaza introduced that concept in Mono. There is...
View ArticleRe: Future directions for C# and Visual Basic
I am great fan of MS and their products, but I hate their disgusting manner in which they present "new" features that have been there for a while. Now I am speaking about this Compiler as a Service...
View ArticleRe: Future directions for C# and Visual Basic
What is impressive, MS pythonizes the using of the Console Mode in a better way.posted by scilar
View ArticleRe: Future directions for C# and Visual Basic
So I'm sure Anders considered having the default for async calls be await without having to type the await keyword allowing for a smaller more concise format. I know this would not work for backwards...
View ArticleRe: Future directions for C# and Visual Basic
@rab36: I agree. Microsoft has pulled off unifying it's previously fractured platform again with WinRT, and looks to have positioned itself well into the future. Unfortunately for .NET that...
View ArticleRe: Future directions for C# and Visual Basic
WinRT components looks really interesting.I hope that I will be able to unload WinRT components and update them at runtime. In .net that is not possible at this moment (only by using AppDomain which is...
View ArticleRe: Future directions for C# and Visual Basic
@bcooly: I think that interoperability between managed and native code just made a big leap forward by introducing WinRT components. I just watched a build session where they demoed how to write a...
View ArticleRe: Future directions for C# and Visual Basic
@Novox:Precisely.That, and I suspect that the Core desktop and application (Office) teams also put their collective feet down and insisted that the future platform not sacrifice native level...
View ArticleRe: Future directions for C# and Visual Basic
7 minutes ago,bcooley wroteThis matters because .NET is the primary development platform for mobile devices, and these devices are underpowered relative to the desktop.And I suspect, that's one of the...
View ArticleRe: Future directions for C# and Visual Basic
@McI spent a bit of time hovering over the keyboard before clicking "Comment", even returned a while later to re-read the post, and decided to leave the post as is. It just needed to be said. If you...
View ArticleRe: Future directions for C# and Visual Basic
As a scientist I would like to support "Roslyn". I see a lot of scientific applications of that project. From my point of view it would be nice to have the following features in c#:- maybe it is...
View ArticleRe: Future directions for C# and Visual Basic
Seriously.. C# vNext is going to be nothing more than access to the compiler so that we can build our own refactorings for visual studio?It's not only about refactoring. As I understand it, Roslyn is a...
View ArticleRe: Future directions for C# and Visual Basic
The async stuff was nothing new to people who follow C# 5, but the Roslyn project pretty much blew my mind. The interactive prompt is nice. My favourite part of the demo is the custom refactoring...
View Article