Software Engineer, Linux Enthusiast, OpenRGB Developer, and Gamer

Lemmy.world Profile: https://lemmy.world/u/CalcProgrammer1

  • 0 Posts
  • 335 Comments
Joined 3 years ago
cake
Cake day: June 9th, 2021

help-circle


  • CalcProgrammer1@lemmy.mltoTechnology@lemmy.worldWhy is UI design backsliding?
    link
    fedilink
    English
    arrow-up
    38
    arrow-down
    3
    ·
    10 days ago

    Change for the sake of change is so dumb. I’m tired of pointless UI changes every so many years because some middle manager and their designers need to wow some dumb exec to get a promotion and they do so just by rearranging all the existing functionality because the product itself is already a complete solution that doesn’t actually need a new version. Sadly, this mentality even creeps into FOSS spaces. Canonical and Ubuntu wanting to reinvent the wheel with Unity, Mir, Snap, etc. GNOME radically changing their UI all the time.







  • I wish these implementations of secure boot were designed more to protect the SOFTWARE against “theft” than the HARDWARE against “tampering”. Let us wipe the secure boot keys, but in the process erase the firmware (or have the firmware encrypted so that erasing the keys renders it unbootable) and then allow new code to run. Blocking third party firmware on consumer devices is a shit move. It just creates more e-waste when the OEM stops updating it and the community can’t make their own replacement firmware.




  • Not really a fan of putting secure boot on. The only purpose that serves is locking the customers out of their purchased hardware. Raspberry Pi is clearly not targeting the maker market with those changes, they want that corporate money and are willing to stick the finger to hackers and makers in the process. Can’t make custom firmware if you can’t boot it.







  • Linux works well on supported ARM platforms, but the problem is that a lot of ARM platforms aren’t supported. I recently got a Xiaomi Pad 5 Pro (had to import it as it’s a China-only model) and put postmarketOS on it. The experience is surprisingly good. Paired with a Bluetooth keyboard/touchpad, it is basically as functional as a normal light-duty Linux laptop except for the lack of x86 support, which mostly just means no gaming. I have been attempting to run Steam via box64 and FEX, but pmOS isn’t a supported distro for that so I have been trying in a Docker container and in Distrobox. I managed to get it started but it crashes due to steamwebhelper, and I think it’s a dependency or configuration issue. Otherwise, for browsing, coding, videos, terminal use, office, etc. it’s great and the battery life is amazing compared to my laptop. This is on a Snapdragon 870. Open source games run and they can hit 120fps on the 120Hz screen. I hope to see ARM support continue to improve, but I am worried about bootloader locks on these new ARM Windows machines.



  • I’m not sure about FF specifically, but 99% of the time you’re connecting a microcontroller to a PC you’re doing so over a serial port (UART) of some sort. It may be a physical COM port or it may be a USB to serial adapter or even a purely virtual serial port over a USB connection, but the methodology is all the same. Unless you are running a serial terminal on that port (as in, a commandline on your PC served on the given /dev/ttyX interface, not a terminal emulator letting you read/write from the port), the microcontroller can’t just run scripts on the PC. Instead, you will want to write a script/program that opens the port and waits for a command to be sent from the microcontroller, then that listener script can execute whatever functionality you require. Note that only one application can have the port active at a time, so if your listener is a separate program from your event handler, you will have to close the port on the listener before running the handler, then reopen the port on the listener once the handler is done so it can start listening for the next event. Better to just make it all one program that is always running on the PC and does both listening for events and handling them so there’s only one program that needs access to the serial port.