kango_v

But, the point is that the RTX cards are a fudge. You still have to do all the tricks that the game designers do for the rasterisation step. Using Path Tracing you get rid of all of those "tricks" so that the designer can concentrate on the scene instead of telling the GPU to work around rasterisation's shortcomings. Ray tracing traces a single ray until it hits an object. Path tracing, on the other hand, bounces a ray around until it cannot be seen. To get better quality, you just up the samples per pixel. 
 
This is why I'd like others to see what they get on their GPUs using path tracing. We would then get an idea of how far the current cards are away from using this in games. Path tracing is not perfect, but it's the best way to get to near photo realism.

Bloody hell, i feel like an old man on this forum. Anyway,
I've been coding since the age of 7 on a Sinclair ZX81 (assembler), then on to a BBC Micro (6502) assembler. Once I got my first PC it was into C, C++, DBase III+, FoxPro, Turbo Pascal, COBOL, Basic etc. 
My first job with using RPGIII/CLP on an IBM System 38 (what a beast), then onto an AS/400 (System i now). From there I've used VB, ASP, C#, SQL, Bash etc. Now do Java full time.
I now design large distributed systems to handle on-line betting using highly async/concurrent servers using Ratpack (way faster than NodeJS). We use the same Disributed NoSQL db that Netflix uses (Cassandra) which is the dogs nuts.
Oh as for IDE, we use Eclipse and IDEA with a sprinkling of VIM and Emacs for good measure.
Not a Windows machine in site! LOL

I've now been using Ubuntu Linux since version 5.10 (nearly 12 years!) at home and at work. I last used Windows when XP had only been out around a year (ish). When I now go back to Windows I'm lost :).
 
So to install the Gimp:
1. Click "Software" icon
2. Click Gimp
3. Click "Install"
4. Run
 
or from the command line:
 
$ sudo apt install gimp
$ gimp
 
Now, that is NOT difficult. My machine at home gets used for games, software developing, video editing, kids homework.
 
I do lots of work stuff like testing clusters of Cassandra nodes (Netflix use this), PostgreSQL, Jboss, Ratpack, various data grids etc. I've never run anti-virus and never had any malware or viruses. I've always built my own PC's so that Linux friendly hardware can be selected.
 
Dive in! Linux today is a doddle to use. If my mother-in-law can use it, I'm pretty sure any one on this forum can
 

We started out with C/C++ for quite large project, but due to many hassles we ended up using Java and the SWT libraries (from Eclipse). It looked and acted like a native app on Windows, Linux and Mac OS, loading fast and proved to be very usable and stable. The users could not notice a difference between a truly native app whatever the platform. This was a massive win for us as it was truly multi platform. Oh and a new user could install it and the JVM via a HTTP URL. Such is the power of JNLP.
 
Something I've learned over the years is to split your app (small or large) into service and client pieces. Think about the service API and test it before even writing a gui. This will enable you to expose it via a remote (e.g. REST, ProtoBuf, Netty etc) interface later if needed with hardly any client changes. 
 
This is the same way Linux tools/apps are written. You will always have a libXXXX portion and then the Python/Ruby/C++/Bash front end using the library.  Makes sense.