Live data from Hacker News

How Microsoft rewrote its C# compiler in C# and made it open source (2017)

medium.com

131–136 of 136 posts

Re: How Microsoft rewrote its C# compiler in C# and made it open source (2017)

#131
post #111
post #78

Earlier quoted context omitted.

That's not entirely true. launchd was released under a free license, and it was one of the most interesting innovations in software in a long while, for example.

So now copying what Sun, Aix, Tru64 and HP-UX already did is an innovation, I guess it goes with the muster of many Apple "innovations".

You're completely wrong in Sun's case, SMF is nothing like launchd.

Re: How Microsoft rewrote its C# compiler in C# and made it open source (2017)

#132
post #131
post #111

Earlier quoted context omitted.

So now copying what Sun, Aix, Tru64 and HP-UX already did is an innovation, I guess it goes with the muster of many Apple "innovations".

You're completely wrong in Sun's case, SMF is nothing like launchd.

It looks quite similar to me in concept.

Re: How Microsoft rewrote its C# compiler in C# and made it open source (2017)

#133
post #101

How would you compare special features, if any, as well as advantages (and disadvantages) of using C# for developing an embedded DSL versus using Julia macros for the same purpose versus using specialized toolsets (e.g., MPS) for developing an external DSL? Please note that I'm aware of the Modeling SDK for Visual Studio. However, since it only allows integration with / targets the Visual Studio environment, it is no…

Maybe you can look at F#, it will compile for Android, iOS, windows, Linux, MAC, javascript frontends and server side. The feature set is different than Julia’s but it is very powerful and versatile.

Thank you for the suggestion. Will definitely take a more detailed look at F#. I have read about it some time ago, including some very positive general feedback. However, even if F# is an excellent fit feature-wise, I can see two potential issues: 1) lack of a decent package ecosystem (since the planned DSL is only one part of multi-feature multi-aspect platform puzzle) and 2) lack of a significant enough pool of experienced developers, which would make building a good team a challenge (due to its relative popularity, C# is IMO much better than F# in this regard).

Re: How Microsoft rewrote its C# compiler in C# and made it open source (2017)

#134
post #123
post #108

Earlier quoted context omitted.

Every VS release is one reason less to use Resharper.

The biggest reason IMO not to use ReSharper is actually Rider (so I don't use VS anymore either). You get all the ReSharper goodies, but inside an editor that's more nimble than vanilla VS.

I just don't use ReSharper anymore and almost don't miss it. I tried Rider but don't use it anymore. I don't like the Intellij/Rider UI, defaults shortcuts are horrible, basic actions are hiding in submenu. In my opinion, Visual Studio UX is not great, but far better than JetBrains products.

Re: How Microsoft rewrote its C# compiler in C# and made it open source (2017)

#135

Earlier quoted context omitted.

> Those tend to get resolved quite quickly. The issues are getting resolved in the public bug trucker, pretty quickly indeed, typically saying "can't reproduce, won't fix", sometimes "not a bug, won't fix". I'm not sure the software problems are getting resolved.

You can look through GH milestones to see specific issues fixed in results. For example, here are the 230 tracked items done for the VS 16.4 public release: https://github.com/dotnet/roslyn/milestone/53?closed=1 You can also see that there are many more resolved issues in previews of that public release: https://github.com/dotnet/roslyn/milestones?state=closed So there are a _lot_ of legitimate problems being fixed a…

My experience might be irrelevant to Roslyn, I experienced these things when reporting Visual Studio bugs in general. Examples:

https://developercommunity.visualstudio.com/content/problem/... (BTW, people have been reporting that bug for years now)

https://developercommunity.visualstudio.com/content/problem/...

https://developercommunity.visualstudio.com/content/problem/...

https://developercommunity.visualstudio.com/content/problem/...

Re: How Microsoft rewrote its C# compiler in C# and made it open source (2017)

#136

Earlier quoted context omitted.

Roslyn is very powerful, but it is still pretty cumbersome. At one point I spent quite a while trying to get a game scripting system akin to the way that Lua is commonly used working, and I just couldn't get it working fast enough to be viable. I essentially wanted to have a core C# engine that provided services, and then have it call an initialization function and a gameloop function that were defined in designated…

I think ignorance is a pretty powerful argument to be made by any developer wanting to use Roslyn. The last few times I messed with it there was literally no documentation and everything I knew/know comes from reading headers, trial and error, and experimentation. I feel defensive about calling it cumbersome though, and I can't imagine why something like your LUA vision isn't possible (though, I've never tried I just…

We have some documentation now: https://docs.microsoft.com/en-us/dotnet/csharp/roslyn-sdk/

would really appreciate bugs/comments on these docs pages of what else you would like to see.

Post reply on HN