They'll probably fail, but that's not the right criterium to apply to most projects...
Airyx OS
71–80 of 258 posts
Re: Airyx OS
#72Airyx’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/
"0.2.2 is the first build of Airyx based on the helloSystem components and FuryBSD LiveCD installer. It can be run or installed from the ISO and should have better hardware support, in addition to the slick helloSystem desktop and applications." via https://github.com/mszoek/airyx/releases
Re: Airyx OS
#73This 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
#74This 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?
> If you dont want to eat meat, why try and replicate the taste, texture and sensation of eating meat?
What is this taste, texture, and sensation of meat in regards to bacon you're talking about? Bacon is the opposite of the actual taste, texture, and sensation of meat. It's cooked, salted, and processed to give it that taste, texture, and sensation.
It's the same with people making fun of plant-based burgers and sausages. Well, guess what, burgers and sausages don't exist in nature, neither as meat nor plant. Well, actually... Cucumbers and a few other plants seem quite like sausages. Anyways. The burger, sausage, and bacon form factor is what makes it attractive. It's why people have liked it for so long, and why people like it still when they switch to a plant-based diet.
I guess it's the same reason why some people are into Airyx OS.
Re: Airyx OS
#75More 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
Why is that so hard? Because of edge-cases? Caching/Timing considerations?
Re: Airyx OS
#76This 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?
I agree. It doesn't make particular sense. Even if you aren't a complete fanatic about MacOs UI, you wouldn't choose FreeBSD as a base, but rather Linux, which has a lot of advantages for the average user, I'd say.
Re: Airyx OS
#77This 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?
And even more absurd to use this kind of argument in the software world. Imagine back then... „If you don‘t like Unix, why...“, or the first GUI implementations on Linux trying to achieve what apple or microsoft did... Oh well, what our hacker world would be like if more people thought that way...
Sorry, not trying to offend, but these projects are what I live for. „Stickin‘ it to the big guys“ - after all, we are hackers, aren‘t we?
Re: Airyx OS
#78Earlier quoted context omitted.
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
If you're on a Mac now, try quickly hitting the menu bar items (at the very top edge of the screen) vs the tabs (below the menu bar, not quite at the edge).
I find the difference quite significant.
Peculiarly, this convenience would flip to the opposite if the screen were touch-enabled!
Re: Airyx OS
#79Pretty 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.
Re: Airyx OS
#80Why do you think people want this?