For me it just depends on the project. Sometimes one or the other performs better. If I am digging into something tough and I think it's hallucinating or misunderstanding, I will typically try another model.
what is it about it that you hate and that makes you associate it with linkedin? I don't hate it, but I feel the linkedin comparison. maybe because of the many linebreaks?
I will say the FreeBSD handbook is such a breath of fresh air compared to other OS documentation. Everything is easy to find and well formatted. Same goes for the OS internals themselves. It's just a cohesive project altogether.
You're seeing the benefit of the cathedral model right there: a centralized, architected approach yields unified documentation, whereas the bazaar is inherently fragmented.
Back in college I spent some time translating portions of it to Russian. It was super easy to work with the project on that. I honestly have no idea if any of my contributions are still a part of it but I am really glad I did that.
It wasn't an absence of a market. Those of us that had to manage OSX Server soon found out the software was marked by several high-profile bugs, technical debt, and a perceived decline in reliability. I migrated a large number of Macs to Ubuntu Server software. The hardware was great.
I fear the quality of macOS is deteriorating today in the same manner than befell OSX Server.
Right, but I could see an alternate timeline where OS X Server took off, and within a decade took a path similar to Windows Server (pared down services, headless flavor, etc)
I am not sure iOS popularity would justify macOS as a server. What would be the use case? It's not app development; that is done just fine on the standard desktop macOS. It's not backend; that is done just fine on Linux servers, even in Swift if that's your thing.
reply