Search results

Yes, the "free" in FOSS is "libre" not "gratis." Free as in freedom, not free as in beer.

In my personal experience, proprietary codebases are about a thousand times more likely to be rats' nests of ugly kludges and hacks. Like the Lovecraftian monstrosity that I inherited last year, which haunts my nightmares.

I don't mind the waiting so much, but the question that's gnawing at me is: now that we've done all the hard work of designing and implementing the Pyra, how much effort will it take to create a Pyra 2.0? (Assume we use nearly identical case, screen, and inputs, and just upgrade the SOC/PCB.)

I'm not too concerned about leaking private data from my Pyra. The most private data on my Pyra will be saved games from my emulators. ...and maybe the root password to my device (and my luggage).

You know about Busco Quadnary?

It's Two Months somewhere*. * In some inertial frame.

You would only be guilty of 0.000004% of the suffering if a 100% tantalum Pyra would account for 100% of the suffering in the world. It would be a tiny fraction of a device (percent tantalum) that is a tiny fraction of the market (of devices containing tantalum). (I was going to add further...

I have nothing against x86, but I really can't see us switching instruction sets this far in. Or maintaining repositories with binaries dual-compiled for two different instruction sets.

I assume if it's using half the power it's also producing half the heat, which would be nice. I'd consider a significantly more efficient, if slightly less performant, SOC to be an "upgrade." (DISCLAIMER: I know shockingly little about these things and am probably completely wrong.)

I can instantly spot a non-native speaker because they use "whom" correctly.

Ah. My working directory was a symlink to My Documents. That explains it. I extracted it fine under my home directory. I got as far as the make step in building dosbox and then Which really somehow looks more like an error in the code rather than in my environment. I don't know.

I was working in the Linux subsystem, and tar printed a ton of cryptic "invalid argument" messages, that I Googled were related to an invalid filename. I looked at the files it was printing errors for, and they all had : in their filenames. Finally, I tried several methods of creating such a...

I can't extract the rootfs because Windows doesn't allow ':' in filenames. I guess I can do this part with Docker at least.

You can actually choose from a few available distros. It's installing dependencies; it looks like it will work. Thank you. So I can hypothetically create an image that will run natively on Pyra, but I can't actually run it until I get mine. Would emulating an ARM device such as a Raspberry...

@xnopasaranx I've used Debian-based distros before (and RHEL and SLES and some BSDs), and I've used the Pandora a bit. I prefer to develop on Windows. I've never compiled before anything for ARM though. I was able to compile and run some C++ code for Ubuntu on Windows from the Linux Subsystem...

But octopodes come from Greek, not Latin.

There's the Linux Subsystem for Windows 10. It might work with that. I'll give it a try. But I was really hoping I could try running things on the Pyra OS. To test but also as an early taste of what using the device would be like.

Sorry in advance if this is all spelled out somewhere already. I have some spare time over the holiday and I thought maybe I'd try writing a game or something for the Pyra. I guess first I would need some sort of emulated ARM machine with the Pyra OS running on it. Then I need a compiler...