141–149 of 149 posts
Earlier quoted context omitted.
I'd have thought something more like the old Qt license tiering would make sense - a GPL version that can only be used to develop GPL apps and a commercially licensed version if you want to sell anything.
The app store does not allow GPL'd apps.
Looks nice, but as with MonoTouch the pricing kills it for me. While I'm sure it pays for itself in overall value if you actually ship a product with it, attaching a price that high to a development tool causes (IMO) all sorts of secondary effects like balkanized user community, inability to realistically use it for writing open source software that anyone will collaborate on, etc. If the product cost more like $99 i…
As a hobbyist, you could always use MonoMac. It is still free and you may have to wrap the StoreKit APIs yourself.
Earlier quoted context omitted.
I don't think they're trying to funnel users to MonoDevelop, I think they're using it because the iOS SDK is for Mac. Take a look at Mono for Android, for example. It uses a VS plugin instead of MonoDevelop.
I might be in the minority here, but I use MonoDevelop in preference to visual studio. It's got a couple of irritating issues (the plugin support is rubbish even now, and it's ridiculously complicated to roll your own), but its just so fast . My morning at work is: git pull, go get coffee while VS spazzes out for 5 minutes and resharper reindexes everything.
Earlier quoted context omitted.
Why not? Visual Studio costs thousands of dollars a license. They could even compete on price, not only features. Windows is a market for such a product just as much as *X is.
VS Professional is only $500, not "thousands of dollars". It used to be $300 for 2008 Pro, but even now it is still OK for an indie at $500.
Earlier quoted context omitted.
I'd personally love for JetBrains to do a C# variant of IDEA (+ R#) for us OSX/*nix folk. I have serious doubts such a beast would be commercially viable, though. (Maybe R# for MonoDevelop? One can dream...)
Why not? Visual Studio costs thousands of dollars a license. They could even compete on price, not only features. Windows is a market for such a product just as much as *X is.
Looks nice, but as with MonoTouch the pricing kills it for me. While I'm sure it pays for itself in overall value if you actually ship a product with it, attaching a price that high to a development tool causes (IMO) all sorts of secondary effects like balkanized user community, inability to realistically use it for writing open source software that anyone will collaborate on, etc. If the product cost more like $99 i…
Where does this leave MonoMac? http://www.mono-project.com/MonoMac states that Xamarin.Mac has broader API coverage; does this mean MonoMac will continue to be developed, but just remain as a (free) subset with LGPL portions?
Earlier quoted context omitted.
If Java is a terrible language and horribly designed then why do people still use it?
1) Great built-in library 2) great third party libraries, 3) decent documentation and tons of books and instructional material, 4) best-in-class virtual machine, good GC, as speedy as you get with managed code, 5) tons of profilers and development tools 6) several industry leading tools written in it (Hadoop, Lucene/Solr, Hbase, etc) and for it (IDEA, Eclipse), 7) Enterprise support from big companies (Sun, now Oracl…
9) A large ecosystem of interoperating JVM languages, from Java-like (Kotlin, Ceylon, Fantom), Ruby/Python like (JRuby, Jython, Groovy), to Haskell like (Scala), to Lisps (Clojure).
Earlier quoted context omitted.
I've been playing with it on my own, and I tend to agree. MonoDevelop is still pretty rough--I'm doing game stuff, so I'm kicking any actual OS X development down the road as far as humanly possible--but once you get your code deploying, it's a very nice setup. I'd really like a way to build in VS (maybe against dummy assemblies or something) and kick it over to my MBP for real compilation and deployment, though. I r…
I don't think they're trying to funnel users to MonoDevelop, I think they're using it because the iOS SDK is for Mac. Take a look at Mono for Android, for example. It uses a VS plugin instead of MonoDevelop.
I'd pay for MonoTouch like-right-now, even though the project I really want it for isn't near ready for it, if I could write in VS, press a button, and have it build and deploy on my Mac.