The only real problem is that I have no clue why Intel is in this business, and I suspect they won't be for much longer.
* DKMS kernel module for what should be a plain vanilla USB 3.0 device
* firmware updates require closed-source libraries
* breaking API and ABI changes that do not respect semver or SOVERSION
The worst part of my dayjob is wrangling the Realsense software suite.
This little lidar looks nice but the last thing I need is another weird kernel module and some closed source library to support my hardware. No thanks.
* disable Secure Boot xor create your own efi signing key pair, get friendly with `mokutil`, and pray your firmware's UEFI implementation supports that complicated custom KEK
* Ubuntu 18.04 support, but forcibly install at least one 16.04 package they couldn't be bothered to build for the latest stable release of their chosen distro --- or `patchelf` the shared object and, again, pray.
* accept that the debugging symbols they provide still bear the source paths from the Jenkins instance that packaged them
* Oh, yeah; sometimes the device is detected as USB 2.1. That's fun when it happens 2 hours into a calibration run
They're good if all you need is a flakey proof of concept. It sounds to me like you require something better.
I bought one. Bad thermals and weirdly flaky wifi, thanks to the overheating. To get it to run the fan fast enough you had to manually edit the startup scripts. Intel quietly killed it a year later, and it appears to be totally unsupported.