News for hackers. Stuff that matters.
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.