News for hackers. Stuff that matters.
Re:Darling: macOS Translation Layer for Linux by grishka on Sunday October 04, 2020 @10:38PM (#24684056)
I wish they took more of a ReactOS kind of approach. Namely, use all the open-source parts that go into macOS, like the kernel and CoreFoundation, and write the proprietary ones from scratch. Then you'd finally have a desktop OS with no compromises and a huge existing app ecosystem (and a consistent GUI).
Re:Darling: macOS Translation Layer for Linux by shp0ngle on Monday October 05, 2020 @02:46AM (#24685173)
That exists, is named PureDarwin (I think) and is about as active as the original article project.

Which is not completely dead, but also not that active.

Turns out there is a big effort difference between “why don’t they just”ing on forums and actually doing it! :)

Re:Darling: macOS Translation Layer for Linux by scythe on Sunday October 04, 2020 @10:57PM (#24684153)
That was tried with OpenDarwin, but Apple was not a fan of the project IIRC.

More generally, it doesn't offer much of practical value to use the Darwin kernel which is at this point pretty tied to Apple hardware that comes with OS X anyway. You can still Hackintosh but it just adds a lot of additional complexity that you won't have to deal with on Linux.

Re:Darling: macOS Translation Layer for Linux by grishka on Monday October 05, 2020 @07:22AM (#24686600)
The point is that desktop Linux is still pretty much a bunch of standalone components loosely duct taped together. Sometimes they fall apart, but even when they don't, it still shows. Linux GUIs still feel like an afterthought.

upd: googling "OpenDarwin" bings up two first results that are news of it closing, in 2006

Re:Darling: macOS Translation Layer for Linux by chungus_khan on Monday October 05, 2020 @08:44AM (#24687211)
And working with the Darwin kernel would offer zero benefit in fixing this. The GUI coming out the other side would still rely on all the same technology as Linux desktops do, just as is the case on BSDs. Using a different UNIX kernel doesn't change any of that, and any effort made on the Darwin side would be easily ported to Linux. The GUI components of Mac OS are not open source.
Re:Darling: macOS Translation Layer for Linux by grishka on Monday October 05, 2020 @12:21PM (#24689148)
> The GUI coming out the other side would still rely on all the same technology as Linux desktops do

Why? Where does this logic come from? And apparently it's common, because PureDarwin mentioned in another comment does just that for some reason.

IMO, the right thing to do would be to replicate Apple's proprietary stack as closely as possible. Like, literally take the real macOS and start replacing essential proprietary frameworks like Cocoa and Quartz and core apps like Finder and Dock with fully API-compatible open-source ones. You'll eventually end up with a fully open-source operating system capable of running macOS apps.

Re:Darling: macOS Translation Layer for Linux by chungus_khan on Monday October 05, 2020 @02:19PM (#24690421)
That would have to be done from scratch as literally none of that is open source. While it could be done, the same amount of effort spent building a better Linux desktop would be more efficiently spent if the goal was to just get a high-quality open source desktop offering.

There's also some hairiness legally about working from within the official Mac OS system outwards AFAIK.

Re:Darling: macOS Translation Layer for Linux by grishka on Monday October 05, 2020 @02:56PM (#24690789)
> That would have to be done from scratch as literally none of that is open source.

That's the point. ReactOS doesn't use any of the Linux parts, and it's reimplementing everything from scratch because there are no open-source components in Windows afaik.

Re:Darling: macOS Translation Layer for Linux by saagarjha on Monday October 05, 2020 @08:49PM (#24693745)
Re:Darling: macOS Translation Layer for Linux by monadic2 on Monday October 05, 2020 @11:22AM (#24688538)
It would offer access to the mac software ecosystem, particularly the (imho) cohesive set of underlying frameworks. Just like linux is "just" a kernel but is in reality a center of floss development, actively organizing around bringing binary compatibility can bring incidental benefits.

That said at this point I don't see anything inherently easier or beneficial about this than creating some other project around an alternative paradigm than PC derived desktop systems on top of some existing better supported kernel.

That said contrary to what the previous poster implied I don't think either OpenDarwin or PureDarwin aimed at reproducing the proprietary bits—they were/are essentially quirky, buggy, poorly documented BSDs just as reliant on the floss ecosystem as much better supported stacks.

Re:Darling: macOS Translation Layer for Linux by blablabla123 on Tuesday October 06, 2020 @07:17AM (#24696564)
> The point is that desktop Linux is still pretty much a bunch of standalone components loosely duct taped together.

To some degree it is. On the other hand this is also why I prefer to use Ubuntu or Debian over any other distribution. They are highly integrated and opinionated in the sense that they keep the packages as unmodified as possible.

Re:Darling: macOS Translation Layer for Linux by symlinkk on Monday October 05, 2020 @09:31AM (#24687586)
Have you used GNOME? Download Fedora and tell me it’s not more visually consistent than Windows
Re:Darling: macOS Translation Layer for Linux by ric2b on Monday October 05, 2020 @12:25PM (#24689181)
> Then you'd finally have a desktop OS with no compromises and a huge existing app ecosystem (and a consistent GUI).

What compromises does Ubuntu have vs MacOS? It has orders of magnitude better gaming support thanks to Wine + Steam Proton.

Re:Darling: macOS Translation Layer for Linux by grishka on Monday October 05, 2020 @01:57PM (#24690210)
Linux GUIs are extremely inconsistent and just generally feel like an afterthought. Out of all GUI desktop operating systems I've used, nothing comes close to macOS as far as consistency goes.

Besides that, Linux desktop is this loosely stacked pile of different components that sometimes falls apart. No one wants to spend 50% of their time writing config files and setting up drivers instead of actually doing something useful.

Re:Darling: macOS Translation Layer for Linux by ficklepickle on Monday October 05, 2020 @07:22PM (#24693139)
So, misconceptions and generalizations then?

I don't understand how you can make sweeping generalizations about every desktop environment that runs on Linux. Every DE is an afterthought? Just the fact you call them "Linux GUIs" makes me question how much you have even used any DE with Linux.

I spend no time writing system config files. Drivers are part of the kernel, so I also spend zero time on that. Brand-new laptop hardware sometimes takes a while to get support, but it is really easy to check before you buy.

It is perfectly OK to prefer a padded, walled garden. Just like it is OK to prefer a modular OSS Linux environment where everything is knowable. Nobody needs to be "right", and nobody needs to bash the other with unsubstantiated claims.

Re:Darling: macOS Translation Layer for Linux by grishka on Monday October 05, 2020 @08:13PM (#24693547)
I do, of course, know that there are many DEs and window managers. I generalize them quite purposefully. The point I'm trying to make is that on Linux, there are hardly any well-defined standards for anything beyond system calls. There also are no UI guidelines and there's no single accepted UI toolkit (some apps use Qt, some apps use GTK, some use something else). This leads to overall subpar user experience. Many apps have UIs that make you think before you do something with it. A good UI doesn't make you think, it feels like a continuation of your thoughts right when you see it for the first time. Consistency helps a lot here. (FWIW, the way GUI apps feel and behave doesn't depend much on your choice of desktop environment.)

I don't like walled gardens — I despise Apple's service ecosystem and the app store. I just prefer things to work sensibly out of the box. The only reason I made an Apple ID is because it won't let me download Xcode without one.

Re:Darling: macOS Translation Layer for Linux by LockAndLol on Tuesday October 06, 2020 @07:04AM (#24696483)
OK, a few questions:

- Why do you think are there so many different DEs, window managers and UI frameworks out there?

- How would you go about introducing one singular UI and UX across all of Linux?

- How would you foster competition and innovation in that space?

- Why do you think Apple is able to define and (somewhat) enforce their standards?

Re:Darling: macOS Translation Layer for Linux by cjones26 on Monday October 05, 2020 @09:55PM (#24694080)
That really depends on the distro. It sounds like you're also talking about how Linux was 10 years ago. I've run Mint for the past decade and I personally consider it a fully featured OS which does everything I need it to do. I admit there is some inconsistency in GUIs depending of the software which you use, though that is simply the nature of the beast. The reason Mac is so consistent is simply due to the fact that you're in a walled garden which Apple fully controls.
Re:Darling: macOS Translation Layer for Linux by dis-sys on Sunday October 04, 2020 @11:04PM (#24684189)
why bother following the clearly failed model? ReactOS has been there for more than 20 years, how many people are actually running ReactOS in production?
Re:Darling: macOS Translation Layer for Linux by paulryanrogers on Sunday October 04, 2020 @11:10PM (#24684223)
ReactOS got too ambitious IMO. If they had stopped chasing versions at say XP/2003 then it may have matured more quickly. That said they are getting closer to useable with every release. Like FreeDOS before it I suspect it will fill a niche where Microsoft binaries are too expensive yet compatibility is important.
Re:Darling: macOS Translation Layer for Linux by JdeBP on Monday October 05, 2020 @03:44AM (#24685460)
Not targetting versions beyond XP is what ReactOS does, and pretty much always has to my knowledge. It's explicitly mentioned in its doco that it targets Windows NT 5.2. Indeed, this is the first thing dealt with in the ReactOS FAQ on its wiki.

* https://reactos.org/wiki/ReactOS_FAQ

I found this disappointing at the time that ReactOS was announced, as I recall, because there were a few things that were architected better in Windows NT 6.

Re:Darling: macOS Translation Layer for Linux by paulryanrogers on Monday October 05, 2020 @08:00AM (#24686865)
Thanks for pointing this out. My recollection was inaccurate.
Re:Darling: macOS Translation Layer for Linux by detaro on Sunday October 04, 2020 @11:12PM (#24684235)
... but they are targeting XP/2003?
Re:Darling: macOS Translation Layer for Linux by jeroenhd on Monday October 05, 2020 @02:34AM (#24685122)
If they stopped at 2003/XP then no modern web browser would run on it and the system would be even more useless than it is today. If you want any decent usage out of the system, you need to support a whole bunch of APIs from at least Windows 7 (probably even Windows 8 now that 7 is our of support) because people have stopped compiling for XP ages ago.
Re:Darling: macOS Translation Layer for Linux by paulryanrogers on Monday October 05, 2020 @08:01AM (#24686879)
Looks like they are open to implementing newer APIs in the future. So if the version reported can be spoofed or modern browsers only feature sniff then there is hope.