Hybridizer: High-Performance C# on GPUs

Re:Hybridizer: High-Performance C# on GPUs by pjmlp on Monday December 18, 2017 @11:56AM (#15953040)

I disagree, if people have given up trying to fly on the years of continous crashes, we would never haven gotten mainstream comercial flights.

Many times there is a need of ongoing investment, where things are failing pretty bad, until they actually take off.

[ Parent | on HN ]

Re:Hybridizer: High-Performance C# on GPUs by kornish on Monday December 18, 2017 @01:05PM (#15953698)

Your example doesn’t account for substitutes, though. Before commercial flights, civilians couldn’t fly. Before Hybridizer, programmers could still use CUDA.

[ Parent | on HN ]

Re:Hybridizer: High-Performance C# on GPUs by pjmlp on Monday December 18, 2017 @01:48PM (#15954156)

The point being that it takes time to get the right solution for a problem, and we shouldn't be stuck with C and C++ for GPGPU forever, just because no one has found out the ideal solution for multi-language GPGPU programming.

Just yesterday I saw a documentary about Gotthard Tunnel, also considered impossible to achieve, with high human costs and risk of insolvency until they finally managed it.

John Harrison took almost his entire life to create the first usefull marine chronometer, amid disbelief and issues to get proper funding.

Or if you want to bring it closer to home, very few people believed JavaScript would ever become fast or even leave the browser.

[ Parent | on HN ]

Re:Hybridizer: High-Performance C# on GPUs by EpicEng on Monday December 18, 2017 @02:27PM (#15954584)

Sure, and on the road to flight many bad/impractical ideas were thrown out.

[ Parent | on HN ]