News for hackers. Stuff that matters.
Re:Introducing .NET Standard by 2bitencryption on Monday September 26, 2016 @01:28PM (#12583767)
I started using Xamarin to develop an Android app, expecting the Xamarin platform to be some gross in-between which only exists to squeeze just a few more developers onto C#.

But, no joke, it's a BETTER experience than Android Studio. I had a much better time using Xamarin Studio (on OS X) and Visual Studio with Xamarin (on Windows) than I ever did with Android Studio. And not just because of the tools: C# provides so many great features that make Android development awesome on it. And the API is essentially the same as the true Android Java API; I found myself googling "start an activity on Android" rather than "Xamarin start an activity on Android" because it's all done the same way.

I normally don't obsess about my code looking clean and beautiful, but when I wrote my simple app in C# it shorter and easier to read than when I did it in the Android Studio.

Re:Introducing .NET Standard by pjmlp on Monday September 26, 2016 @02:04PM (#12584109)
I still don't understand how Microsoft was able to provide a better debugging and tooling experience for Android, than Google itself for their own OS, although Android Studio 2.2 finally seems to be usable.
Re:Introducing .NET Standard by Delmania on Monday September 26, 2016 @02:39PM (#12584436)
> I still don't understand how Microsoft was able to provide a better debugging and tooling experience for Android, than Google itself for their own OS, although Android Studio 2.2 finally seems to be usable.

Visual Studio was first released in 1997, the company has 20 years experience in designing and building tooling. I believe they also have a very firm dogfooding policy, and some very intelligent people work there.

Google changed the search engine landscape and created the only competitor to the iPhone, but building tools and tooling is definitely not a key strength.

Re:Introducing .NET Standard by pjmlp on Monday September 26, 2016 @02:51PM (#12584532)
Surely a few of those PhDs able to draw inverted tree algorithms on the whiteboard should be capable of producing a proper IDE that doesn't hang the computer all the time, an OS simulator and get their mind around how to have an actual working build system for NDK users.
Re:Introducing .NET Standard by em500 on Monday September 26, 2016 @03:08PM (#12584685)
But Android Studio is basically IntelliJ IDEA, which is not that much younger at 15 years.
Re:Introducing .NET Standard by mattmanser on Monday September 26, 2016 @03:54PM (#12585014)
The parent's point was that MS have the institutional memory and expertise that you don't get by simply forking someone else's codebase.
Re:Introducing .NET Standard by geldan on Monday September 26, 2016 @02:45PM (#12584482)
Except browser tooling, where they are far ahead of others.
Re:Introducing .NET Standard by mattmanser on Monday September 26, 2016 @03:58PM (#12585052)
Compared to VS, chrome dev tools are bloody awful.

There are some incredibly annoying basic missing features in Chrome dev tools. Like you still can't just hover over a variable, you inexplicably need to highlight it. Functionality that IE dev toolbar had 10 years ago. And don't even get me started on their shitty black boxing solution, something that should be as easy as right clicking on the file you want to black box, but no, time for some bloody regex foo.

It's better than Firefox + IE, by it's not better than proper IDEs by a long shot. And it's got "designed by a programmer" written all over it, the UX is awful.

Re:Introducing .NET Standard by oblio on Monday September 26, 2016 @05:25PM (#12585714)
Well, on the other hand, while debugging, if I recall correctly, in Eclipse you can select an (almost) arbitrary section of code and evaluate it. In Visual Studio for the same thing you have to use the clunky "Watches" feature. So even VS can improve.
Re:Introducing .NET Standard by dsp1234 on Monday September 26, 2016 @05:46PM (#12585881)
In Visual Studio for the same thing you have to use the clunky "Watches" feature.

VS has the 'immediate window' which allows you to execute (almost) any statement within the context of the local scope, including intellisense and autocomplete.

Re:Introducing .NET Standard by tracker1 on Monday September 26, 2016 @05:55PM (#12585924)
Caveat to the use of lambdas... Where, ironically the last time I used .Net was what I needed to inspect the most were subsets of collections or the results of other queries... I always used the function methods for linq over the language extension.
Re:Introducing .NET Standard by Locke1689 on Monday September 26, 2016 @11:32PM (#12587271)
Lambdas are supported in the debugger as of Visual Studio 2015 :)
Re:Introducing .NET Standard by tracker1 on Tuesday September 27, 2016 @02:00AM (#12587742)
Thanks.. can you tell I haven't done nearly as much .Net for the past couple years? ;-) Though the .Net core stuff has me relatively excited for the platform again.
Re:Introducing .NET Standard by alistproducer2 on Monday September 26, 2016 @02:30PM (#12584362)
For me, the biggest downside to AS is its reliance on graddle. I used AS pretty extensively and I honestly feel like the Eclipse workflow was much better.

I'm curious about Xamarin. I've been weary of cross platform tools since the days of trying to use phone gap but I understand the current gen of tools are much better.

Re:Introducing .NET Standard by mattleibow on Tuesday September 27, 2016 @12:15PM (#12590712)
Xamarin does not "wrap" the API in the traditional, it just provides a binding - calling a method in C# actually calls the underlying native method. The classes are just proxy classes and do not actually have anything more/less that does not exist in native code.
Re:Introducing .NET Standard by Nullabillity on Monday September 26, 2016 @05:04PM (#12585542)
Did you try Kotlin?