gfxgirl

> This might be excluding anybody that cannot work after hours, for a reason or another.

Maybe I'm reading into this but I see this type of response a lot on HN.

> A: You need experience. Get some after hours

> B: I don't have any time after hours. It's not fair

Like gees! What do you expect?

B: I wanna be guitar player in a rock band

A: Well, if you don't play guitar, take lessons after hours

B: I don't have any time after hours

A: So what do you expect me to do about it? I'm not about to add someone who's never played guitar and can't demonstrate the skills as a guitarist in my band. It's not my problem that you can't play, don't have the time to learn, and yet want to be in my band.

---

Same for any company: So what do you expect me to do about it? I'm not about to add someone who's never programmed games and can't demonstrate the skills as a game programmer in my team. It's not my problem that you can't code games, don't have the time to learn, and yet want to be in my gamedev company.

It is close to deprecation. In fact it's already deprecated on a device ~50% of American's use (an iPhone). It's also deprecated on MacOS.

Many hardware manufactures are getting rid of it from their drivers and just using 3rd party libraries that emulated it on newer APIs.

was there ever a setting for this? I always used gSwitch or gfxCardStatus to varying degrees of success

No, the problem is bad developers pulling in dependencies for trivial functionally. If there was a `for-loop` npm package bad devs would be pulling it in instead of writing their own for loops. Padding on the left is something if it doesn't exist you write it in a few lines of code yourself. You don't add a package for such trivial functionality.

curl | bash doesn't bother me because I do it like twice a year from sites I trust. On the otherhand, the node crowd uses "npx command" all the time where npx will download and execute code from the net. Unlike "curl | bash", "npx command" is something you're expected to do 10s or 100s of times a day. Each one of those times is a chance for you to have a typo and execute code from some randon source like if you type "npm commmand" or "npx comman" or "npx coomand" or "npx comman dargument", etc...

As is often commen, wikipedia is plain wrong. I've never heard this opening narration and I saw it on opening day

?? I saw it in the theater when it opened. nothing was ruined. maybe there is a second cut I'm unaware of. Certainly the cut Roger Ebert gave 4/4 stars, which is the original theatrical cut, isn't the one with spoilers

I skipped that by choosing lisp as my scripting language. took a day to implement. no complex parser required

for config I used ini files, super simple to parser (and now json so always can use an existing solution)

At the time a single seat of PowerAnimator, the predecessor to Maya, cost $50k-$60k. $30k was for the SGI machine to run it and the other half was the software license.

Microsoft bought Softimage, one of the top competitors to Maya at the time. They charged iirc $4k or $8k and a PC to run it would run $4k-$5k

Softimage is long gone but it's what Valve used for the Source Engine and Half Life 2

It's not doing what I expect. Oh? Change the spec

It's not doing what I expect. Oh? Change the code

How is that different from now?

Not to defend the OP because I agree that null is bad. But, in my limited experiecne with Swift I just add a few characters at the right place and the null's are now incorrectly ignored and the warnings go away. So, the language gave me warning, but it didn't really force me to deal with it correctly. Is Swift a bad example of a null-safe language?