A whole lot of people here don’t read MBFC each day and it shows. They tend to take a single and testable claim and make a decision. It’s really easy to see if the claim is true or false if the claim is specific. They don’t have a habit of taking a big claim and ruling it false because of one small detail like Snopes does.
My approach would be to have the Python script read the serial console of the microcontroller in a loop and parse the text data exchanged through it. Binary can work too but then you’d need to implement the necessary logic to figure out if you’re done reading or not.
Through things like udev rules you can automatically start such a script when the device is detected (i.e. the cable is plugged in).
Something like this should work, depending on the settings of your serial connection:
<span style="color:#323232;">#!/usr/bin/env python3
</span><span style="color:#323232;">import serial
</span><span style="color:#323232;">
</span><span style="color:#323232;">ser = serial.Serial(
</span><span style="color:#323232;"> port='/dev/ttyUSB0,
</span><span style="color:#323232;"> baudrate=57600,
</span><span style="color:#323232;"> parity=serial.PARITY_ODD,
</span><span style="color:#323232;"> stopbits=serial.STOPBITS_TWO,
</span><span style="color:#323232;"> bytesize=serial.SEVENBITS
</span><span style="color:#323232;">)
</span><span style="color:#323232;">
</span><span style="color:#323232;">while(True):
</span><span style="color:#323232;"> line = ser.readline()
</span><span style="color:#323232;"> # Do something with the line of text that was just read
</span><span style="color:#323232;"> print(line)
</span><span style="color:#323232;">
</span><span style="color:#323232;">ser.close()
</span>
The udev rule depends on how you connect to the device, of course. Also make sure to mark the script as executable if you call it directly. First improvement I’d make is to figure out how to detect the device (instead of hard coding ttyUSB0) and the correct parity settings.
If you were getting bald (which you might not) you’d have 2 options:
hair transplant (if needed) and medication for the rest of your life.
shave/trim and move on
I’m generally for team 2. I’d hate medicating (which from internet opinion has various long-lasting unwanted side effects) for the rest of my life for such stupid thing.
I must confess, I have the benefit that I don’t look that bad. Also, being fit becomes much more required when bald, 😅, you have to compensate your older look; and side effects from exercise are virtually all positive. So I’ll take it.
WSL2 exists for the very reason, if you hate using Windblows, you can install Linux OS on top and do everything from the Linux VM. Why even bother struggling with Windozes interface and software ?
I have to use Windows on my work computer and I am finding it hard to get FOSS applications on Windows that can do stuff like
The Gold standard in the screen recording world is OBS. It’s not only available for Linux, but also for Windows and, well, is the gold standard. If you ask the question if OBS can do this-or-that regarding screen recording, the answer generally is yes (or “yes, via plugin”). Just use OBS on all platforms, it’s clearly the most mature screen recording tool out there.
While I understand and empathize with your dislike of proprietary blobs (fuck you, NVIDIA), every game is a huge blob unless you’re playing FOSS games exclusively.
Tell me about it English is a bastardised language made up of so many different languages rules. Have you heard of Lee and Perrins Worcestershire sauce? It’s pronounced wuster-shere.
Great sauce btw, real umami flavour and great on cheese on toast.
kbin.life
Oldest