![]() ![]() It just will not allow you to avoid Windows. The above will allow you to own only a Mac (assuming it's Intel-based) and will still allow you to do all of your development in OS X + Mono if you so desire. All of our testing happened in VMs long before we put them on real boxes. When our code was buggy, we could REALLY mess things up. At my last job, we did low-level invasive scanning and tweaking. If your app has the possibility to do any damage, you'll especially want to use VMs for sandboxing. VMs are good enough for most testing and debugging. environment that you prefer, you'll eventually want to test your apps running at native speed. That said: I'd recommend Boot Camp and Parallels/VMWare. Even if you abhor Windows and all that it stands for, if you're writing software for Windows, you owe it to your users to thoroughly test it in Windows. I would never release any product, even internally, that I've never even run myself in the intended environment. The gist behind this question seems to be the idea of avoiding purchasing a Windows license and using Mac and Mono only. Regarding development environments: #develop and MonoDevelop are cross-platform. ![]() NET to Mono a few years ago, things went very very badly but I've been told that Mono has been greatly improved since then. To answer your question directly: yes, Mono's performance is fast enough for developing on the Mac. NET and Java on most tests, with a handful of exceptions.įinally, OSX-specific limitations are being worked on, and will also be in 2.8. Sadly LLVM makes for very slow JIT compile times, so we only use it for "ngen" like scenarios or for programs that want better performance at the cost of startup speed. The codegen engine can now optionally use LLVM, in 2.6 it is ok, in 2.8 it will have 99.8% code coverage (from the current 60 or 70). We are working on a new GC that is generational, like.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |