> Drag and drop app install and uninstall - no package manager, no installers
Awful
Airyx OS
121–130 of 258 posts
Re: Airyx OS
#122I'd love to throw an investment into something like this with GUI, marketing and supply chain resources to build a solid computer under $300 for a developing world.
Go up against Fuchia and Google hardware in less time and with more clarity.
Re: Airyx OS
#123Earlier quoted context omitted.
> It's a pity you are working with Linux, or it could have been of use to her. FTFY
Oh, I wasn't trying to diss FreeBSD. It would probably have been better to write my driver for fuse to make it portable, but it's too far along at this point.
Out of interest, why can't file system implementations be portable? A shared core that exists as a library that can be tested in userland, and which can then be used by a lightweight shim that implements the kernel-facing interfaces. But I haven't seen any file systems implemented this way.
Re: Airyx OS
#124Earlier quoted context omitted.
I probably missed a lot of things, but didn’t Gnome already achieve this? Weren’t most of the people behind its design from Apple?
The developer of Hello would disagree with you: https://medium.com/@probonopd/hellosystem-three-layer-ux-des...
Funny how he complains about missing the German language setting and proposing a new system where my language (Dutch) is completely missing... I will stick to Gnome...
Re: Airyx OS
#125As a long time windows user, Linux Mint greatly eased my transition from Windows to Linux and now I love it so much that I am never going back to windows again.
Such projects help reduce a lot of friction for people who want to switch but need a little help to make the jump.
Re: Airyx OS
#126Earlier quoted context omitted.
> 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 that she is working with FreeBSD, or it could have been of use to her. I suppose FreeBSD made more sense as a base considering MacOS is derived from BSD.
FreeBSD differs quite substantially from the XNU kernel used by MacOS because XNU is based on Mach, and it was forked (Edit: from 4.3BSD) in 1988 - before Linux even existed.
The XNU kernel does not have a stable syscall ABI so perhaps it doesn't matter if the syscalls are different because the implementation of libSystem can convert as appropriate in userspace (see also: WINE).
Re: Airyx OS
#127Airyx’s developer may want to say hello to the developers of Hello, who are doing something very complementary to this with UX—and are quite far along already. https://hellosystem.github.io/docs/
If any Hello devs are here, I just want to point out that I was interested in using their interface, until I noticed that the window titles are not centered based on the window but on the space between the window buttons and the window (this is on the website). That put me off the whole website (which is fast judgement on my part, but hey I've got stuff to do). Does anyone else here agree?
oh, why did you point that out to me!, now it's driving me crazy.
Re: Airyx OS
#128Earlier quoted context omitted.
Oh, I wasn't trying to diss FreeBSD. It would probably have been better to write my driver for fuse to make it portable, but it's too far along at this point.
Out of interest, why can't file system implementations be portable? A shared core that exists as a library that can be tested in userland, and which can then be used by a lightweight shim that implements the kernel-facing interfaces. But I haven't seen any file systems implemented this way.
The irony is that most of the newer ones in Linux are written that way, just nobody writes a FUSE binding to them. For example, both Btrfs and XFS contain fully functional pure-userspace implementations of the filesystem inside their userspace code (libbtrfs and libxfs both contain the complete filesystem code), but nobody has written a FUSE binding to either.
Btrfs' implementation is even used to do most of the functionality in the tools (like send/receive) rather than using the kernel to do it (in order to minimize context switches that reduce I/O performance).
Re: Airyx OS
#129No screenshots for a GUI-centric OS? Seriously?
This is incredibly common. Why would you develop anything and then not provide screenshots? Even for CLIs screenshots are useful!
What's the first thing you see on Apple's Big Sur landing page[1]? A big fat screenshot!
What about Windows 11 preview[2]? Yep, screenshots!
I can't think of a single time when the first thing I want to see on a landing page (or 1 click away) is not a screenshot or a demo.
[1]: https://www.apple.com/macos/big-sur/ [2]: https://www.microsoft.com/fr-fr/windows/windows-11
Re: Airyx OS
#130Pretty 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.
I actually find the metaphor quite useful–as a developer I can develop a GUI application utilizing a common menu metaphor but _not_ always have a window open; essentially an application is a 'toolbox', presenting its tools via the global menu, and documents/'work' appear as windows. For context, I used Windows all my life before switching to Mac about six years ago, and I find this makes a lot more sense than one menu per window, where application developers often like to go their own way and implement their own menu metaphors.