Highest Rated Comments


migueldeicaza31 karma

We do not want to be on any dreaded list, but I think that the list that you are quoting had us and Cordova on Mobile and everything else was non-mobile.

And some of the challenges just come with the territory, like having slow Android emulation on Windows (as Windows defaults to Hyper-V, which makes Android emulation slow).

This is one of the things that is most painful for our users, which is why we invested in the Live Player, so we could avoid using the Android Emulator at all, and just go straight to device and provide a live updating experience.

I would say that our users have complained about a number of things:

Compilation times: while things work great for small projects, the compilation times become very slow for very large projects. We are aware of the issues, and we are working towards long-term fixes. The issues are not just a matter of optimizing a loop though, they are usually fundamental problems in the way that we need to link native libraries or third party components and the balance between compilation times, deployment times and executable sizes.

For example: We can compile very fast if we do not remove unnecessary code, but then your application is larger.

Evolution of tooling: we had to cope with the migration from PCL to .NET Standard 1, to .NET standard 2, and this created a lot of problems for our users during the transition period. Things have started to stabilize, and the community has been rallying around .NET Standard 2, so we think that this issue will be solved mostly on its own.

As for how we are fixing those issues, we are trying to be very proactive on these issues, so we survey our users to find out what are their major pain points and fix those, and reactively when customers come to us asking us for help.

Our motto for years has been to delight developers, and it is something that our team aspires to achieve every day - from fixing bugs, and performance issues to designing APIs, tools, processes and UI that will achieve that goal.

migueldeicaza29 karma

The layout is fine, the problem is dealing with the people walking into the office to ask a question to someone else in the room

Even if they are trying to be polite, one question every day in a room of six people is still six interruptions.

And I have to unplug and replug computers all day as I go from my desk to a private room to take phone calls.

Not enjoying it one bit

migueldeicaza28 karma

Yes, we are!

More and more code is being shared between the IDEs today.

We are following the guidance to split our code between xplat code and platform specific code.

We started with the core of Roslyn, and we are in the process of replacing the text editor to share the same core as VS on Windows, except one will use a WPF frontend and the other will use a Xamarin.Mac (cocoa) frontend.

The HTML editor, CSS editor, Json editor, and soon the Razor and TypeScript and JavaScript editors will be 100% shared.

While VS 4 Mac started as a fork of MonoDevelop, over time, we have been replacing parts of the code with code from VS, and when we write new code, we write it in a way that works on both platforms.

For example, Mikayla today pointed me to this sample that shows where we are going, we will be one day be able to even share extensions between both of the IDEs:

https://github.com/gundermanc/vs-xplat-extensibility-samples

migueldeicaza27 karma

For years, my goal was to create a world built on open source software and this took various forms.

One of those forms were the efforts to build desktop applications -that at the time were lacking on Linux.

I wrote a spreadsheet called Gnumeric, and collaborated with others to put together a suite of desktop applications, the last one I was involved with was Evolution - an email and calendar client.

We built all of those with C, as scripting languages in 1997-2001 were just too slow to run on the machines of the day (we tried and tried).

.NET hit the right spot of high-level capabilities, and performance that we were looking for. So we set out to build an open source implementation so we could build the next generation of desktop apps for Linux

migueldeicaza25 karma

I am impressed how far Javascript has come.

I can't even