To my knowledge, PayPal does not hold funds “forever”. They penalise the account holder by locking it away for 180 days. At that point, they can withdraw the balance to a bank account. I have multiple friends and clients who had this happen to them, but in all cases, they were exposed to higher risk by accepting payments through donation forms, or a marketplace where they sell directly to customers. (Despite what feels like an anecdotal high failure rate, somehow I’ve never had an issue running my own marketplace for the past decade.)
Legacy Update is my project, appreciate the thoughts. I’ll look at both. OpenCollective would be a great idea going forward for better transparency, as much as it requires more paperwork.
I do consolidate most of the expenses with my other projects, and ads cover most of the costs, but we’re planning some future projects such as hosting of custom Windows updates (opt-in) that will get expensive. So this will matter a lot more soon enough.
Thanks for spreading the word John, it means a lot. In my teen years I discovered PortableApps and would read through the forum threads, fascinated by the ways the community tricked apps into being portable. Another incredible resource, and I really respect that it’s stayed around so long.
It’s hard to teach people it’s worth their time to double-check these things of course, but I try to show a chain of trust:
1. Files come from Wayback Machine, which is trusted to serve legitimate snapshots
2. There is a sha1 and size listed for most files (though these come from Wayback)
3. Checking signature is easy enough from Explorer
Perhaps a page on “how to know this is legit” is a good idea to help educate about this. The goal of the project is to have legitimate downloads with good SEO, without having to cut through ads/spam/sketchy redirects (still has a few ads but intentionally non-obtrusive), so people aren’t blindly downloading from sketchy sites.
> Then, how could native apps have much better performance on the same hardware, on both Android and iOS?
Web engines were honestly not great back then. WebKit was ok but JavaScriptCore was very slow, and of course that’s what iOS, Android, and BB10 were all running on that slow hardware. I have distinct (bad) memories that even “GPU-accelerated” CSS animations were barely 15fps, while native apps reliably got 60fps unless they really messed up. That’s on top of the infamous 300ms issue, where every tap took 300ms to fire off because it was waiting to see if you were trying to double-tap.
So I really think some of the blame is still shared with Apple, although it’s hard to say if that’s because of any malicious intent to prop up the App Store, or just because they were under pressure to build out the iOS platform that there wasn’t enough time to optimise. I suspect it was both.
Note: A Microsoft account isn’t required to download free apps from the Store, it works fully without extra prompts on a local account. (I like that it works this way, because it means you can install Firefox on a fresh install of Windows without even once opening Edge.)
No - one dev evangelist accidentally diverged from the marketing language for Windows 10, and now his words in a conference talk nobody previously cared about are being used as “proof” Microsoft lied. It’s like if Bob from accounting accidentally mentioned future plans on his LinkedIn years ago, then years later it’s being used as proof of the company going back on their words, despite them issuing a statement back then distancing from it. At some point, someone in a big company will say the wrong thing out loud and it needs to be carefully retracted without confirming or denying future plans.
Note: This appears to be a fork of Sam Henri Gold’s recent lid-angle sensor project, with the wav file changed. The readme does give credit, though the license has been changed from Apache to MIT for some reason.
On the Pro tier, it’s a fixed monthly price with fixed quota per 5 hour window.
That said, every time I’ve tried it, it’s spent ages writing code that barely works, where it keeps writing over-engineered workarounds to obvious errors. Eventually, it gives up and decides broken is good enough, and returns to the prompt. So you still have a point…
