mrhill
Our team is working on GPU cloud and virtualization, we are looking for C/C++ developers to work on Android, Windows, and MacOS. We are still a small team on a new product with lots of room to grow.
We use a good mix of low-level OS engineering, graphics, cross platform, and web technologies: C/C++, Python, Docker, Xen, AWS, Qt, Flask, SDL, OpenGL, DX, audio/video codecs, x86/ARM, Linux, Windows, MacOS, Android.
Contact: dschalig at nvidia.com
Not only made it the data really small (we could fit all the roads of a country like Germany in 5 MB), it was also blazing fast to decode. Our vector map renderer used to do the vector map decompression on the fly, while doing coordinate transformation, and rendering to the screen. That was really the trick to get realtime zooming and panning vector maps on ~100 MHz ARM CPUs with tiny data caches of the time.
We even took that compression scheme a step further from byte-bound to bit-granularity. Above article made me wonder, how our old scheme performs on today's CPU...
My team is working on GPU cloud and virtualization, we are looking for C/C++ developers to work on Android/Mac/Windows clients.
We are still a small team on a new product and look to grow. We use a good mix of low-level OS engineering, cross platform, and web technologies: C/C++, Python, Docker, Xen, AWS, Qt, Flask, SDL, OpenGL, DX, audio/video codecs, x86/ARM, Linux, Windows, MacOS, Android.