We should just call it loading. Loading from an app store we can call simply, mortgaging our cognitive liberty and liquidating the middle class for comfort or MOCLALTMCFC.
What we talk about when we talk about sideloading
11–20 of 646 posts
Re: What we talk about when we talk about sideloading
#12Everyone developer who worked hard to make windows phone die. Hope you're happy.
I was a telco product manager at the time and I can tell you right away that it wasn't developers that killed Windows Phone. This book (https://asokan.org/operation-elop/) tells part of the story, but the telcos I worked for (and competed with) definitely played a big role.
Re: What we talk about when we talk about sideloading
#13> https://keepandroidopen.org/
The UK petition link appears to be broken:
Re: What we talk about when we talk about sideloading
#14Everyone developer who worked hard to make windows phone die. Hope you're happy.
> who worked hard to make windows phone die
You mean Microsoft? No backwards-compatibility with Windows Mobile to begin with (so companies can't reuse their existing investment into line-of-business apps on actually nice modern devices either), then they reset the ecosystem 2 times (once during the WP7->WP8 transition, another time during the Windows 10 transition).
Re: What we talk about when we talk about sideloading
#15The existing comments here somehow display a big amount of discomfort with the semantics of the article, not so much with the points argued...
Sorry, but "welcome to HN?" Commenters here regularly miss the forest for the trees, ratholing on minutiae and nitpicking one or two words in a 1000 word article. Often totally missing the overall point. We're notorious for it.
Re: What we talk about when we talk about sideloading
#16I think we could set the bar substantially higher. Don't even bother with discussion of sideloading. Talk about bounded transactions and device control.
What is needed is: Once I have purchased a device, the transaction is over. I then have 100% control over that device and the hardware maker, the retailer, and the OS maker have a combined 0% control.
Re: What we talk about when we talk about sideloading
#17Everyone developer who worked hard to make windows phone die. Hope you're happy.
Let's not pretend that MSFT would have been one tiny bit better here.
Re: What we talk about when we talk about sideloading
#18The existing comments here somehow display a big amount of discomfort with the semantics of the article, not so much with the points argued...
Dear F-droid, please edit your article to be technically correct so that HN can like it. All you have to do is change "coined" to "popularized".
Re: What we talk about when we talk about sideloading
#19On MacOS it warns you when you're about to open an app you've downloaded and installed yourself. "Foo has been downloaded from the internet, are you sure you want to open it?". It doesn't stop you from installing it. Why should doing so on your phone be any different?
Re: What we talk about when we talk about sideloading
#20As an iOS user who's been frustrated with Apple's approach to "self-loading" (i.e., running your own code on your own devices) and who's actually gone out and gotten Android devices to write PoC/PoV apps on instead, I really don't like Google's stance on this--even if I would not, at this time, choose to daily drive an Android device, I do rely on F-Droid for getting software on six or seven different devices _right now_ and they would be useless to me if I couldn't do it.