Live data from Hacker News

We need to document macOS

eclecticlight.co

261–266 of 266 posts

Re: We need to document macOS

#261
post #70

Earlier quoted context omitted.

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.

If you are just using bash for everything why don't you just use a tty instead. Jokes aside, Isn't linux a better idea if Bash is all you need? The only difference is that Mac has more proprietary stuff that don't support linux. If that's not an issue linux is much better.(IMO)

Well, I don't use bash (zsh nowadays) for literally everything. I also use the browser, etc. My VIM isn't in the console, I use the GUI, so I can have more colours and better fonts. But in general, when I can, I control things via the least complicated interface possible - plain text commands.

My gripe isn't that there's anything inherent in GUIs that makes them a less reliable interface than the terminal, it's that getting them to the same level of dependability appears to take more time. And, for all its warts, the fashion du jour of making a GUI by just dumping HTML+JS in a browser instance is something I whole-heartedly support, because it gives application developers probably the simplest (today) wide-spread technology to build GUIs with. It almost always results in applications that consume too much RAM, too much CPU, aren't native-looking, and there are probably other easy GUI-building solutions (QML?), but at the same time they're trivial to edit, quick to write, and there is a ton of documentation and a large community around them. I really hope that electron becomes a standard installable application platform in the near future.

Re: We need to document macOS

#262
post #208

Earlier quoted context omitted.

IIRC Max now works at Apple and is responsible for Swift's package manager.

I think he left sometime last year https://changelog.com/podcast/232 they start talking about his departure from Apple at 55 min and 26s, unless he went back recently

Ah.

Re: We need to document macOS

#263

Earlier quoted context omitted.

I have not used smart searches, and now I'm reading about them and it does look pretty cool. But that search bar should give me something sort of close to what I'm looking for in a couple strokes and it really doesn't. I can specifically call out what my issues are with Finder. - Where is my fucking folder tree. There was no reason to take it away other than "thinking different" just like the backspace key. Super spe…

A lot of these just seem like you aren't familiar with the Finder, did you check the menus, preferences, or do a web search for Finder tips? - No folder tree you are correct. I don't miss it personally. Gotta just deal with this one I think. - What way specifically does the search not work for you? It's incredibly powerful and you can search by file name, content, file type, creation date, etc. - It should save the w…

Thanks for your point for point response mate. I'm going to take a look at all of it.

Sorry for the points that were unclear. They are general frustrations that I've had. This looks like it'll help with a lot!

Re: We need to document macOS

#264

Earlier quoted context omitted.

I have not used smart searches, and now I'm reading about them and it does look pretty cool. But that search bar should give me something sort of close to what I'm looking for in a couple strokes and it really doesn't. I can specifically call out what my issues are with Finder. - Where is my fucking folder tree. There was no reason to take it away other than "thinking different" just like the backspace key. Super spe…

> - It appears to be designed to keep you away from the system HD. More and more so with every release. I want to look at my filesystem, it it's entirety, easily and without using "go". One "pro tip" is use "Cmd + Up arrow" to navigate one level above current folder. Also, Finder creates ".DS_Store" files in each folder, which remembers current folder display. If you want to enforce say "List files" view everywhere,…

Thanks for the pro tips homie! I'm taking this and some of the other responses and making a cheat sheet. You guys have genuinely improved my situation.

Re: We need to document macOS

#265
post #49

Earlier quoted context omitted.

A beefy windows workstation or laptop to cover Adobe & DAWs + VMWare for Linux. With fullscreen VMWare and open-vm-tools I can barely notice that it doesn't run bare metal, and i can keep different distros at hand for different purposes.

I bought Windows 10 Pro last year and had really high hopes for it after the Ubuntu shim was introduced. Windows is a fucking nightmare for anything involving producing audio at a pro level. The Ubuntu shim does not solve what I need even though it's a nice add. The real kicker is that STILL many errors produce a window where I can't even fucking copy the output. Why that is still a feature, I have no idea. That coup…

FWIW, Ubuntu Studio rocks for audio guys.

Re: We need to document macOS

#266
post #96

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.

I guess the problem is that Apple don't need to do it; lots of people would like them to do it, and maybe they should do it, but it's not hurting their bottom line much so they can just continue as they are. Unless a whole heap of customers suddenly decide to buy different laptops instead over it, but I'd not be betting on that.

Arguably, this might happen in the long run. They might slowly lose dev over the years if they neglect documentation, which will eventually hurt the app ecosystem. Eventually, that'd affect user.

Very hard to say if the problem is serious enough yet though.

Post reply on HN