We are DOOMed !
We are DOOMed !
"socialist shithole" ? Seriously ?
Did you had a look at what happened the last 5 years ?
The socialist president and governments have done more for companies, and less for people than the previous, right wing one. Socialist does not mean anything anymore. It's just a label politics chose when they get out of the ENA (National School for Administration : it's where most politics come from, they never had a real job).
Once in charge, they only do things to please their friends and sponsors
please note that :
- the law says 35h/week, but it is not enforced everywhere, far from that. Almost all companies have a negotiated agreement. The law say that if you work 35h/w, you get nothing, and if you work 39h/w, you get about 22 days of additional free time. The agreement usually says you get 10 to 15 days, period.
So I can work 35h/w and get 15 days ? Yes, may be. But most people work 39h/w, and often more.
So, who is the winner ? The company of course. The law and its application are different.
- there are many countries which have work hours less than the French 35h/week. what not talking about these ones ?
- what about productivity ? Many studies show that French are much more productive than many other countries.
Alright, my turn : stop bashing France, you Americans who will kill themselves working like crazy 50, 60, 70h/w or more. Your productivity is less than French.
Can't wait to see the new episode !
You're right, it's part of the process and I shouldn't have neglected it. But I think it's not the main reason for the delay.
Just keep in mind that there is more than that, especially in the case of a car (that I don't know everything about), but also in a BT speaker (which I know much more because it's part of my job).
There are many potential causes for the delay. And they can add a second here, few ms there. I guess that :
- there is the button on your wheel that goes through the car wiring and base embedded system : can (and CAN !) take time.
- the button event is communicated to the infotainment system : should be fast, but who knows ?
- the infotainment system sends an AVRCP (play, stop, pause, next/previous track) command through its Bluetooth module : some of these can also take time. I had the case where play was immediate, but pause (same play/pause command in fact) took 3 seconds. By the way, next/previous may be used in two way : short press (for track change) or long press (for fast forward/backward). May be your car system waits a bit to know of its a short or a long press.
- your phone receives the command and propagates it to the music player : depending on the music player, there may be some fading delay. Check your player settings !
By the way, may I ask how this topic is related to the initial post (cURL) ? Oh, yes, the mail example
I'm already using Qt and am happy to stay away from the painful VS.
- under Windows, Qt uses gcc/MinGW (or VS compiler if you wish)
- under Mac OS X, Qt uses XCode compiler
- under Linux, Qt uses native and easily installed gcc
At the time of the version 3, I also had the opportunity to work with the embedded version (user interface in trains, running on PPC computers).
So there is Qt, and there are many other solutions described in the other comments. M$, what are you doing here, then ?
By the way, since Skype is made using Qt : M$, please, explain why there are so many differences between versions, especially with the Linux one ? Need some lessons in portability ?
I was hoping it could read text messages. It may, but
There are a lot of disappointed users on the play store :
It's rated 3.3 at the time of writing. I will wait a bit before trying myself !
... the Space Bubble !
Sorry, it's Friday, I'm tired
And probably most of "advanced" countries.
Accountability ? Close to zero.
Look for Amesys and Qosmos here : https://reflets.info/ (French)
Could you point what's inaccurate please ? I'd like to improve my knowledge.
Or go away yourself ?
To add details to your answer : first point, look at your source : is it FLAC or MP3 (or any equivalent). If the source is bad, it cannot be better at the other end.
AFAIK, Bluetooth uses an A2DP pipe and this pipe allows the transmission of data using 4 codecs :
- SBC : the first historically, the worst in quality
SBC, AAC and MP3 are lossy codecs. I never saw a product that accept AAC or MP3. There must be a license to pay to use MP3; may be also for AAC.
aptX is both lossy and lossless. And most source devices (smartphones, computers
So, the technology already here to allow a much better quality than what we know (as long as one can force the use of the lossless variant of aptX, which is
Then what ?
Then CSR : the dominating Bluetooth chips manufacturer. More than 70% of the chips last time I heard.
CSR has patents on aptX.
And patents are meant to make money (yes; were you told otherwise ?).
So, the sink devices (BT speakers, car audio systems,
And guess what : manufacturers like profit, so they don't pay CSR for aptX and stick to SBC.
The hardware is always ready, the firmware may contain the aptX codec, but if the license key, linked to the BT MAC address of the chip, is not present in the firmware, aptX won't be negotiated as an available codec with the source device. Only SBC will be used, even if your source device can do aptX.
By the way, if you like your music, listen to it on real speakers in your living room !
Not at all.
Let's them play their money games in private.
I know, it will be hard.
Adding features does not necessarily increase functionality -- it just makes the manuals thicker.