Live data from Hacker News

Darling – MacOS translation layer for Linux

darlinghq.org

61–70 of 274 posts

Re: Darling – MacOS translation layer for Linux

#61
post #43

Earlier quoted context omitted.

And that is related to which part of my post, because I do not see the connection? I didn't mention Windows. And good luck with wrestling with Windows doing UNIX things. It had it, but it was not comparable to Linux and BSDs. Now it is better situation, much better, but still I would rather spin some BSD based system in VM, than try and use Ubuntu through WSL.

SUA(SubSystem for Unix-based Applications) is litterally a BSD fork...

You mean the Unix subsystem they made just to claim POSIX compatibility, that they totally abandoned in recent Windows versions?

Re: Darling – MacOS translation layer for Linux

#62
post #21

Earlier quoted context omitted.

That simply is not true. Most of the people that likes commodities of UNIX, nice UI and long battery life in combination with nice hardware uses Macs. Even people who do not do any iOS development. There is no such thing as Mac Dev tools, (maybe just iOS related but there aren't many that you do for that process besides Xcode). I use my Mac like I used Linux and FreeBSD, package manager check, nice terminal check, Em…

No, Windows had an Unix subsystem since forever, and WSL helps switchers more than ever actually.

Windows Services for Unix has been discontinued for a while, so "since forever" is just flat wrong.

And who in the hell ever developed for it anyway? That was a niche, forgotten product if there ever was one.

edit: maybe you should keep up with stuff more if you're going to defend it so much, it was deprecated like 7 years ago

https://en.wikipedia.org/wiki/Interix

Re: Darling – MacOS translation layer for Linux

#63
post #49

I am hoping that with cross platform Swift we can start seeing more libraries to help us port Mac apps to Linux. I am a Mac developer but I'd love to make stuff available on Linux. I really like Linux as a backup plan, in case Apple totally drops the ball on professionals on the Mac. The Linux desktop is getting pretty good, but it lacks well designed high quality GUI applications. If porting to Linux was done easier…

> it lacks well designed high quality GUI applications. If porting to Linux was done easier that could change. Fundamental to most peoples complaints about desktop Linux applications is the lack of look and feel cohesion across all permutations of distro, desktop, and toolkit. Wine applications using the Windows APIs look like complete garbage and fit in nowhere. The same would be true of OSX Cocoa apps - they wouldn…

I suppose it's useful when almost everything works, but that one thing that you absolutely need isn't otherwise available.

Re: Darling – MacOS translation layer for Linux

#64

> Why “Darling”? >The name Darling is a combination of “Darwin” and “Linux”. >Darwin is the core operating system OS X and iOS build on. If that's the case, why not Darlin? But then, I'm southern so that's why it makes more sense to me.

I was looking at emacs documentation the other day and thought that RMS is probably right that Linux should be called GNU/Linux. In that case, newcomers to this project might ask "What's GNU Darlin?

I think nowadays we should start to use the name SystemD/Linux

Re: Darling – MacOS translation layer for Linux

#65

This is neat, but I can't think of a single non-GUI tool on OS X that I need or doesn't have an equivalent in Linux...

How about "packagebuild" and "productbuild"? They build OSX packages. You could use a linux server to build DEBs, RPMs, and OSX packages without using OSX.

Ever since the gpl bomutils project you can, here's a nice tutorial:

http://bomutils.dyndns.org/tutorial.html http://hogliux.github.io/bomutils/tutorial.html

Re: Darling – MacOS translation layer for Linux

#66

It's a shame that you can't run a container with MacOS installed and just run the apps natively. Unlikely to ever happen though. You'd have to run the MacOS kernel and Mach concurrent with the Linux kernel without virtualization (something I am not sure is possible). At that point, you might as well just bite the bullet and run a VM.

I'd be happy enough if I could run the VM.

You can: https://news.ycombinator.com/item?id=12556609

Re: Darling – MacOS translation layer for Linux

#67

This is neat, but I can't think of a single non-GUI tool on OS X that I need or doesn't have an equivalent in Linux...

mediafilesegmenter and mediastreamvalidator used for creating and testing M3U8 (HLS) files. You can of course use open or closed source alternatives, but they're fairly shitty in comparison to the mac native tools. Last time I tried mediafilesegmenter had a dependency on some of the core audio libraries that were missing under Darling.

I've had success with segment filter for ffmpeg. Yes it's more complicated, but I wouldn't describe it as you did.

Re: Darling – MacOS translation layer for Linux

#68

It's a shame that you can't run a container with MacOS installed and just run the apps natively. Unlikely to ever happen though. You'd have to run the MacOS kernel and Mach concurrent with the Linux kernel without virtualization (something I am not sure is possible). At that point, you might as well just bite the bullet and run a VM.

I'd be happy enough if I could run the VM.

Do you mean legally, or at all? Because if it's "at all" I believe there is a very vibrant community who have a lot of tutorials for doing that

Re: Darling – MacOS translation layer for Linux

#69

> Why “Darling”? >The name Darling is a combination of “Darwin” and “Linux”. >Darwin is the core operating system OS X and iOS build on. If that's the case, why not Darlin? But then, I'm southern so that's why it makes more sense to me.

I feel like "Darlin" only sounds "cute" when said with a southern accent.

Re: Darling – MacOS translation layer for Linux

#70
post #55
post #21

Earlier quoted context omitted.

No, Windows had an Unix subsystem since forever, and WSL helps switchers more than ever actually.

Except neither of those work worth a damn. You can't even run stuff like MSBuild or Sublime Text from the WSL.

MSBuild/.NET Core work fine on WSL now.
Post reply on HN