News for hackers. Stuff that matters.
Re:We need to document macOS by stuntkite on Sunday August 13, 2017 @05:47AM (#15002268)
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 looked around for a bit for some help on refining the search sensibly and nothing in the OS helped (back on topic!). I've been using a great replacement for Finder called PathFinder that does everything Finder should do, but you can't swap it out. All the native places I access Finder are important inroads. They used to have instructions to hack it but apple shut them down.

I feel more and more like UI and usability innovation totally ate itself and died at maybe a specific moment in time ~6 years ago. Where did the people and companies go that do cool new things? Are the giants on their laurels long enough yet to get eaten? I'd switch totally to Ubuntu or Mint for my desktop work, but I do things that require the adobe suite, I need a trackpad that works as well as the mac one without fighting it, and I want to just solve problems, not fiddle with barely supported gizmos for weeks.

Did we reach the absolute end of all we can do with this juggling of rectangles that display and accept text and now we just get everything that matters to a power user stripped off for the sake of what "most users care about"? I really don't think we have.

I'm still pissed and I still have no answers. My kingdom for a $3000 laptop that "Just works" and helps me murder code, deployment, graphic arts, music, and still loads HBONow.

Re:We need to document macOS by codyb on Sunday August 13, 2017 @07:01AM (#15002424)
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.

Re:We need to document macOS by givinguflac on Sunday August 13, 2017 @09:18AM (#15002791)
FWIW, I've never had that issue. Are you aware it sets the view type for each folder? It makes sense if you want to view different files in different ways. If you want to set all views to list system wide, you can set list as default in the view menu. Depending how you've set other folders you may need to nuke view settings, by it sounds like that won't be an issue for you. Spend a minute to learn how your tools work man. https://howchoo.com/g/mzuxyjqyzmy/how-to-set-the-view-option...
Re:We need to document macOS by stuntkite on Sunday August 13, 2017 @07:37AM (#15002512)
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 by pampa on Sunday August 13, 2017 @06:31AM (#15002364)
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.
Re:We need to document macOS by stuntkite on Sunday August 13, 2017 @07:07AM (#15002437)
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 coupled with how they manage fixes/updates and a general distrust for the system being close to secure... It just didn't work out.

I wanted to buy that giant drafting table computer with the knob and say fuck it to the MBP. I went to look at it and bought another kinect one day, and what felt like an omen, their windows run point of sale system that tries to hide in the desks like the apple store failed so bad at taking my card that the guy had to use two different work stations and literally was "turning it off and on again" with both his card swiping windows mobile phone and the computers.

I feel like my future is in some sort of hand rolled main LXD or CoreOS or the like, that quickly composts whole systems locally and in the cloud but also easily remote desktops to local Mac and Windows machines. I have ideas in my head and a bit in code for a bare bones graphical interface that renders a graph that I can attach arbitrary points to that go to systems, API, terminal instances, containers, etc. I can weight the node connections and also record weight on paths based on frequency of traversal enabling automatic access shortcuts. Of course OSX is close to impossible to run virtualized, which is stupid as hell. Actually if it could without a larger time investment than my full time job that might solve all of my problems.

I don't know, I still need all of the systems that are out there... but I think it's time to put a top layer interface on it that gives me them and more. Setting up a springboard for something that doesn't sit around waiting for big providers to bless me with mana from heaven while they wave their dicks in my face.

Here's an example of a nerfed version of what I'm talking about as an OS supervisor UI that I'm using for a lesson series on Docker [https://www.dropbox.com/s/be4lh1015y305jr]. There is nothing about it that's clean or safe to operate, but I just wanted to prove it. In the current version you can select a node and drop to a terminal inside of a container. Also, I've added support for API nodes auto generated from graphql and REST (if you write the schema). I think it proves the concept. The next step is the pullback to whole systems I guess.

Re:We need to document macOS by anonymfus on Sunday August 13, 2017 @08:34AM (#15002658)
> 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.

BTW a standard way to do it is to just press Ctrl+C in such window without any text selection or context menu. Because such messages could be shown when system has no resources to create context menu or text selection, and that was very important in 16-bit days.

Re:We need to document macOS by delinka on Sunday August 13, 2017 @08:48AM (#15002695)
Let me klingon to the thread with this:

It's 2017 and I still can't use the keyboard to copy and paste from and to a Windows command line window...

Re:We need to document macOS by hungerstrike on Sunday August 13, 2017 @11:03AM (#15003166)
Yes you can. Try it out.

Windows has better keyboard accessibility than any other desktop OS.

Re:We need to document macOS by DanBC on Sunday August 13, 2017 @08:50AM (#15002702)
Ctrl C and Ctrl V works in Windows 10 command prompt.
Re:We need to document macOS by stuntkite on Sunday August 13, 2017 @09:07AM (#15002751)
Also if you're not quite ready to kill yourself while using the windows command prompt. Enjoy a powershell.
Re:We need to document macOS by rpeden on Sunday August 13, 2017 @09:25AM (#15002808)
You'd probably enjoy Cmder[1]. Everything works really nicely, it supports multiple tabs, and you can download a version that includes most of the Unix commands you know and love.

[1] http://cmder.net/

Re:We need to document macOS by majewsky on Sunday August 13, 2017 @05:00PM (#15004904)
> you can download a version that includes most of the Unix commands you know and love

Is it the actual Unix commands that I actually know and love, or just 25-year-old parodies like on macOS? (I've stopped keeping track of how often my bash scripts broke on macOS because I was giving some switch to a coreutil that was introduced less than 25 years ago.)

Re:We need to document macOS by krallja on Sunday August 13, 2017 @10:52AM (#15003108)
Alt+Space E P
Re:We need to document macOS by stuntkite on Sunday August 13, 2017 @08:47AM (#15002689)
I'm sure your right. The fact that they haven't updated that and I've been in *nix/OSX for 8 years now made my frustration point maybe lower than it should have been. Then the next thing I'm doing is trying to use cmd and powershell and my hair falls out.

But this is great info and will definitely keep be from cursing quite as much next time I'm MS admining.

Re:We need to document macOS by Roboprog on Sunday August 13, 2017 @02:42PM (#15004243)
I hear you about the audio part. I do electronic music as a hobby - I'm not much of a keyboard player, but I do a lot of editing and tweaking using a digital audio workstation program (DAW).

Whenever I look for stuff in user forums, it seems like it's always the folks on Windows who are having a devil of a time getting audio drivers and stuff to play nice. I can't imagine dealing with all of the nagware popups and such on Windows, either, when trying to run a song. Sounds like the kiss of death if you were ever performing.

I have been using Linux since 1995, but switched over to OSX (Macs) about 5 years ago. Commercial audio products generally don't work on Linux. Maybe you can get Reaper to work under WINE, but good luck getting any licensed soft-synths to run (maybe, but I never tried). I'm sure you can "muzzle" some of Windows more annoying nagging and such, but I have other things to do than get an MSCE cert - paying triple for a laptop to Apple every 5 years or so turns out to be cheaper and faster than keeping up with MS internals :-(

Back to the main topic: I've developed a vested interest in the last few years of seeing OSX continue to thrive. I hope Apple doesn't kill it by continuing to make reckless changes to the hardware and/or software.

Re:We need to document macOS by mmjaa on Thursday August 17, 2017 @11:57AM (#15037911)
FWIW, Ubuntu Studio rocks for audio guys.
Re:We need to document macOS by oscii on Sunday August 13, 2017 @08:22AM (#15002620)
It probably depends on a personal workflow, but for me, Finder works perfectly, and I really miss it on Linux. I have a reasonably organized directory structure, and I navigate and do basic tasks like copying mostly using just a keyboard. I remember directory names and I just start typing their names and the Finder goes to them (actually, most file managers have this feature). Occasionally, I do 'ls | grep' or 'find' from the console to find some specific stuff (I have Spotlight disabled).
Re:We need to document macOS by givinguflac on Sunday August 13, 2017 @09:13AM (#15002775)
I agree. Years ago Finder left much to be desired, but with all the updates of the last few revisions I'm not left wanting for anything.

People complaining about searching likely haven't tried smart searches, it's awesome.

Can anyone specifically call out what their issues are with Finder besides "it sucks"? I really feel that I'm missing something here.

Re:We need to document macOS by stuntkite on Sunday August 13, 2017 @09:41AM (#15002861)
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 special guys.

- Search bar does not behave in a way that I think comes close to useful for quick search.

- Why does the window default to something so small and not have an obvious way to set the default spawn size to something reasonable. At this point it should be context aware.

- I don't want more windows, I want tabs too.

- The sliding cell browsing is cumbersome, it sometimes forces you into a folder when you are trying to be in it's parent, it limits your view of your total file list, and in this view there is no way (that I know of) to utilize ordering without the dropdown, so you are stuck with hitting the first letter of the file you think might be there to try to get there quick.

- let me make symlinks from the UI.

- The list view is great for the most part, but since you don't have a tree you have to either loose your browsing context to move to a new folder or you have to open a new window... and it will be too small. Then when you try to drag things into the new window, that probably defaulted to the sliding cell view floating around to get where you want to go will inevitably have you dropping the file somewhere bad. This was the most egregious before Lion when "cut and paste" did not exist. You could enable something that called itself that but it didn't do it and used the trash? Mostly it was just delete.

- I can't preview a file in the list view without hitting space and blocking my view of my context.

- 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".

- Because you can ONLY use finder for getting files from an application you are stuck with usually a default view that is just a directory dropdown. Then you open it up and it's the slider cell. Then you get trapped and you can't go up a single directory so you have to go to a directory that you used recently, hopefully.... if not you have to go to you user root and navigate down a train.

- If you're gonna be designed to keep normal users "safe" then maybe let me have a button that does "open ssh in directory."

- Drag and drop file copying is laggy as fuck and produces constant problems with relocating files. It's always been the same level of unpredictable and now I'm just trained to sit there and wait for the green +. If the UI is going to be so restrictive and drag copy centric, then this should be like lightning.

- Let me use cli applications from the UI. A right click is fine, a button is ok, a hot key is better. This is a Unix based system. Give me that option, out of the box.

- Without any customization, the program should be focused on less clutter, not more. The defaulting to opening new tiny windows that get left in a stack is bad. I sort of get the DMG open window install process when we were back in the CD days like 12 years ago. Now it's ugly, and shitty, and gives leeway to software providers to just do dumb illegible stuff. It seems that the rendering of the DMG install windows changes over time and that breaks the desired UI for older packages. This thing needs to die.

----

I want to be able to move down a tree looking at files like the cell does, with filtering, with a tree on the left, with easy file previews, to any place I can write on my system. Maybe that includes downloading a file from Chrome into /opt. File browsing is a noise heavy data intensive problem sometimes. If you are going to arbitrarily make the most basic tool on the system default to an oddly specific size, well then in use you should do some context detection and expand when there's a huge god damned list of files in the folder. I. Should. Always. Be. Able. To. Sort. And. See. My. Sorting. Options.

If any of this is available, please give me protips.

Re:We need to document macOS by pwinnski on Sunday August 13, 2017 @10:44AM (#15003078)
Unfortunately, your points aren't numbered, but I'm confused by a couple of them.

- Finder has had tabs for a few releases, and I can't recall the last time I had multiple Finder windows open at the same time. I use tabs for everything.

- By "sliding cell" do you mean the columns view? I use the list view roughly 100% of the time, so I'm no help there.

- On my system, quicklook opens a preview to the left of the finder window, so it doesn't cover the finder window. I think I must have moved it over there in the past, and it remembers.

- My system shows me every single dotfile, hidden file, and everything. I don't recall which setting I used for that, but zero things are hidden.

- Do you not have right-click, Services, New Terminal Tab at Folder? If not, then that must be something I installed in ages past.

Finder isn't perfect, by any means. It conflicts with how I like to do things semi-regularly. But I think a few of the issues you've raised might be solvable. At least that would lessen your pain a little.

Some of the differences between the defaults and what I see on my system might be down to this: https://github.com/mathiasbynens/dotfiles/blob/master/.macos

Re:We need to document macOS by sd8dgf8ds8g8dsg on Sunday August 13, 2017 @11:05AM (#15003179)
For showing "system hidden files", most popular is the ~/Library, run this command in terminal

    defaults write com.apple.Finder AppleShowAllFiles YES
For toggle display of hidden & dot files, type "Shift + Cmd + ."
Re:We need to document macOS by majewsky on Sunday August 13, 2017 @05:04PM (#15004930)
I can already see how n-gate is going to summarize this thread:

> An internet complains about how macOS documentation is only transmitted by tribal knowledge. Hackernews acknowledges the problem, and proceeds to trade said knowledge in exchange for internet points.

Re:We need to document macOS by sd8dgf8ds8g8dsg on Sunday August 13, 2017 @05:57PM (#15005174)
You are not wrong, but my account is throw-away just for this thread. Not hoarding HN points, that is a ridiculous behavior.
Re:We need to document macOS by majewsky on Monday August 14, 2017 @09:09AM (#15008312)
Don't worry; I didn't mean to bash on you. I just saw the irony of the thread.
Re:We need to document macOS by BakaRakuda on Sunday August 13, 2017 @11:27AM (#15003274)
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 window size you last set it as on a per folder basis when you open a new window from a location. Don't really have any troubles with how it works personally.

- Finder has tabs. Command+T

- Not 100% clear on the problem exactly. If you're going into the wrong folder you don't just have to select a folder by the first character, just keep typing and it will jump to the matching folder name in a list.

- File -> Make Alias

- This one is a bit unclear too. Use spring loaded folders, or a new tab in the location you want to drop to or add the folder to the sidebar that you want to drop files to. Cut and Paste with same named files is a lot better than it used to be and basically works fine now, IMO.

- View -> Show Preview

- Indeed it is designed to keep people away from the system files. 95% of people shouldn't be in there. And of the remaining 1% most of them shouldn't either even if they think otherwise. :P

If you actually need to muck in the system files you can toggle their display in the Finder via a terminal command.

- Command + Up Arrow to go up a directory

- You can open a directory in the terminal easily in a number of ways, including dragging and dropping the folder into the terminal window or icon, using the services menu, etc.

- I don't really find drag and drop copying to be slow in general, are you on a spinning HDD? Anyway with High Sierra the new APFS will make copying files instantaneous.

- There are various services you can use or you can create your own automator services, folder actions etc. to do a multitude of things.

- Finder is decently clutter free IMO, AND it can do a lot of sophisticated things as well.

Re:We need to document macOS by someone7x on Sunday August 13, 2017 @12:31PM (#15003542)
I'm not GP, but I recently sank time into trying to change Finder searches to default to the current directory instead of my entire machine. It mildly infuriates me that I can't change this; I gave up after I saw com.apple.finder.plist is not plaintext.
Re:We need to document macOS by comex on Sunday August 13, 2017 @01:15PM (#15003790)
Plist files have two standard encodings, an XML-based textual one and a binary one. You can use plutil to convert between the two, e.g.

    plutil -convert xml1 com.apple.Finder.plist
However, for preferences you probably want to use the `defaults` command instead, because IIRC they’re managed by a daemon (cfprefsd) that might not notice if you modify the backing files while it’s running.
Re:We need to document macOS by concede_pluto on Sunday August 13, 2017 @01:44PM (#15003944)
When someone decides a config file needs two different serializations and a daemon, I'm reminded of https://www.jwz.org/doc/mailsum.html.
Re:We need to document macOS by comex on Sunday August 13, 2017 @02:19PM (#15004131)
The two different encodings aren't just for config files; property lists are used throughout the OS for all sorts of things. They're a serialization of standard data structures such as arrays and dictionaries: same idea as JSON, decades before JSON. In retrospect, the XML-based text format is excessively verbose, but back then XML was all the hotness… As for the binary format, well, even given JSON's relative succinctness, there are many different formats that attempt to fill the role of 'binary JSON' (BSON, BJSON, JSON-B, MessagePack, CBOR, UBJSON, Fleece, PSON). It's just that none of them have become ubiquitous, probably because of some combination of fragmentation and the lack of built-in browser support.

As for the daemon, among other benefits, it allows preference changes to be immediately visible across all processes on the system, rather than requiring manual action to reload from disk. See:

https://developer.apple.com/library/content/releasenotes/Dat...

Re:We need to document macOS by kitsunesoba on Sunday August 13, 2017 @01:15PM (#15003793)
Default search scope is an option in the Finder's preferences window and has been ever since 10.7...
Re:We need to document macOS by stuntkite on Tuesday August 15, 2017 @11:10PM (#15024668)
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 by sd8dgf8ds8g8dsg on Sunday August 13, 2017 @11:01AM (#15003153)
> - 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, you will also need to nuke these from your system.

There is Path Finder, which is a good software (Shareware) that has a more traditional take on file explorer software, which might be good to check out if you are coming from Windows or Linux.

Myself, I'm just giving Finder a second chance, after having used Path Finder for a couple of years. It is well worth learning some of the key combos for better use.

Here is some more:

In finder, or in a "Open file" dialog, you can type "Shift + Cmd + G" to get a "Go to folder" dialog.

In finder, or in the "Open file" dialog, you can type "Shift + Cmd + ." to toggle "Show hidden files" (.dot files).

Re:We need to document macOS by stuntkite on Tuesday August 15, 2017 @11:12PM (#15024676)
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 by comex on Sunday August 13, 2017 @02:28PM (#15004182)
You may know this, but from column view you can use the toolbar or a keyboard shortcut to do 'Arrange By', which is not exactly a sort but similar. (It splits files into groups based on intervals of the specified property, and the groups are sorted, but the files aren't sorted within the groups.) Alternately, it's not exactly the most streamlined option, but you can change 'Sort By' from the window that pops up from Cmd-J.
Re:We need to document macOS by AsyncAwait on Sunday August 13, 2017 @10:52AM (#15003109)
I find Dolphin to have every possible feature I could ever want under Linux, I feel pretty confident in saying that it can be configured to work exactly how you want it to under Linux.
Re:We need to document macOS by Asooka on Sunday August 13, 2017 @08:10AM (#15002591)
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.

Re:We need to document macOS by kronos29296 on Sunday August 13, 2017 @10:18AM (#15003000)
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)
Re:We need to document macOS by Asooka on Monday August 14, 2017 @03:44PM (#15012113)
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 by fauigerzigerk on Sunday August 13, 2017 @02:30PM (#15004192)
Device drivers. That's what kills Linux for desktop/laptop use.
Re:We need to document macOS by blacksmith_tb on Sunday August 13, 2017 @05:07PM (#15004940)
I much prefer mdfind[1] to locate or find on macOS, it uses the same metadata Spotlight leverages.

1: https://ss64.com/osx/mdfind.html

[dead]
Re:We need to document macOS by stuntkite on Sunday August 13, 2017 @07:24AM (#15002473)
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 by jsz0 on Sunday August 13, 2017 @08:54AM (#15002709)
> What I'm bitching about here is what I consider to be a lack of innovation and a dereliction on obvious existing, key tools.

The confusing part is you mentioned PathFinder as being a great alternative yet it's very much a Norton Commander (1986) style file manager that hasn't changed all that much in the last decade. It's a great app but proves almost exactly the opposite point.

Re:We need to document macOS by stuntkite on Sunday August 13, 2017 @09:06AM (#15002748)
I don't think that my point is opposite. I find Finder to be so regressive that just more of the exact same would be a blessing. It's also entirely possible that hierarchical file system browsing is a solved problem and Norton Commander or even XP MS Explorer is as good as it needs to be. I don't entirely buy that it's the final form, but sure I'd be fine if it were true.

My suspicion with Finder is that it was deliberately made small and cumbersome to drive people to Spotlight. However at the time Spotlight was totally inadequate. The iOS platform started to take off and caring about that was shelved. To make up for that I used Alfred for years until Spotlight was updated. Alfred still has a leg up on Spotlight to some degree, like being able to run ssh commands. The Spotlight update came with what? Lion? To just make it pretty good?

How Spotlight works is absolutely indispensable, but that doesn't leave me in a place where my workspace is cleaner and easier to navigate than if they just gave me Norton Commander along with it.

Re:We need to document macOS by nebabyte on Sunday August 13, 2017 @08:05AM (#15002576)
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 by stuntkite on Sunday August 13, 2017 @08:27AM (#15002637)
Can you elaborate on what technology choices I'm missing? Lets just say specifically the Finder issue. Is the solution to use Linux as my desktop environment? I mean this honestly, I'm not trying to be flip.

Can you give me some examples of the solutions that other people have moved to years ago that you are referencing? I am very open to the fact that I could have just totally missed the train to a better creative tooling experience.

I don't accept the financially sensible part of your argument. I know how that what a company makes is money, and is beholden to investors over all. In my opinion, innovation really stopped around the time the iPhone3 took hold. I personally don't give a shit about their bottom line, it's doing fine and they can totally continue to funnel us in a direction of more of the same. However, I do think leaving the creators they once prized and facilitated behind for a more narrow experience catered to a consumer experience of walled gardens and media subscriptions has currently left the market wide open for a new home for people like me who are begging them to do better.

3 years and no reasonable update to the tool I use to produce my craft and it's still the best thing. That's really saying something for what the company has built as a legacy. The gap is so huge now, and they appear to just keep gutting focus on tools for their once beloved artists and creatives. A new iMac looks pretty good! But it doesn't live up to where I think their platform leadership should be.

In my opinion they have left a desperate, loyal, audience out in the cold so long that it's offensive and I'm looking forward to whoever can fill the role next.

Re:We need to document macOS by jcelerier on Sunday August 13, 2017 @10:03AM (#15002952)
> Lets just say specifically the Finder issue. Is the solution to use Linux as my desktop environment?

Yes, especially with KDE's Dolphin file manager which is more or less the pinnacle of GUI file browser.

See https://www.youtube.com/watch?v=jkWuVCKpiXs

it becomes especially good when you start taping in its scripting capabilities and the wealth of scripts available: https://store.kde.org/browse/cat/102/.

Re:We need to document macOS by sd8dgf8ds8g8dsg on Sunday August 13, 2017 @11:13AM (#15003214)
Please be cautious about recommending KDE's Dolphin. According to Hanno Böck in https://media.ccc.de/v/SHA2017-148-improving_security_with_f..., KDE are refusing to sandbox the thumbnail/preview code, which has proven to be riddled with easy-to-find bugs (using software fuzzing)
Re:We need to document macOS by jcelerier on Sunday August 13, 2017 @12:22PM (#15003491)
how do we know there aren't similar bugs with MS explorer / Finder ?
Re:We need to document macOS by spost on Sunday August 13, 2017 @02:05PM (#15004057)
Well, we don't, but would you rather use software known to have bugs or software not known to have bugs?
Re:We need to document macOS by jcelerier on Monday August 14, 2017 @06:02AM (#15007591)
uh... software whose bugs are known and whose source is accessible of course ? it's not like finder does not have CVEs: https://www.cvedetails.com/vulnerability-list/vendor_id-49/p....
Re:We need to document macOS by sillysaurus3 on Sunday August 13, 2017 @10:03AM (#15002950)
I use `find . | egrep -i foo` to find foo on OS X.

  ~/Downloads$ find . | egrep -i lisp
  ./ANSI_Common_Lisp_-_Paul_Graham.pdf
  ./lisp_in_small_pieces.pdf
  ./onlisp.pdf
It works well on an SSD. I also wrote a script called `narrow` which lets you pass in several terms to narrow the results by.

  ~/Downloads$ find . | narrow self pdf
  ./An Efficient Implementation of SELF, a Dynamically-Typed Object-Oriented Language Based on Prototypes.pdf
  ./Optimizing Compiler Technology for SELF, a Dynamically-Typed Object-Oriented Programming Language [10.1.1.87.4221].pdf

  ~/Downloads$ find . | narrow racket h$
  ./racket/collects/raco/main.lch
  ./racket/collects/setup/main.lch
  ./racket/include/escheme.h
  ./racket/include/mzconfig.h
  ./racket/include/scheme.h
  ...
I know this isn't too helpful of an answer. It isn't responsive to your argument that the GUIs have stagnated. But it's possibly a way to get what you want.
Re:We need to document macOS by ThrowawayR2 on Sunday August 13, 2017 @11:06AM (#15003181)
The original poster already said "I normally default to locate or find now...", so presumably he's well aware of find.
Re:We need to document macOS by nxtrafalgar on Sunday August 13, 2017 @08:28AM (#15002642)
So, what point are you trying to make here? That everybody should write their own tools?

That seems like a pretty inefficient use of everybody's time.

Re:We need to document macOS by dredmorbius on Sunday August 13, 2017 @09:01PM (#15006016)
Starting a comment with a personal attack isn't well-advised here.

Doing it twice in a row, far less so.

Re:We need to document macOS by AsyncAwait on Sunday August 13, 2017 @08:14AM (#15002603)
I don't see how wanting a competent file manager or at least have the ability to completely switch to a different one has anything to do with "hilarious entitlement", it seems like a pretty reasonable expectation.

> you can't simultaneously hope for a consumer product that "Just Works^TM" and demand your customization needs

The problem is Finder "doesn't just work" for many people, so yeah, they should be allowed to swap it, that has nothing to do with it "just working' in other parts of the system.