Live data from Hacker News

Mysterious Avid Issue Knocks Out Mac Pro Workstations Across Hollywood

variety.com

131–140 of 213 posts

Re: Mysterious Avid Issue Knocks Out Mac Pro Workstations Across Hollywood

#131
post #51

Earlier quoted context omitted.

What you're describing sounds like industry-specific anecdotes from a very common, cross-industry reality about non technical users.

On two occasions I have been asked, — "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" In one case a member of the Upper, and in the other a member of the Lower, House put this question. I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question. - Charles Babbage - Passages from the Life of a Philosopher (1864), ch. 5 "Differen…

The question makes sense rhetorically, to establish that the machine is still only as good as its operator, just faster.

Re: Mysterious Avid Issue Knocks Out Mac Pro Workstations Across Hollywood

#133
post #21

Sound like someone messed up a removal routine, equivalent to "rm $base_dir/$temp_dir -rf".

Yeah, that’s exactly what the behaviour sounded like to me too, having inadvertently done this to myself a few times over the years, and given that many autoupdaters run with root permission, it’s perfectly plausible.

Yeah, I think we had that twice: 1. "I can't work if all the NFS mounts empty" 2. "You're aware that closing the GUI empties /home/$(whoami)? Related: Did you see our sysadmin?". Backups are awesome.

Re: Mysterious Avid Issue Knocks Out Mac Pro Workstations Across Hollywood

#134
post #128

Earlier quoted context omitted.

On two occasions I have been asked, — "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?" In one case a member of the Upper, and in the other a member of the Lower, House put this question. I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question. - Charles Babbage - Passages from the Life of a Philosopher (1864), ch. 5 "Differen…

If you want to use incorrect data to get correct answers, you need a human. That's one of the fundamental differences between humans and computers.

Floating point numbers are trying hard to rectify this ;-)

Re: Mysterious Avid Issue Knocks Out Mac Pro Workstations Across Hollywood

#135

Earlier quoted context omitted.

I don't understand this. > The thinks-their-technical users English was not my first language and sometimes I get tripped up. What does this mean?

They meant "thinks-they're-technical", which might clear things up. Putting dashes between a bunch of words isn't really a correct way to do this, but it's a way to smash a bunch of words together and pretend it's one word. In this case an adjective describing the users.

It's perfectly cromulent to hyphenate words this way. Doing so causes them to become adjectives. For instance, you would say "fast-paced agenda," not "fast paced agenda," or "fast, paced agenda." The latter two have a different—and in this example, weird—meaning.

In this case, I think it's a poor style choice, because there are two verbs and an adjective being combined, but there's nothing 'incorrect' about doing so. It might be clearer to say "users who think they are technical," but fixing the mixed pluralization and incorrect use of "their" would go a long way on their own.

Re: Mysterious Avid Issue Knocks Out Mac Pro Workstations Across Hollywood

#136
post #107

Earlier quoted context omitted.

I'd revise that to the far more irritating segment of users who think they're more technical than they really are. Actual non technical users are fine, because they generally know when they don't understand a thing. The thinks-their-technical users will bravely throw in whatever phrases they've heard mentioned in relation to a completely unrelated problem.

That's the super-user syndrome. They know enough to get themselves into a bind but not enough to get themselves out. It's difficult just trying to get an accurate description of the problem because they lace the description with theories about what the cause is. "Please just describe the problem and, if possible, how you reproduce it. No, just describe the problem. What's happening when you press the button? No, just…

I imagine this is especially prevalent for editors because they are expected to be the technical ones in a room of high-ego professionals. Every second of their day is them being judged on how super-user they are.

Re: Mysterious Avid Issue Knocks Out Mac Pro Workstations Across Hollywood

#137

Earlier quoted context omitted.

I don't understand this. > The thinks-their-technical users English was not my first language and sometimes I get tripped up. What does this mean?

They meant "thinks-they're-technical", which might clear things up. Putting dashes between a bunch of words isn't really a correct way to do this, but it's a way to smash a bunch of words together and pretend it's one word. In this case an adjective describing the users.

What? Hyphenated compound adjectives have been a standard feature of English for centuries:

https://www.grammarbook.com/punctuation/hyphens.asp

Re: Mysterious Avid Issue Knocks Out Mac Pro Workstations Across Hollywood

#139
post #37
post #30

The use of 'trashcan' to refer to the MacPro by multiple users in the link is pretty amusing. > Has anyone had their trashcans go down today out of nowhere?

That must really be annoying someone over at apple. Spend all that time design something beautiful. And... Everyone calls it garbage

As far as I can tell, everyone calls it the trashcan, even inside the company.

Re: Mysterious Avid Issue Knocks Out Mac Pro Workstations Across Hollywood

#140

Earlier quoted context omitted.

> their copy protection management tool/device driver - iLok MacOS Catalina makes running kernel extensions hard, they probably were testing new iLok version for Catalina.

Catalina major change is ANY dll should know pass through security. That's why notirisation also for software plug-ins is needed meaning also runtime hardening in future and proper entitlements by host and plug in

Your comment is a bit hard to parse. Would you mind clarifying it a bit?
Post reply on HN