Poked around a little bit on the livecd system, screenshots: https://imgur.com/a/OsxT3GI
Airyx OS
51–60 of 258 posts
Re: Airyx OS
#52Earlier quoted context omitted.
Ubuntu's Unity was a lot more macOS-like with the default global menu bar, then they gave up on it :( Gnome doesn't even have a menu bar anymore, preferring apps use a single hamburger menu.
Unity was designed more for touchscreens, so that Ubuntu could make smartphones based on it. It didn't work out apparently.
Unity was originally designed for netbooks with limited screen real estate.
Re: Airyx OS
#53Pretty interesting project. However, who really wants a "global menu bar". It made sense for the original mac, when people just used one app at a time. And it's left in the current MacOS for legacy reasons. But now people usually have multiple 27" monitors. So, instead of having menus where the app is, you need to move the mouse all the way to the top and then back. Im not sure why anyone would want to replicate it.
One advantage of a global menu bar is that items at the top of the screen are effectively an infinitely large target, so you can rapidly move the mouse to them without worrying about overshooting: https://en.wikipedia.org/wiki/Fitts%27s_law
Re: Airyx OS
#54More information and motivation in the git repo[0], the link to which I didn't spot easily in the site header. The main design goals are: * source compatibility with macOS applications (i.e. you could compile a Mac application on Airyx and run it) * similar GUI metaphors and familiar UX (file manager, application launcher, top menu bar that reflects the open application, etc) * compatible with macOS filesystems (HFS+…
> compatible with macOS filesystems (HFS+ and APFS)
How far along is this? I think she's underestimating how hard it is to implement a modern filesystem that won't eat users' data. I've been working on a Linux APFS driver[0] for several years, and it's not fully functional yet. It's a pity that she is working with FreeBSD, or it could have been of use to her.
Re: Airyx OS
#55Given the amount of stuff GNUStep is lagging behind macOS Frameworks after three decades, let alone the Swift ones, what is this for?
Re: Airyx OS
#56Pretty interesting project. However, who really wants a "global menu bar". It made sense for the original mac, when people just used one app at a time. And it's left in the current MacOS for legacy reasons. But now people usually have multiple 27" monitors. So, instead of having menus where the app is, you need to move the mouse all the way to the top and then back. Im not sure why anyone would want to replicate it.
One advantage of a global menu bar is that items at the top of the screen are effectively an infinitely large target, so you can rapidly move the mouse to them without worrying about overshooting: https://en.wikipedia.org/wiki/Fitts%27s_law
But you want to select a specific menu and not just click somewhere on the whole menubar. So, it's no longer an infinitly large target and you need precision
Re: Airyx OS
#57Earlier quoted context omitted.
> source compatibility with macOS applications (i.e. you could compile a Mac application on Airyx and run it) Hard to see how this can be done legally. The libraries (sorry, Frameworks) that make up the user-space runtime for macOS are all proprietary. There's no replacement for the most important parts of it.
Sure there are (for some definition of "most important parts). Take a look at GNUstep for a start. Some MacOS frameworks like WebKit are also open sourced from Apple itself. As an example of how this works in practice, the disassembler/decompiler Hopper has both MacOS and Linux versions that are compiled from the same code. Now, how successful they'll be extending the open source frameworks to made this useful in com…
>Some MacOS frameworks like WebKit are also open sourced from Apple itself.
It had to be, it was forked from KHtml, which was GPL.
Re: Airyx OS
#58More information and motivation in the git repo[0], the link to which I didn't spot easily in the site header. The main design goals are: * source compatibility with macOS applications (i.e. you could compile a Mac application on Airyx and run it) * similar GUI metaphors and familiar UX (file manager, application launcher, top menu bar that reflects the open application, etc) * compatible with macOS filesystems (HFS+…
> compatible with macOS filesystems (HFS+ and APFS) How far along is this? I think she's underestimating how hard it is to implement a modern filesystem that won't eat users' data. I've been working on a Linux APFS driver[0] for several years, and it's not fully functional yet. It's a pity that she is working with FreeBSD, or it could have been of use to her. [0] https://github.com/eafer/linux-apfs-rw
> It's a pity you are working with Linux, or it could have been of use to her.
FTFY
Re: Airyx OS
#59This reminds me of vegan bacon.
If you dont want to eat meat, why try and replicate the taste, texture and sensation of eating meat?
If you dont want to use macOS, why try and replicate the taste, texture and sensation of using macOS?
Re: Airyx OS
#60Earlier quoted context omitted.
Isn’t that dependent on your private key stored on Apple’s equivalent to a TPM? That said, lots of IDEs let you build on Windows/Linux, they just use a daemon running on a headless Mac on your LAN (or a rented “cloud” Mac) to do the code-signing part.
No, building software for iOS is possible on other platforms although this is against the terms of the Apple developer agreement.
> this is against the terms of the Apple developer agreement.
Of course it is
Heaven forbid we have any choices at all.