> Alongside these games there have always been small groups of men moving around groups of small men in a basement somewhere re-enacting some battle or other.
Maybe I'm splitting hairs, but GP called it a copyright violation and my understanding is a "clean room" reverse engineering for interoperability was fair use and not a copyright violation.
Yes this does threaten Blizzard's business model so I understand why they'll go after Turtle, but that doesn't mean we have to care or let them prosecute Turtle for Contempt of Business Model.
Now, if Turtle used Blizzard's WoW trademarks to advertise and make money, I fully agree that violates their _trademarks_ and can be litigated as such. But if Turtle somehow didn't do that (and still sold access to their compatible WoW backend), I'd be interested to hear if that is somehow still a copyright violation.
In the discussion of the Triforce arcade compatibility, there's some discussion of "IC Card" support needing to be implemented, and doing so unlocking a lot of missing functionality.
I think this is referring to the Japanese rail payment cards? I know you can use them on things like vending machines, but from the article it seems like the Triforce cabinets let you save game progress on them too, which would be a great feature I've never seen in US arcades.
IIUC, if you have the source you can recompile said Windows app with LiteBox to statically link in the Windows OS kernel dependencies, so it'll run on any compatible processor regardless of OS (since it won't be making syscalls anymore). It's a unikernel basically.
That's the theory, but I don't know how far LiteBox is along to supporting that workflow.
Would you mind pointing me at the research you found? I've been looking for studies that correlated hypoxia and autism (and related interventions that might help) but I haven't been successful.
There are certain genetic markers you can test for, but not all forms of autism appear in the tests we have today.
Then there's things like the folate blocking antibody (https://pmc.ncbi.nlm.nih.gov/articles/PMC4783401/) which you can do a blood test for, but again not all people with autism have the antibody.
Yes it's exactly the one-off situations like that, which aren't super often but occur enough to greatly inconvenience someone without a pocket browser.
I've been trying to do this too - paring down distracting apps, leaving only essentials like communication, maps, uber, etc. But my problem is what to do about the browser? I feel it's too essential to the "long tail" of uses (as the author put it), but also among the most distracting apps on my phone.
- Money (the concept) is useful to society as a store of value, so you don't have to waste effort bartering for things.
- Adding on to that, credit is useful to society since it lets humanity even more efficiently allocate its good and labor (stored as money).
- Finally, stocks, insurance, and other financial instruments are additional advanced developments on top of credit, where groups of humans (companies) can take on even more risky endeavors supported by investors or insurers.
So my view is companies like Jane Street facilitate these complicated value transfers, to let (e.g.) a spaceship company draw on resources generated by growing crops, selling shoes, giving haircuts, etc via a convoluted path through stocks, ETFs, whatever.
I think Git was initially more popular and that had compounding effects that made it eclipse Mercurial.
In 2010 or so we tried to adopt Mercurial at the small company I worked at, but the support for Git was just so much better - even back then. Git's popularity meant that tooling, documentation, and general ease of finding people to ask questions was 100x easier with Git, so we switched. I'd imagine the same thing played out many times over.
A few FAANGs did and still use Mercurial, but they're on their own islands and don't really affect the wider tech ecosystem.
I'm self hosting Readeck (https://readeck.org/en/) and I really like it. It's nicer than Pocket was, the website extraction seems to work better, and it can't ever be shut down.
For my Kobo, I wrote a mod that lets me redirect Pocket API requests, and a small proxy server that translates Pocket API calls into Readeck calls.
So far it's working flawlessly and my Kobo is using its built in Pocket viewer for Readeck instead. I'm hoping to open source it soon so others can use it.