Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CUDA Toolkit Release Notes

docs.nvidia.com

Post reply on HN
Print view View original

91–100 of 126 posts

Re: CUDA Toolkit Release Notes

#91

Post by sergiomattei »

andybak wrote: post #43
dang wrote: post #19

Submitted title was "Nvidia drops support for CUDA on macOS". We changed that for a while to "CUDA 10.2 is the last release to support macOS", which is language from the article itself. Since then someone emailed and asked why the title was like that in light of the discussion at https://news.ycombinator.com/item?id=21617016 , so I've reverted to the article's title. Edit: If the article were more a burying the lede…

Any title that gives us a clue why the story is worthy of note. At the moment it's frustrating as you have to click through to find out if you want to click through. (title at the time of my comment was "CUDA Toolkit Release Notes")

Agreed. Quite frankly the new title doesn't help people understand why it's newsworthy.

Re: CUDA Toolkit Release Notes

#92

Post by vkaku »

snuxoll wrote: post #10
wlesieutre wrote: post #4

Not surprising given Apple’s apparent vendetta against Nvidia hardware

A well deserved vendetta, Nvidia has screwed Apple over multiple times going back to the PowerPC days. After the defective chipset fiasco one can’t blame them for cutting ties.

Sounds like AMD and Intel should sever their ties too.

Re: CUDA Toolkit Release Notes

#93

Post by pvg »

jsgo wrote: post #73
pvg wrote: post #53

Earlier quoted context omitted.

As the whiner who whined about this title - the story isn't worthy of note at all, other than someone fishing a supposedly-important detail out of it and putting it in the title. Apple hasn't as much as sold a machine with an Nvidia GPU for many years. This non-editorializing thing is explained in great illustrative detail here: https://news.ycombinator.com/item?id=21617907

Perhaps they haven’t sold Nvidia hardware, but the allowance of Nvidia’s web drivers so that I could connect my eGPU w/ GTX 1080 to the 13in Macbook Pro was one of the primary reasons I bought the MBP. It is fine if they want to kill off features off upcoming hardware, but killing off the capacity to use something that was used for months is not the best look. If Metal Only was the goal, add a prompt when someone ena…

The configuration you're describing was never officially supported - I'm not arguing the changes in this support is a good or bad thing just addressing the concern Nvidia might be trying to sneak something super-important past people in release notes and thus the editorializing should perhaps get a pass.

Re: CUDA Toolkit Release Notes

#94

Post by vkaku »

iguy wrote: post #70
navaati wrote: post #64

Earlier quoted context omitted.

> if usable outside MacOS software stack Except, of course, according to Apple’s history regarding the matter, it won’t.

Unless the swift-for-tensorflow effort cross-fertilises something interesting, I suppose? If you were asked to guess the most likely path by which AMD cards become widely useful, perhaps this would be as good a bet as any.

Someone will need to get ROCm on MacOS, or something like that.

God, I really hope AMD goes out of the deal with Apple as well. I'd rather people abandon macOS early than have to put up with Apple imposed implementations like Metal, HLS and Webkit.

At the end of the day, Apple should realize that having money alone does not make you , by any means, a popular company. It's the little things that make people sign up for Apple.

Re: CUDA Toolkit Release Notes

#95

Post by sbuk »

QuixoticQuibit wrote: post #40
snuxoll wrote: post #10

Earlier quoted context omitted.

A well deserved vendetta, Nvidia has screwed Apple over multiple times going back to the PowerPC days. After the defective chipset fiasco one can’t blame them for cutting ties.

That seems like a very one-sided take considering Apple’s history. Moreover, the reason is almost certainly related to Apple not wanting to proliferate Nvidia’s tools and instead force developers to use their Metal API. AFAIK Apple’s even abandoned OpenCL on macOS.

So, you are aguing that NVidia constantly messing up when Apple have used them in good faith as a supplier, followed by the subsequent denial of problems even existing by NVIdia and their refusal to accept any culpability (see Bumpgate), is "a very one-sided take" and eschew it in the belief that this is all about pushing Metal? That seems like the very narrowly held view to me. Perhaps they are thinking the way you propose, but since NVidia hasn't figured anywhere in any of Apple's hardware since Bumpgate, I'd suggest that NVidia being a bad partner has considerably more to do with it.

Re: CUDA Toolkit Release Notes

#96

Post by mikhailt »

amelius wrote: post #52
bitL wrote: post #15

Earlier quoted context omitted.

NVidia didn't want to pay for failing NVidia chips in MacBooks when they had problems with their manufacturing over half a decade ago and since then Apple tries everything to make NVidia's and its customers' life difficult.

Weren't these chips failing because of bad thermal design of the enclosure?

Nope. This was a confirmed defective GPUs by Nvidia themselves.

All companies that used these GPUs were affected. They even sued Nvidia.

Here is example: https://blog.dell.com/en-us/nvidia-gpu-update-nvidia-class-a...

Re: CUDA Toolkit Release Notes

#97

Post by andybak »

pvg wrote: post #56
andybak wrote: post #54

Earlier quoted context omitted.

1. I didn't know the fact highlighted in the original title 2. Doesn't this have an impact on eGPUs, Hackintoshes and other customizations? It basically means heavy GPU-based work is pretty much a Linux/Windows only thing now. Huge problem as machine learning starts to become an interest topic for people in the art and design community.

For 1., again, the standard isn't 'someone might not have known a detail in the story', it's 'does the title represent the story'. If that particular detail is worthy of highlighting, it's easy to find (or even write!) a story about that or point it out in a comment. For 2., that's been the unfortunate case for ages but more importantly, see 1.

It's not a "detail" if it's pretty much the only reason to post or read the story in the first place.

Re: CUDA Toolkit Release Notes

#98

Post by benologist »

sbuk wrote: post #95
QuixoticQuibit wrote: post #40

Earlier quoted context omitted.

That seems like a very one-sided take considering Apple’s history. Moreover, the reason is almost certainly related to Apple not wanting to proliferate Nvidia’s tools and instead force developers to use their Metal API. AFAIK Apple’s even abandoned OpenCL on macOS.

So, you are aguing that NVidia constantly messing up when Apple have used them in good faith as a supplier, followed by the subsequent denial of problems even existing by NVIdia and their refusal to accept any culpability (see Bumpgate), is "a very one-sided take" and eschew it in the belief that this is all about pushing Metal? That seems like the very narrowly held view to me. Perhaps they are thinking the way you…

Nearly a decade has passed since nVidia messed up one generation of laptops so probably it's time to let it go. Grudges don't really help anyone, and Apple's so far from innocent they shouldn't promote grudges as solutions to problems, especially as alternatives to consumer-friendly hardware support.

In much more recent times Apple themselves ruined four generations of laptops and were deceptive and dishonest about it, until they grudgingly rolled out their free keyboard replacement program which starts expiring for their earliest victims at the end of next year. Apple chose to experiment for 3 additional years at, in aggregate, major expense and inconvenience to their customers.

nVidia was never as bad as Apple and it's hypocritical too. How many Foxconn employees killed themselves without Apple permanently prohibiting working with Foxconn? How many child workers have they found in their supply chain without terminating their relationship with suppliers? nVidia obviously solved their one issue, and went on to ship millions of chips in laptops since then without problem.

Re: CUDA Toolkit Release Notes

#99

Post by throwawaysea »

So what do people here use to learn/fool around with GPU-dependent ML stuff (non production use cases)? A non Mac laptop? Or do you do it all in the cloud? Using the cloud presumably gets expensive over time and I also would think that the overhead of dealing with a cloud setup and all the associated legwork to get started can be frustrating compared to working locally.

Re: CUDA Toolkit Release Notes

#100

Post by mirekrusin »

mirekrusin wrote: post #38
pvg wrote: post #24

Earlier quoted context omitted.

That only flies if Ctrl-[ also enables Nvidia support.

MacBooks with iPhone stripe don’t have Nvidia hardware.

Being downvoted I'm genuinely interested - are there new MacBooks with Nvidia cards? I'd like to get one if it exists. Am I missing something? All have AMD/Intel graphics cards, right?
Post reply on HN