@morbiuswilters said:
Filed under: Toy language.
You know what? You're right. It *is* a fucking toy. The type you smash to pieces and have fun with the remains while your older brother watches you pitifully.
Though I hate to blame the language when the fault is in the libraries, I feel that a high level language is mostly distinguished for its libraries. Especially if it is so widely spread on the Linux desktop (thanks, Red Hat, you really didn't have to). On the other hand, I think the fault is partly in Python's lack of native threads, so screw apologies. Threads or no threads, though, the libraries still sucked the perfomance out of my application.
alsaaudio, I condemn thee!
I've spent around 30 man hours trying to figure out what the fuck's wrong with this thing. I went nuts in the meantime. Ultimately, I said hell to it all and dug into C++.
Guess what. It worked the first fucking time. Took me less than 3 hours to get a fully working playback-and-capturing app. No multi-threading whatsoever. Screw you, Python!
Also, I noticed something peculiar in the process of rewriting.
You know Linux, right? That thing that's the hype on mobile devices and everyone's so happy about? You also know that most mobile devices nowadays have Bluetooth, right? And Linux's running on those devices, right? And Linux has support for Bluetooth, right?
Well, guess what, [b]no one wrote a single line of documentation for the Bluetooth stack[/b]. It's all in the source code.
I mean, sure, it's a pretty obvious and convenient implementation - just adds an additional type of socket and everything should be clear to someone with experience in networking. But a line or two of official docs wouldn't have hurt. Or at least a document with the common pitfalls. Like a FAQ. Is that too much to ask? I spent 50 minutes trying to figure out a cryptic voice setting. Thanks, Linux, that was really helpful.
So, yeah, this project was a big disappointment. Nevertheless, I have one hell of a useful application ready to go. That counts for something.