I feel like there's a difference between the car regulation you state and the regulation approach being taken in the EU. Specifically the ability of third parties to limit end user choice.
With vehicle repair, I can still choose to use the manufacturer operated/approved repair shops. I truly am gaining additional choice and can continue to service my car as I always have.
The EU regulations allow third parties to remove my choice to live in the walled garden if they wish. So while it could enhance competition for developers I don't know if it greatly improves the users choice, or experience.
The media is likely reporting incorrectly here. Apple has come out and stated that they view the judgement as a major win for their side and Epic has come out and said they intend to appeal. The cliff notes I've seen on why are that Apple is legally not a monopoly, does not have to provide an alternative payment processor 'in-app' and may still legally charge a commission fee on each purchase, even if completed through an external payment processor.
Once I gave up on Scroll Revserser, I found Mos[1] as another option for this need. It just got a new v3 release and allows for toggleable smooth scrolling, as well as very granular scrolling options on top of the scroll reversing. I'm a big fan.
I'm trying to wrap my head around the use case here. I love to support well crafted native software so don't take this as a negative question. I often use a tool such as Arq or Veeam to create snapshots in time of a folder or set of folders that then get uploaded to a remote storage location or repository, to recover files or documents from that time. I also use cloud storage providers to keep a copy of data that I am working on in sync between devices.
I can't seem to tell but this product seems to be missing any additional features to really fill a role that I lack. It doesn't appear to make incremental copies of the data set to allow me to roll back in time, it does track deleted items but interim changes are not kept or tracked, so it's really just a capture of the state of the folder at last run time.
It's compared to robocopy but the tool assumes an empty initial destination directory, there's no facility for copying data into a directory with content in it already, so it's can't be used as a general file transfer tool.
It seems the best use case is for say transferring a directory of tarball dumps to a remote location over SMB?
You can grab build artifacts from builds of the master branch off their CI. You need to enable developer mode to allow the loading of an unsigned binary.
The article covers this. Intel was going to build FireWire into their chipset which would make the technology ubiquitous but at the time Steve Jobs swapped the licensing model from a flat fee to pricing per port which pushed Intel away. If Intel had bought into FireWire PCs would have the port.
If you look at why the application was built I would say it's not as silly as it sounds. It was built as a fun side project for GNOMEs 20th anniversary and was used to test starting a project using GNOME Builder. https://blogs.gnome.org/mclasen/2016/12/02/gnome-loves-to-co...
I doubt it's something they took a serious amount of time on.