181–190 of 258 posts
No screenshots for a GUI-centric OS? Seriously?
I wonder if the reason is that it looks really unpolished (there are some screenshots on Imgur). Those sidebars would get your team fired at Apple. If this isn't the final look then I apologise.
Earlier 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
I think are underestimating in general how much work it is. ReactOS has been developed for 23 years and is not in a useable state yet.
>It builds on the solid foundations of FreeBSD Why not build on Darwin which basically forms macOS's core? And how it differs from helloSystem?
Earlier quoted context omitted.
Because modern UX designers consider users their enemy. It's the only explanation I've heard that fits all the data.
It does sometimes seem like they are designing to impress other designers at talks and conferences, rather than to make users happy. But I respect anyone who develops open source end-user software. To say it is thankless is quite an understatement.
Earlier quoted context omitted.
> this is against the terms of the Apple developer agreement. Of course it is Heaven forbid we have any choices at all.
Nobody is forcing you to make ios apps
[0] And it didn't even make sense. I was making industrial equipment repair guide software. The first version of it I made for the Hololens, where it made sense, because, you know, you need your hands free to be able to actually enact the repairs. But you try telling that to a literally corrupt manager.
Earlier quoted context omitted.
I think are underestimating in general how much work it is. ReactOS has been developed for 23 years and is not in a useable state yet.
However ReactOS has a more challenging/bigger goal for a few reasons. It aims to be binary compatible, not just source compatible. Much more of the underlying tech is proprietary while the BSD subsystem on macOS is free for them to use.
Earlier quoted context omitted.
> how hard it is to implement a modern filesystem that won't eat users' data. Why is that so hard? Because of edge-cases? Caching/Timing considerations?
The main problem is simply that people really really really don't like losing their data after they saved it to disk. A simple app that corrupts its in-memory state once a year is probably acceptable. A filesystem that corrupts its on-disk state once a year is pure garbage. You basically need to aim for zero bugs. How hard this is, it depends on the filesystem. Something like FAT, for example, is pretty much designed…
One thing I wonder is why they're using FreeBSD as a base and not Darwin. I use FreeBSD myself and it's great, but if you're really going for Mac compatibility I would use the same kernel considering it's FOSS.
Could be something else, I know there were projects attempting to do things with Darwin in the past and none were successful.
Earlier quoted context omitted.
The core of MacOS is Darwin which is open source. Based on the MACH/XNU kernel and *BSD. So any MacOS clone would start with using Darwin code.
Emulating macOS at the Darwin layer is not necessary and often not advisable (see: GNUstep).
Earlier 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.
> Hard to see how this can be done legally. Why? Things like Wine and Proton exist and Windows is proprietary.
There is absolutely no equivalent for macOS frameworks. GNUStep is a tiny part of the picture, and in addition has not kept up with the fairly radical changes that Apple has introduced to the frameworks that GNUStep does correspond to.