I think one can appeal to the morals and desire to be good/useful with a community mapper, but one cannot with a corporation, especially a publicly traded one.
If Facebook decides that the metadata format/style for a particular field should be X because otherwise they'd have to spend $______ of engineering resources on reworking their mobile app and fuck the OSM community which has decided it should be Y, for completely valid reasons that were debated and decided upon by the community....and then all of their hundreds of 10-cents-an-hour drones start submitting changes with the new style...the community is screwed. Especially if it accepts money from Facebook, because there's a power imbalance no matter how much paperwork you have saying "thou shalt not get anything from thy donation."
If you want a great example of how corporate involvement corrupts - look at Firefox, which has been caught not only with its hand in the Collecting User Data cookie jar, but inserted software for the makers of a TV show (Mr. Robot) and software nobody asked for, with no way to disable it (Paper, I think it was/is called?)
Not only did they get caught with their hand in the Collecting User Data cookie jar, but when someone brought it to the public's attention via the bugtracker, the bug was locked almost immediately by a mozilla employee. Then that was reversed. Then the project manager for said project who had previously worked at a data analytics company re-classified the bug as secret/internal-only, and it quietly all disappeared under the rug.
> Seems the newest version determined that my quad core Xeon processors didn't support SSE 4.2 or later. A LOT of people were fuming online that in order to run the latest version, they would have to get a new PC or laptop with a new processor that was now required for the newest version.
I was with you until I looked up when SSE 4.2 was introduced.
SSE 4.2 was introduced in the Nehalem architecture...twelve years ago for desktop processors, ten for xeons. I really don't see anything wrong with Adobe requiring a processor newer than ten years old for software used by and large by creative professionals, people who make money with it.
If you're a creative professional working off a twelve year old computer, you're wasting money just from lost productivity waiting on that system - as well as flushing money down the drain on all the wasted energy running the system, unless you live somewhere electricity is insanely cheap.
A new computer would literally pay for itself in reduced power consumption alone, both idle and loaded wattage. A Ryzen 3600 uses less than half the power of a lot of xeon chips, has a single-core performance 50%+ higher than the very fastest second-gen quad core nehalem, and has two more cores.
Same goes for a modern GPU - everything is GPU accelerated these days, and you can get a several year old Nvidia card that is so power efficient the fans aren't even spinning most of the time.
Then there's the huge performance boost of NVMe.
The list goes on. Dude(tte). Buy a new computer. Or one at least made in the last 5-6 years?
If Facebook decides that the metadata format/style for a particular field should be X because otherwise they'd have to spend $______ of engineering resources on reworking their mobile app and fuck the OSM community which has decided it should be Y, for completely valid reasons that were debated and decided upon by the community....and then all of their hundreds of 10-cents-an-hour drones start submitting changes with the new style...the community is screwed. Especially if it accepts money from Facebook, because there's a power imbalance no matter how much paperwork you have saying "thou shalt not get anything from thy donation."
If you want a great example of how corporate involvement corrupts - look at Firefox, which has been caught not only with its hand in the Collecting User Data cookie jar, but inserted software for the makers of a TV show (Mr. Robot) and software nobody asked for, with no way to disable it (Paper, I think it was/is called?)
Not only did they get caught with their hand in the Collecting User Data cookie jar, but when someone brought it to the public's attention via the bugtracker, the bug was locked almost immediately by a mozilla employee. Then that was reversed. Then the project manager for said project who had previously worked at a data analytics company re-classified the bug as secret/internal-only, and it quietly all disappeared under the rug.