jansc

I bought an ID.4 Pro Performance just before the summer and after about 15.000km I can say that the software is not great at all. I could perfectly live with the delays, sometimes it takes many seconds for something to happen after pressing on an item on the screen, but there are many other problems.

I am no longer able to log into the car with my We Connect account. No error message after login, but the car keeps on telling me that I have to log in. However, I still can control charging with the We Connect app using the same account and I can drive, so who cares?

The speech recognition (which could solve the non-button issue) often triggers when listening to music on the radio. It mostly doesn't trigger when I want it to saying "Hello, ID". Pressing the right place on the steering wheel (not a button I can feel without looking at it) seems the best option to trigger speech recognition. When it's first activated, the only thing that sometimes works is turning on heat in the drivers seat. Gives me a nice and comfy feeling. Other than that, we don't communicate.

The ID.Drive Travel Assist sees lots of traffic signs that aren't there. At the most extreme, I was driving 100km/h on an open road. Suddenly the car "saw" a 30km/h sign that wasn't there and started braking. On my daily commute, I have to drive a road at 40km/h for some kilometers. Travel assist keeps on insisting that there are lots of 30km/h and 50km/h speed limit signs. Day after day. My uneducated guess is that crossing roads with other speed limits are triggering speed changes. IDK. Sometimes the travel assist does not work at all - no matter how many speed limit signs I pass nothing happens until restarting the car. So I more feel like being the assistants assistant.

I am still not able to use the "buttons" for turning on the wind shield or rear window heating without taking my eyes from the road (not part of the touch screen, they're located at the left side of the steering wheel). Guess I never will be.

The navigation is ok. Mostly works without ending up in a blocked road. Not always the smartest choice of way. Keeps my brain cells activated, I like making my own decisions anyway. Also, shows me logos ("ads"?) for McDonalds, Burger King, Esso, Shell and other sights on the road. Easy to see the places I want to avoid.

Charging mostly works. Hooray!

I've concluded that using the screen while driving is distracting anyway (so I wish there was not screen at all - except for maybe navigation and radio). When traveling alone, I mostly don't use the screen. When traveling with others, I outsource adjustments.

Would I buy the same car again? Not sure. Battery range is fine. Besides the software, I really enjoy driving it. From a usability point of view, I prefer driving my old e-Golf.

RabbitMQ. It just works.

I always thought of important as the sudo of styling.

I did the same thing. Bought a refurbished Thinkpad X250 and installed FreeBSD on it. Now it use it as my main development machine. I haven't look back since.

Two examples: The application has two main components, a controller and a struct containing the ui implementation. Callbacks in the cursive library are called with a reference to Cursive, but I had a hard time figuring out how to pass the controller to the callback. In the end I decided to use a message channel (mpsc::Receiver and mpsc::Sender) to let the two components communicate. After some struggling I saw that cursive has a function to set user data which is accessible inside the callbacks. So I pass the channels through userdats. Not sure if this is the best architecture. I never managed to pass a reference to the controller to the ui callbacks. The Compiler complained about undefined lifetime of the reference, though I knew that both outlive the application runtime.

A similar situation occurred in the asynchronous communication with gopher servers. I use a thread to fetch a resource from another server while keeping the ui responsive. Passing the result from the thread back did not work out in the beginning.

I don’t think the idioms are so different in Rust, but when passing data between components, threads and the like, you have to be very specific in your code, using Arcs, RwLocks, Mutexes, etc.

On the bright sight, when the code compiles, it usually worked as intended. Using C or C++, there would be more race conditions, null pointer exceptions and more.

I'm not affiliated with humblebundle in any way, and this was a genuine question. I know that the packt books are not best quality, but if one these books is a good introduction to practical ML, I would consider it a good deal. In my opinion much better than googling algorithms and tutorials and visiting 10s or 100s of sites full of ads and ad trackers to find a suitable algorithm for a given problem. Reading an EPUB on my daily commute sounds much better and works offline.