Live data from Hacker News

Microsoft Acquires Xamarin

weblogs.asp.net

261–270 of 405 posts

Re: Microsoft Acquires Xamarin

#261
"Anything you can do in Objective-C, Swift, or Java you can do in C# with Xamarin"

What about the things that you can do in Objective-C but cant do in Java, or visa versa? iOS has some iOS specific features that I'm not sure how Xamarin could possibly map to Java.

Re: Microsoft Acquires Xamarin

#262

"Anything you can do in Objective-C, Swift, or Java you can do in C# with Xamarin" What about the things that you can do in Objective-C but cant do in Java, or visa versa? iOS has some iOS specific features that I'm not sure how Xamarin could possibly map to Java.

There are platform specific APIs for that functionality. You can't necessarily do everything on each platform that you can on a given platform, but if you want some iOS or Android specific behavior you can implement it.

You might have to wait a bit for new releases for features that come out in new OS versions, but that's not terribly surprising.

Re: Microsoft Acquires Xamarin

#264

Earlier quoted context omitted.

Look at Winforms, WPF and Silverlight. They are all .Net and all abandoned. I wouldn't bet my long term future on Xamarin.

Yes, Silverlight has been abandoned. I would argue that Winforms is now a mature technology and requires little upkeep, but it is still a part of the stack. WPF development has slowed significantly, but still proceeds.

None of these are good technologies if you want to stay up-to-date. You could also write your site in IE6 compatible HTML which was quite mature but that seems a really bad idea.

Re: Microsoft Acquires Xamarin

#266

"Anything you can do in Objective-C, Swift, or Java you can do in C# with Xamarin" What about the things that you can do in Objective-C but cant do in Java, or visa versa? iOS has some iOS specific features that I'm not sure how Xamarin could possibly map to Java.

Xamarin offers common APIs for platform-specific behaviors when using Xamarin.Forms, otherwise, when targeting Xamarin.iOS or Xamarin.Android, you're developing with pure-native APIs. You will need to use the native provider for whatever action you're executing. If you'd like to be able to reuse common concepts cross-platform, then you need to write your own interface and provider model.

Xamarin is the equivalent of a thin wrapper/intercace over the platform-implementations. Xamarin doesn't really "do" much, it just calls the underlying API which maps to the specific behavior. The type and method signatures for Objective-C and Java are very near synonymous in Xamarin/C#.

Re: Microsoft Acquires Xamarin

#267

Earlier quoted context omitted.

I've seen that but the showcase doesn't look very convincing compared to say emscripten. Do you know about any bigger projects using JSIL ?

I've not used JSIL myself, but the performance of the demos seems fairly decent. Do you have any bigger .NET projects of your own you could try out? If you're looking for asm.js/wasm support in particular, you may be interested in LLILC, which appears to be a .NET Core to LLVM IR compiler, meaning you could make use of Emscripten to convert the code to asm.js: https://github.com/dotnet/llilc

I don't, I've written a prototype for my lib a year ago in C# and probably have that lying around somewhere but since then we've ported it to C++ and done heavy refactoring/development - I could probably spend some time and try to get that prototype working on JSIL but I need to see how the xamarin story plays out before I invest significant time into this.

IIRC LLILC is ways off from actually being usable as a static compiler and you'll still have to figure out how to ship a runtime and do GC in asm.js (realistically can't) and not to mention it's single threaded so it's a question if you can even get CoreCLR to run in such enviroment without heavy modifications.

It would be huge if we could just write everything in C# (frontend/lib and backend) but I don't see this realistically being possible for at least two years given the development pace of webasm.

Re: Microsoft Acquires Xamarin

#268

Given that Xamarin bought RoboVM last year and that the project went closed source and raised prices just after that, it's fair to assume that RoboVM is dead. Also, I'm personally not happy about this. I think people on HN should know better. Besides a couple of black swans being the exceptions that confirm the rule, acquisitions is how projects die. This is because acquisitions are either defensive or acquihires. An…

android youtube and maps were all acquisitions.

i think it's confirmation bias you don't really think of all the many successful acquisitions only the bad ones stand out.

Re: Microsoft Acquires Xamarin

#269

Earlier quoted context omitted.

>>Nonsense. The last 5 years show it's a whole new Microsoft Yeah, that's why Windows 10 sends all your data to Microsoft by default and Windows updates no longer come with detailed explanations of what is in them. /s edit: judging by the downvotes, there's a surprising number of Microsoft fanboys here. I guess all they had to do to win people over was make a few token contributions to the open-source community...

The Windows 10 privacy issues really do leave a bad taste, and I will be sticking to Windows 7/8.1 for as long as I can. There is a reason there are free upgrades to 10 being pushed so hard, and it's not because they are feeling nice. It seems like they are giving with one hand (open source to developers) and taking with the other (data from their unsuspecting users).

> sticking to Windows 7/8.1

Well, you know, you can't walk into the same Windows twice. (Unless you ignore all updates.)

Re: Microsoft Acquires Xamarin

#270

This is giant news for the .NET ecosystem. It means that MS is serious about their push into Mobile and Linux, and that .NET developers aren't going to have to work with Xamarin's ever-so-slightly-behind libraries anymore. It also means that MS now produces an IDE on Linux, which is a crazy change from 10 years ago.

When the integration is done, we'll have Dotnet Core targeting Windows, OSX, Linux, Android and iOS. There will be frameworks for serverside and clientside applications. I think it can become the best alternative to the javascript world, which already can target all these, but needs all kinds of native support and is much less solid as a language.

If they could convince all browsers to host some version of the CLR so you could have IL and so (C#/VB.NET/F#) as a viable alternative to JavaScript then I would agree.
Post reply on HN