Earlier quoted context omitted.
You 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.
This really depends on the tests you're running.
Darling – macOS Translation Layer for Linux
31–40 of 176 posts
Re: Darling – macOS Translation Layer for Linux
#32I wish I had the time to contribute to this. Getting Logic running on linux would let me ditch the Apple hardware. It's usefulness is entirely limited to the implementation of the core library frameworks such as Core Image, Audio, MIDI, Animation, Data, etc...which will be very, very difficult, I think, while maintaining FOSS status.
I wish Ardour had some of the features Logic does (most significantly flex time), as well as a nicer UI. Literally Logic is the only thing keeping me on macOS.
Re: Darling – macOS Translation Layer for Linux
#33I wish I had the time to contribute to this. Getting Logic running on linux would let me ditch the Apple hardware. It's usefulness is entirely limited to the implementation of the core library frameworks such as Core Image, Audio, MIDI, Animation, Data, etc...which will be very, very difficult, I think, while maintaining FOSS status.
I wish Ardour had some of the features Logic does (most significantly flex time), as well as a nicer UI. Literally Logic is the only thing keeping me on macOS.
Re: Darling – macOS Translation Layer for Linux
#34[0] https://github.com/shinh/maloader [1] http://shinh.skr.jp/slide/ldmac/000.html
Re: Darling – macOS Translation Layer for Linux
#35What would be amazing is if Darling could join forces with the long-running GNUstep project in order to provide access to the Cocoa APIs. This would provide a means to run Cocoa apps on Linux, which will make Linux a more attractive operating system for prospective Mac converts and may also increase the popularity of GNUstep. Also, with many Mac users expressing anxieties about the future of the Mac given Apple's bus…
— System-wide UI consistency, especially in the fine details
— Singular UI/UX vision eliminates points of confusion and everything-is-a-compromise choices for third party developers
— Navigable by non-experts, even when things turn to shit
— Nominally "perfect" hardware support
— Robust colorimetry
— Millisecond audio latency
I use Linux extensively, but I'm not aching to leave macOS as my primary platform. Yes, they did start to go a bit loopy and off-track around Mac OS X 10.7–10.9, but from my vantage point it has been all uphill again since Mavericks.
The idea of running Mac apps in a Wine-like compatibility layer sounds worse than anything Apple could ever do to macOS. Yes, I like free. And yes, I like personal choice. But I value my time and I'm sorry to proponents of other platforms, but macOS just values my time more than any other platform.
________
[0] The achilles heel of the open source community stems from the lack of a unifying vision and a top-down approach. This has major advantages as well as major disadvantages. But nonetheless it affects the result. And depending on your priorities, the advantages might outweigh the disadvantages or vice versa.
[1] And to be fair it's equally true in the opposite direction. Open source succeeds in many aspects like robustness, hardware compatibility, longevity and transparency/deep trust. Hence why it has utterly destroyed the server market. These areas of success are not accidental or arbitrary.
Re: Darling – macOS Translation Layer for Linux
#36What would be amazing is if Darling could join forces with the long-running GNUstep project in order to provide access to the Cocoa APIs. This would provide a means to run Cocoa apps on Linux, which will make Linux a more attractive operating system for prospective Mac converts and may also increase the popularity of GNUstep. Also, with many Mac users expressing anxieties about the future of the Mac given Apple's bus…
The problem with replacing MacOS is that its key value lies in aspects that the open source community have yet to succeed in, or are structurally unfit to succeed in.[0][1] — System-wide UI consistency, especially in the fine details — Singular UI/UX vision eliminates points of confusion and everything-is-a-compromise choices for third party developers — Navigable by non-experts, even when things turn to shit — Nomin…
Re: Darling – macOS Translation Layer for Linux
#37I'm puzzled, wont most console apps already cross compile without much modification? Isn't this basis of brew/etc? The GUI piece seems like the key, but without it I'm failing to understand why this is significant.
Re: Darling – macOS Translation Layer for Linux
#38Earlier quoted context omitted.
Every year or so I take a look at GNUStep just to see what's going on. Crazy it hasn't taken off.
Unfortunately - call me superficial - I can't really get past its crusty look.
They've added theming support to GNUSTEP, but that's really lipstick on a pig. Then again, I can't blame them too much, the project is mostly quiet and doesn't attract as much attention as the other popular Linux toolkits.
Re: Darling – macOS Translation Layer for Linux
#39Earlier quoted context omitted.
The problem with replacing MacOS is that its key value lies in aspects that the open source community have yet to succeed in, or are structurally unfit to succeed in.[0][1] — System-wide UI consistency, especially in the fine details — Singular UI/UX vision eliminates points of confusion and everything-is-a-compromise choices for third party developers — Navigable by non-experts, even when things turn to shit — Nomin…
— Internationalization
Re: Darling – macOS Translation Layer for Linux
#40What would be amazing is if Darling could join forces with the long-running GNUstep project in order to provide access to the Cocoa APIs. This would provide a means to run Cocoa apps on Linux, which will make Linux a more attractive operating system for prospective Mac converts and may also increase the popularity of GNUstep. Also, with many Mac users expressing anxieties about the future of the Mac given Apple's bus…
As someone who was part of the GNUstep scene and contributed a tiny bit of code, I think the reason is obvious: GNOME was getting the big corporate investment, and KDE also had a stable foundation somehow. As you say, the "Linux desktop" very quickly came down to a GNOME/KDE duoply. Plus, GNUstep was written in Objective-C which was outside of a lot of devs' comfort zone at that time. So, GNUstep only managed to attract a few passionate hobbyists but no more.