5 ms·
Something like this is sorely needed by the open-source, not-for-profit, shoestring-resources, cross-platform development community... For example, let's say t
by peter_d_sherman 8y ago
Something like this is sorely needed by the open-source, not-for-profit, shoestring-resources, cross-platform development community...
For example, let's say that I'm writing some cross-platform open source software. And let's say that I am developing this software on a Windows or Linux Box.
Now, let's say that for whatever reason, I don't have and can't afford a Mac (a scenario like this is more common than you would think, especially in developing countries...)
OK, so now how do I compile/run/test the Mac version of my software -- without having that Mac?
?
That's why your software is so important.
Anyway, if you can get this fully operational (GUI and everything), you'll solve that problem for that group of software developers...
If you're successful, if you prevail... Apple shouldn't sue you... they should help you, because additional software for their platform ultimately benefits their platform.
Also, judging by the source, you've done an amazing amount of work so far... I hope you can find the additional developers/contributors you need to take this thing to completion...
- karmakaze 8y agoWorth noting that outside of this bubble, macOS has less than 10% market share. Not every software needs to run everywhere. There are other working solutions, JetBrains seems to do alright with Java runtimes.
- MuffinFlavored 8y ago> Now, let's say that for whatever reason, I don't have and can't afford a Mac. Rely on some developer(s) spend 10,000 hours of their time for free developing a Mac emulation layer, or go on eBay and buy a $600 used Mac to test on...
- deleted 8y ago[deleted]
- asark 8y agoIt may still be too expensive for devs in (very) developing countries or whatever, but I'm pretty sure there are (paid) remote desktop solutions for this. Also you can snag an old mac mini for well under $600, where I am. Like $200-300. It won't be good but that's probably better for testing anyway.
- scottjg 8y agoI offer a service that provides you with your own macOS VM, running on real Mac hardware. https://zeromac.com https://zeromac.com It's billed by the hour, so if you just need to quickly test something, it's pretty cheap. Buying an older mac may be more economical though if you need to develop software long term.
- MuffinFlavored 8y agoThis is super interesting. Is it your full time job? What level of success are you having with your idea?
- scottjg 8y agoI run it alongside my regular consulting work, so I suppose it's not my full time job. It's also a fairly new business so I'm not too sure how successful it will be yet.
- axaxs 8y agoWhile your point is taken... I write and contribute to free/open source tools. I can afford a Mac, but will not buy one because there's zero incentive to me. While I'm not sure this project would help, if a free or very low cost proper emulation existed, I'd use it.
- gchamonlive 8y agoIt may also be a matter of principle. I won't buy macs even though they are sexy and I have the money for it because I don't agree with its practices. My theoretical customers shouldn't suffer from it though
- macdice 8y agoOr use one of the CI providers that will test your stuff on macOS (alongside Windows, FreeBSD, ...). Possibly for free, if your stuff is open source. I use that for Windows, which I don't personally use at all, and it finds bugs and problems all the time. I wish someone would provide free (!) CI for some rarer OSes and CPU architectures too, but I can dream.
- viraptor 8y agoYou can't fully test things this way. Not enough to make a serious release anyway. You can easily pass all tests while not being able to even start the app. You need at least one person with the real hardware to do testing.
- saagarjha 8y agoThis really depends on the tests you're running.
- viraptor 8y agoTrue. But in context of: "tests in a CI environment which costs you less than a MacBook", I don't believe anyone would go to the level that avoids those issues. It would take a lot of work and resources to replicate a "real run in clean, real environment".
- saagarjha 8y agoAgain, this depends on the tests you’re running and how you’ve set up your CI environment.
- faissaloo 8y agoUnfortunately MacOS testing is usually extremely slow due to limited numbers of machines to run tests on.
- loeg 8y agoThe nice thing about the former is that that cost is shared across all consumers, whereas the latter would be incurred for every user. The latter approach may still cost less for now (or forever), but it's something to keep in mind.
- michaelmrose 8y agoThe logical option c is just to not support mac unless your target market is one disproportionately likely to use macs like developers or artists in the US.
- zapzupnz 8y ago> For example, let's say that I'm writing some cross-platform open source software > OK, so now how do I compile/run/test the Mac version of my software -- without having that Mac? You don't. Darling is not a suitable replacement for testing on a real Mac in exactly the same way WINE is not a suitable replacement for testing Windows software. A developer who thinks so is misguided. Virtualising macOS would be more suitable, although the only way to do so without violating macOS' licence conditions is to run the virtualised OS on a Mac anyway. Even then, virtualised macOS lacks hardware accelerated graphics support, limiting the testing of GUI apps at least. > Apple shouldn't sue you There's no reason they would. Nothing of Apple's seems to be infringed, as the system seems only capable of running anything that Apple's open source Darwin OS can. Even if the Darling project reimplemented some of Apple's proprietary frameworks, this could be done based on Apple's open source releases of things such as Core Foundation, etc. The reimplementations of things like AppKit, when done in the future, could even possibly be based on something like GNUstep — which would give that project a well-needed shot in the arm, to say the least. > additional software for their platform ultimately benefits their platform Firstly, any well-written cross-platform software is easily ported to macOS. This is most evident with software intended for FreeBSD but is equally possible with software that originates on Linux; see Homebrew, MacPorts, etc. for the plethora of utilities that began life on Linux but have since become cross-platform, or software made by GNU that is typically cross-platform by design. Secondly, Apple has been down the cross-platform road before, and none of its developers wanted a bar of it. Apps that are developed on other systems but not tested properly on macOS are always heavily criticised by macOS users as feeling foreign and un-Mac-like. Back when Mac OS X was shiny and new, Apple offered three major platforms for developers: Cocoa, their C and Objective-C APIs inherited from NeXTSTEP; Carbon, their C and C++ APIs inherited from Classic Mac OS; and Java, a cross-platform offering to entice developers from other platforms, particularly Linux. Apple deprecated their own Java in 2010 because (A) people really disliked using Java apps, even though Apple's implementation of the JVM was performant and had native support for Cocoa-style controls and (B) nobody was using it, with major preference going to Apple's own Cocoa and Carbon APIs. Apple, and its userbase, prefer apps that are made with love and care _on_ Macs and _for_ Macs/iOS devices/Apple Watches/Apple TVs, respecting those platform conventions by being developed and tested on them.
- 8y ago
- lostgame 8y agoGenerally different platform builds are handled by different developers - the codebase has to be modularized to be ported from Windows, to, say, Linux, to start, same with the UI. If you're already porting to Linux, you're already dealing with a UNIX executable, which makes it at least slightly easier to port to MacOS. There are also virtualization services available where you can rent dev time, and decent and upgradeable Macs are not that expensive second hand. I dev on MacOS all the time, and have the same issue with Windows. These days I try to write everything as a PWA to start so I especially don't have to deal with extreme UI/UX pains.
- xoa 8y ago>I don't have and can't afford a Mac Why wouldn't you just virtualize, same as any other OS? If you're not virtualizing on Mac hardware than there are a few minor extra hoops to jump through but it's still less work compared to a hackintosh. Performance can be janky if you don't dedicate a video card to it, but something perfectly adequate like a Radeon 560 seem readily available for $60-80 now. There are a few bits of Mac specific hardware these days like the T-series chips, but not even all supported Macs have that by a long shot.
- simcop2387 8y agoDoing so is not legal in most countries. the macOS T&C/EULA/etc. forbid running it on non-apple hardware. This is a large barrier to entry that a lot of people don't want to even approach.
- qaq 8y agoIn developing countries piracy is rampant none really cares much about EULAs
- T-A 8y ago>OK, so now how do I compile/run/test the Mac version of my software -- without having that Mac? Splurge on a $1/hour or $20/month account with https://www.macincloud.com/ https://www.macincloud.com/ ?
- electroly 8y agoIn case anyone is curious, you have to prepay $30 for the PAYG plan, and you get non-admin access to the slowest Mac Mini you've ever used in your whole life. It does technically work to build iOS and macOS apps, though.