News for hackers. Stuff that matters.
Re:AMD releases FireRays 2.0 ray-tracing library as open source by tiplus on Tuesday May 17, 2016 @12:17AM (#11711318)
Why not contribute to Blender cycles instead?
Re:AMD releases FireRays 2.0 ray-tracing library as open source by taneq on Tuesday May 17, 2016 @01:36AM (#11711531)
Because they're open-sourcing an existing library?

To answer the larger question of "why create a new library instead of contributing to open-source project X instead", the answer is that working on other peoples' open-source projects (if you're actually going to improve them rather than just throw more me-too mud at the wall) usually consists of cleaning up other peoples' messes. You're at the mercy of a third party maintainer, you're stuck with someone else's (probably terrible) design decisions, and you're dealing with a list of existing bugs and defects.

I can't speak for everyone but just personally, if I'm doing a job like that, it's because I'm being paid for it.

Re:AMD releases FireRays 2.0 ray-tracing library as open source by optimiz3 on Tuesday May 17, 2016 @01:50AM (#11711566)
You're also at the mercy of their often unreasonable demands (testing bars and sign-offs that they themselves never would pass).
Re:AMD releases FireRays 2.0 ray-tracing library as open source by dagw on Tuesday May 17, 2016 @05:29AM (#11712242)
Re:AMD releases FireRays 2.0 ray-tracing library as open source by jensnockert on Tuesday May 17, 2016 @05:55AM (#11712337)
Because Cycles is a rendering engine, while FireRays is a ray intersection acceleration library. Cycles could opt to use FireRays for ray intersection if they wanted to, but most uses of FireRays probably could never use Cycles since need a rendering engine with entirely different capabilities (real-time &c.)
Re:AMD releases FireRays 2.0 ray-tracing library as open source by Const-me on Tuesday May 17, 2016 @01:28AM (#11711507)
I mostly work on closed-source software. If they contributed to Blender, I would never be able to use that FireRays because GPL.

Instead, AMD released FireRays under permissive license, so I can pick the technology for a next project if I see fit. BTW I have good experience using libraries by AMD, such as SSEPlus (Apache license).

Re:AMD releases FireRays 2.0 ray-tracing library as open source by greenknight on Tuesday May 17, 2016 @02:37AM (#11711716)
Cycles (the blender raytracer) is actually licensed under the Apache License v2.0 -- https://code.blender.org/2013/08/cycles-render-engine-releas...

It is being implemented into Rhino at the moment and already has had a release into Poser

Re:AMD releases FireRays 2.0 ray-tracing library as open source by Qantourisc on Tuesday May 17, 2016 @02:57AM (#11711784)
Depending on what you want to render, and what kind of look you are after. Blender cylces can be the worst of raytracers. I'd be more interested in a general ray-hitting lib, less then a raytracer.