NET core really needs the options that mono has. That would make my life.Īnd one more thing. Core will be OSS and I certainly hope canonical puts it in the ubuntu repos. Just look at the java community, i have no idea how they manage when the primary runtime isnt even allowed in the repositories. Its been absolutely great for what it is as long as its been out, and there are parts of it that Microsoft really needs to integrate (Mono.SIMD, Cecil, etc.), but it is going to be much easier for the development community to all go to one place for a solid, stable, and tested runtime that we all use. But don't get me wrong, I would switch to a microsoft supported alternative in a hot minute. Its stable and extremely fast when comparing to a php or python. Its been absolutely great for us and we even run it in various places across our stack in production apis. NET to be used more widely, and greatly improves the diversity and skillets in the. NET Developer (even if you're only developing on Windows), you should be excited, because this opens up. NET Framework (the Windows-only larger superset), but the commitment to. Of course, ASP.NET also runs on top of the. NET core, by redesigning ASP.NET 5 to run on top of.
Microsoft has already made a huge commitment to. NET, and Microsoft's history of chucking compatibility to the side in favor of new features (I think of Java apps I wrote in 2007 that still work on Java 8 - now that's backward compatibility). NET, but the concern in the past has largely been around the proprietary nature of. I don't think so - a sizable portion of developers on Linux may like. If this goes anything like Skype's buyout, expect support for the Linux version to drop steadily in quality over time. But it's got such a nasty ability to keep not working at no fault of the developer. Xamarin has an amazing idea and when it works, it's great. They're often not really programming issues and certainly not a problem with my code. I hate, hate, hate dealing with these kinds of issues. I've lost so much time over issues like this and it's immensely frustrating. Just today I encountered a cryptic issue of installation failing that was resolved by uninstalling the app on the iOS device (which has never been necessary before and shouldn't be). I've also had countless issues with devices not being recognized or mysteriously not building.
#Xojo vs xamarin update#
Last time Xamarin updated, it didn't correctly update some paths in the project (I found the wrong version number in the path fine, but not the rest of the path changes).
The fix is to add a x:Name to a XAML file. For example, there's a current bug where certain files needef for Xamarin.Forms aren't generated automatically like they're supposed to be. I've encountered so many bugs and other issues that stop me from being able to code. Are you interested in promoting your own content? STOP! Read this first.Īnd pricing aside, it certainly has some serious downsides with regards to setting it up (not too bad for Android, but iOS is stupidly complicated - although it's a bit easier than it used to be).For posting job listings, please visit /r/forhire or /r/jobbit.Do you have something funny to share with fellow programmers? Please take it to /r/ProgrammerHumor/.Do you have a question? Check out /r/learnprogramming, /r/cscareerquestions, or Stack Overflow.Direct links to app demos (unrelated to programming) will be removed.
#Xojo vs xamarin code#
If there is no code in your link, it probably doesn't belong here.