Cool stuff. Now how about running C# apps on the web? :)
Your C# App on 66 Million Macs: Announcing Xamarin.Mac
51–60 of 149 posts
Re: Your C# App on 66 Million Macs: Announcing Xamarin.Mac
#52This might be the final blow to Java on the desktop.
Personally, I think computing power has hit the point where Java desktop apps and applets aren't that big a deal. I've got one running on my desktop right now. It runs for day's on end without being a significant burden to the rest of the system.
Many still write code without thinking one second about performance.
Java isn't C, but if you code thinking about performance it is possible to write quite usable applications for many use cases.
Re: Your C# App on 66 Million Macs: Announcing Xamarin.Mac
#53This might be the final blow to Java on the desktop.
If Java is a terrible language and horribly designed then why do people still use it?
1) Tons of experienced and battle-tested people in the ecosystems
2) Standards that keep improving
It's a dual-edge sword thingie, on one hand standards are good for stability but bad because sometimes it slow innovation down. Having said that, the Java ecosystems typically have one strong alternative outside the standard so your choices, in most cases, come down to 2: use what comes from SUN/Oracle or use the leading open source alternative solution. Simple.
Re: Your C# App on 66 Million Macs: Announcing Xamarin.Mac
#54Earlier quoted context omitted.
Not at all. This offers a completely different solution than java. With java, you write once and run on everything. This lets you write C# on OS X, but it won't compile and run on Windows or Linux. Windows software can't be as easily ported to OS X either, the entire GUI, at the least, will have to be rewritten. I would argue that Python would make more sense as a java-killer. It has the write once, run everywhere th…
Yes, but write-once-run-anywhere solutions deliver mediocre user experiences on every platform. You don't want your Mac app to look anything like your Windows 8 app. With Xamarin you separate the presentation layer of your app from the rest of the app, and the only thing you're rewriting from platform to platform is the UI. Typically this is only about 25% of the code (though of course it can vary). This is how our c…
Re: Your C# App on 66 Million Macs: Announcing Xamarin.Mac
#55Cool stuff. Now how about running C# apps on the web? :)
Re: Your C# App on 66 Million Macs: Announcing Xamarin.Mac
#56Xamarin's stuff looks really nice, but I really wish they had a non-profit free tier. I can't even make opensource Android apps without paying a lot. The other problem is the lack of linux support for their SDK. Seems rather odd, considering Mono's roots.
It personally pains me not to support Linux, but we get such a tiny fraction of our customer base coming from Linux that it isn't worth it. Not to mention that there is effectively no "Linux" platform and you have to select a subset of distro versions.
Perhaps more of your customers would use Linux for Xamarin stuff if it was available?
Re: Your C# App on 66 Million Macs: Announcing Xamarin.Mac
#57This might be the final blow to Java on the desktop.
If Java is a terrible language and horribly designed then why do people still use it?
Re: Your C# App on 66 Million Macs: Announcing Xamarin.Mac
#58Earlier quoted context omitted.
At a $1,000 a license? I don't think so.
$1,000 seems pretty meager to me. If I can share well over 50% of my code across multiple platforms then that is code that I don't have to rewrite in another language. If that 50% takes more than 10 hours to reproduce (allocating my time at $100.00/hr) then it is well worth the expense. That doesn't even factor in the time saved in maintaining the application going forward. Granted, if you are just building a small a…
Re: Your C# App on 66 Million Macs: Announcing Xamarin.Mac
#59Re: Your C# App on 66 Million Macs: Announcing Xamarin.Mac
#60Earlier quoted context omitted.
Personally, I think computing power has hit the point where Java desktop apps and applets aren't that big a deal. I've got one running on my desktop right now. It runs for day's on end without being a significant burden to the rest of the system.
It's the quality of the experience, GUI, not just the resource-hoging of Java Desktop app. And even for that "It runs for day's on end without being a significant burden to the rest of the system" is hardly something to write home about.