@davidgerard are they trying to pull a raspi? because that's how you pull a raspi...
Top-level
@davidgerard are they trying to pull a raspi? because that's how you pull a raspi... 3 comments
@drwho @feonixrift @davidgerard Regarding the RasPi situation, if you interact in more mainstream maker spaces, there hasn’t really been any noise at all. A lot of people truly couldn’t care less. I’m not sure there will be much impact regarding this Go telemetry stuff. @maddiefuzz @drwho @feonixrift @davidgerard It's a pretty big ask for folks to leave the raspberry pi ecosystem considering there basically isn't anyone else out there that actually supports their products. Step one for leaving the Pi ecosystem is "figure out how to build Linux for ARM" |
@feonixrift @davidgerard That might work to their benefit.
Of the entire RasPi userbase, how many folks actually got upset, kicked up a fuss, and gave up on them? Not many. We're a pretty small fraction.
Of the entire userbase, how many folks probably irritated them to no end by abusing and repurposing their products, causing lots of support issues and possibly IP hassles internally? Again, not many.
By losing us pains-in-the-ass their business situation improved by suddenly getting simpler because that leaves everybody who doesn't give a fuck for whatever reason. They're much easier to get along with, and thus make money from (because they're a business).
The same thing applies with the Go ecosystem. Plus, so much infrastructure is written in Go that you can't just lift and shift away from it. Not having to put up with us who think their telemetry thing is bullshit simplifies things. We're a small group that's easy to ignore.
@feonixrift @davidgerard That might work to their benefit.
Of the entire RasPi userbase, how many folks actually got upset, kicked up a fuss, and gave up on them? Not many. We're a pretty small fraction.
Of the entire userbase, how many folks probably irritated them to no end by abusing and repurposing their products, causing lots of support issues and possibly IP hassles internally? Again, not many.