3 ms·
> the published solution is to build from source I tried that, it didn't work, and they keep closing issues about it instead of addressing it. They are a compa
by dheera 6y ago
> the published solution is to build from source
I tried that, it didn't work, and they keep closing issues about it instead of addressing it. They are a company with a 200B market cap, and it's already 5 months since the release of 20.04 and they still can't get their drivers straight.
People like me want to use their hardware. I don't have time to be debugging their drivers -- I have other work to do. I don't think it's unreasonable ask for them to support the latest LTS release of the most common Linux distribution in a timely manner with pre-compiled binaries that just work, in return for the $179 that I and tens of thousands of others paid for the device.
This isn't some open source community software that I'd be glad to pitch in some time and help debug. This is a driver for a device that I paid a for-profit company for and I expect timely support especially for an exceedingly common OS that I use.
- eesmith 6y agoYou wrote "Python 3.8 has broken a LOT of stuff", as if it were only Python's problem. Clearly other things are broken too.
- dheera 6y agoIf they maintained semantics of versioning, any 3.x code should always run on 3.(x+1)
- eesmith 6y agoSure. But they don't. So is the error in them, for not following semantic versioning, or is the error in you for incorrectly assuming they follow semantic versioning? Are you really just complaining about the version numbering? Ok, let's say they follow semantic versioning, and instead of calling it 3.8 they called it 4.0. The package you use would still be broken. Now what do you do? Why don't you install Python 3.7 yourself and pip install the pre-built binary?