Live data from Hacker News

We need to document macOS

eclecticlight.co

61–70 of 266 posts

Re: We need to document macOS

#61
> We

That would be Apple's job, and if you're waiting for them to make it easier for third parties to work on the system they think rightfully are theirs alone to develop, don't hold your breath.

Did we all start taking amnesia pills or something? You knew what you signed up for.

Re: We need to document macOS

#62

OT a bit but I think still related. 8 years ago when I switch to OSX I was furious with finder. Tiny window, no hierarchical browsing and the search just doesn't do shit that is useful. I normally default to locate or find now so much that I was using it the other day I was reminded about how much it sucked. It's literally identical (aside from tags and labels) to what it was forever ago and is a terrible paradigm. I…

I love reading these hilariously entitled comments from people who must have either ignored or foregone considering their choice of env years ago while anyone sensible and reasonably intelligent realized how to avoid these issues in the first place. No, you do not get any hand-holding in the world of technology; you can't simultaneously hope for a consumer product that "Just Works^TM" and demand your customization ne…

Listen man, I do plenty of customization. What I'm bitching about here is what I consider to be a lack of innovation and a dereliction on obvious existing, key tools. Finder is a beautiful example of Apple not taking care of it's shit.

I don't need a fucking hand hold. My 3 year old Macbook Air is in my opinion the BEST laptop available. I'm angry that the innovation appears to have ceased from the availible providers and I just can't fathom why.

Just because I used a vernacular you don't appreciate doesn't mean I don't take my work seriously and know how to operate my tools. The second they shape up, someone else delivers me an answer, or I write something to get me out of this platform, there I go. Nothing I'm talking about involved "hand-holding." I want a same priced laptop, with a good GPU, with what I've got now, plus some effort into glaringly obvious old problems. Maybe innovating in a direction that was geared towards a producer and not vibration emojies for a jogging watch. If my math on their income is right both could be possible.

Maybe I'm just naive.

Re: We need to document macOS

#64

When I did some work on porting out product to macOS (so developers could run their server environment locally, though a few loons wanted to actually run macOS on servers), I was immediately struck by how awful and incomplete the documentation was. And, I've been working in the Linux world for a couple decades...where docs are copious but wrong about 50% of the time. In particular, the service launcher (launchd, ment…

> But, I'm kinda baffled why anyone would volunteer to provide free labor to one of the largest and most profitable companies in the world. I give away tons of my time for OSS, but I'm not about to get out and push if I've paid for a luxury car.

> I'd rather put my time into something that is free and open for everyone, including my future self. Actually, the word "rather" isn't strong enough: I would never give my labor to an $820B corporation.

That's exactly what springs to mind. Why should we do Apple's work for them when they are swimming in cash reserves. It beggars belief that anyone would suggest this. Obviously their pain is so great, they're so tightly shackled, their alternatives so limited, that they would rather willingly donate their labor to a wealthy corporation than attempt to take said corporation to task or shock horror jump ship.

Re: We need to document macOS

#65
post #53

OT a bit but I think still related. 8 years ago when I switch to OSX I was furious with finder. Tiny window, no hierarchical browsing and the search just doesn't do shit that is useful. I normally default to locate or find now so much that I was using it the other day I was reminded about how much it sucked. It's literally identical (aside from tags and labels) to what it was forever ago and is a terrible paradigm. I…

Ugh, finder is shit. I've set my default to list view a million times only to see a bunch of folder icons on my screen everytime I double click a directory. I enjoy living in terminal. I'm very mediocre with both find and grep but I'm getting better and it makes me feel cool ;-), heh.

With textexpander, grep, sed, awk, and xargs I macro my way around most of the issues. If you haven't tried TE I highly recommend it. I found it when I started to suffer from some repetitive strain injuries that look like carpal tunnel last year. Being hobbled has actually improved my output!

Re: We need to document macOS

#66
No. It's Apple who needs to do that. This isn't a free software project - lack of documentation is an argument for abandoning the platform, not for starting a community project of doing work for Apple for free.

Re: We need to document macOS

#67

Earlier quoted context omitted.

I mean, I'm not the target audience and I don't have the attachment to OSX as a platform, but if I was gonna expend the energy to document a thing, I'd hope it goes towards a good cause and isn't just free labor for like the richest corp I can think of from the top of my head.

Documentation effort towards OSX would help vastly more people than similar efforts for any flavor of Linux, which nobody plus epsilon uses (except amongst devs). Impact is a big factor in how useful an activity is, even if it's tied to a big company.

> Documentation effort towards OSX would help vastly more people than similar efforts for any flavor of Linux, which nobody plus epsilon uses (except amongst devs).

Documentation effort towards Linux would help get that number up from nobody plus epsilon.

Also, at this point that's just not true because of Android. Most of the userspace is different from normal GNU/Linux distros, but not all: for instance, if your question is "how the heck am I supposed to connect to this WPA-Enterprise network," it's wpa_supplicant under the hood whether you're using Android's network dialog or GNOME's, and documenting wpa_supplicant's abilities and bugs helps Android users just as much as GNOME users.

Re: We need to document macOS

#68

Earlier quoted context omitted.

I love reading these hilariously entitled comments from people who must have either ignored or foregone considering their choice of env years ago while anyone sensible and reasonably intelligent realized how to avoid these issues in the first place. No, you do not get any hand-holding in the world of technology; you can't simultaneously hope for a consumer product that "Just Works^TM" and demand your customization ne…

Listen man, I do plenty of customization. What I'm bitching about here is what I consider to be a lack of innovation and a dereliction on obvious existing, key tools. Finder is a beautiful example of Apple not taking care of it's shit. I don't need a fucking hand hold. My 3 year old Macbook Air is in my opinion the BEST laptop available. I'm angry that the innovation appears to have ceased from the availible provider…

Your delusion that paying "availible [sic] providers" the large price tag they put on their electronics and 'doing plenty of customization' make them "your" tools is the reason I don't take you seriously; "your vernacular" is more an indicator than an issue in that regard.

> The second they shape up, someone else delivers me an answer, or I write something to get me out of this platform, there I go.

The first two are more of the same. The third is just something you're telling me (and yourself?) to try and continue the charade, as anyone capable of taking that option would already (and as I said, did many years ago when they saw the choices in front of them) have done so, and would not be "angry" over what they would see as the obviously financially sensible decision from Apple et al.

Re: We need to document macOS

#69

When I did some work on porting out product to macOS (so developers could run their server environment locally, though a few loons wanted to actually run macOS on servers), I was immediately struck by how awful and incomplete the documentation was. And, I've been working in the Linux world for a couple decades...where docs are copious but wrong about 50% of the time. In particular, the service launcher (launchd, ment…

Maybe the project can get started, add some donation links, and someone from Apple will help them out (with info or docs).

Management probably doesn't even realize this is an issue. Perhaps getting this started will get some visibility on the problem.

Re: We need to document macOS

#70

OT a bit but I think still related. 8 years ago when I switch to OSX I was furious with finder. Tiny window, no hierarchical browsing and the search just doesn't do shit that is useful. I normally default to locate or find now so much that I was using it the other day I was reminded about how much it sucked. It's literally identical (aside from tags and labels) to what it was forever ago and is a terrible paradigm. I…

This sentiment is why I do almost everything in a terminal. I see even people who use mac do everything on the terminal. Whenever someone complains about a UI tool crashing, acting wonky, being slow, my reply is always 1. I can't help you, I don't use that; 2. Just use the terminal.

UI fashions come and go, but the terminal is forever.

Post reply on HN