121–130 of 148 posts
Maybe someone more familiar with operating systems kernels can answer this: Is Darwin really all the exiting? It is different from both the BSD kernels and Linux, but less so than Windows. Other than the ability to run macOS applications (assuming you can clone the libraries and APIs from macOS) is there some benefit of Darwin that I'm not seeing?
Earlier quoted context omitted.
And now that I have walked over the whole website: Why not a single screenshot anywhere?
Because there is nothing to screenshot. Others have speculated that the UI looks like ass. Some have said "Mac OS window chrome with Win 95 GUI controls. Yeah, no. See for yourself. This is the most recent release on their github page. I considered posting it to my Youtube account to gain some of that much-needed eyeballs and attention, but it's 11pm and I'm not doing that shit, I'm not playing that game. Here is wha…
Earlier quoted context omitted.
XNU has some interesting features. It’s Mach based, so it has Mach ports, which are an IPC system that is fairly heavily used by macOS. It has DriverKit, which is a C++ framework for drivers that’s got morecsuppirt than the usual Unix driver model. Mach-O does more than ELF, and enables the two-layer namespacing that makes macOS able to manage dynamic linking dependencies better than ELF. Nothing really earth-shatter…
> Mach-O does more than ELF, and enables the two-layer namespacing that makes macOS able to manage dynamic linking dependencies better than ELF. I've always admired that mach-o supports fat binaries.
Earlier quoted context omitted.
Man I used to develop SAAS software using Cappuccino. Since I knew Objc (and JS/CSS) really well it was such a beautiful system for development. I'm sad it never went anywhere
May I ask what made it special? It does look awful "elegant" and well put together ...
Cappuccino improved upon javascript by using a different language (objective-j) that added many features js didn't have, and it used the same (mostly) well-honed api as AppKit. In comparison to other js UI frameworks of its time, it was lightyears ahead.
Maybe someone more familiar with operating systems kernels can answer this: Is Darwin really all the exiting? It is different from both the BSD kernels and Linux, but less so than Windows. Other than the ability to run macOS applications (assuming you can clone the libraries and APIs from macOS) is there some benefit of Darwin that I'm not seeing?
Most kernels are kind of the same really. Some have slightly fancier inter-process communication. Leading to my all-time favorite YouTube video, an explainer on Android IPC cut like a spy thriller. I'm not even joking: https://www.youtube.com/watch?v=Fb4UoqXPEtI
Earlier quoted context omitted.
not saying $TECHCO doesn’t know about X project. i’m just saying that if the average person doesn’t know about it, it’s unlikely to get shut down, as it poses no threat.
Maybe. But Microsoft get the bulk of their licensing from enterprise offerings. And Windows comes preinstalled on consumer machines anyway. So I don’t think there’s any risk of ReactOS becoming a problem for MS. And with Apple, they’ve always approached the market as a hardware company first and foremost. Which is why macOS has always been free vs Windows which, until recently, was not. Platforms like Linux was alway…
I swear I see this exact kind of project every year under a new name
Earlier quoted context omitted.
Maybe. But Microsoft get the bulk of their licensing from enterprise offerings. And Windows comes preinstalled on consumer machines anyway. So I don’t think there’s any risk of ReactOS becoming a problem for MS. And with Apple, they’ve always approached the market as a hardware company first and foremost. Which is why macOS has always been free vs Windows which, until recently, was not. Platforms like Linux was alway…
You may be broadly correct, but “macOS has always been free” is definitely not true: all the Big Cat releases of Mac OS X were paid-for, right up until MacOS X 10.8 “Mountain Lion” released in 2012. Only later, from Mavericks in 2013 onwards, were upgrades free. And further back in time I remember buying a software update for my first-generation iPod Touch up to par with the first-generation iPhone way back in 2008.…
But i didn’t realise Apple used to charge for OS upgrades. So thanks for the correction there.
Earlier quoted context omitted.
May I ask what made it special? It does look awful "elegant" and well put together ...
when Cappuccino was written, Apple was still using the Objective-C + AppKit stack. It had been honing this stack for years, every WWDC brought useful and deliberate improvements. Back then macOS development was much more niche (and tech in general). They could take their time. MacOS releases happened every couple of years, not every year. Not the kind of outcome we have nowadays where changes are rushed because of de…
PS: Compare to today, with code slop (and good agent-mediated code: It also increases overall speed).-