News for hackers. Stuff that matters.
Re:GPU glitches in 2016 MacBook Pro models by gcp on Friday November 25, 2016 @02:06PM (#13039075)
Try running a VM and compiling inside that...
Re:GPU glitches in 2016 MacBook Pro models by bdcravens on Friday November 25, 2016 @02:56PM (#13039400)
The nature of VMs is that you can assign memory to it. So if your machine is already light, you wouldn't give it much memory to start with, and it'd run (just slower)
Re:GPU glitches in 2016 MacBook Pro models by rockdoe on Saturday November 26, 2016 @03:07AM (#13042451)
So you're saying the Mac "Pro" is OK for running things slowly.
Re:GPU glitches in 2016 MacBook Pro models by bdcravens on Saturday November 26, 2016 @05:10PM (#13046187)
Not saying that at all. Saying that if someone says it'll run in 8GB instead of 16GB, or 16 instead of 32, it's possible, but those claims ignore performance. The presence of those statements means absolutely nothing absent of context (for instance, the required performance of a Windows 10 VM isn't the same for someone just testing a site on IE versus a developer running a 300GB SQL Server database)
Re:GPU glitches in 2016 MacBook Pro models by pjmlp on Friday November 25, 2016 @02:12PM (#13039104)
You mean like using Swift, D and Rust on a VMWare instance running Ubuntu Linux 16.04 LTS?
Re:GPU glitches in 2016 MacBook Pro models by rockdoe on Saturday November 26, 2016 @03:04AM (#13042435)
Linking some amount of C++ code can get very painful very quickly on a constrained VM.
Re:GPU glitches in 2016 MacBook Pro models by pjmlp on Saturday November 26, 2016 @06:34AM (#13043012)
Linking C++ is painful anywhere, this from the point of view of someone that likes the language since 1993.

Modules might finally solve it, but it will a Python3 like story until they get integrated across major compilers, libraries and frameworks.