Oh yeah, man, FoxPro... for a year or so in 2008 I was responsible for a FoxPro database of music venues and artists for an agency. Felt really interesing to maintain a system that's older than me.
When we modernized all desktops in the office, I set up Win2k in Qemu on each of them, which loaded the FoxPro thing from a shared network mount. I'm just realizing 19-year-old me never checked if FoxPro supported simultaneous access. It surely did, at least I hope so :-)
edit: However, 19-year-old me was smart enough NOT to touch that Solaris or whatever-it-was server hosting the FoxPro thing.
Ignite looked intruiging when I checked it out recently - but I need to import rootfs tarballs directly, without going through any registries. Any helpful pointers are appreciated :)
I think performance is just a top priority as security, I remember how in their first whitepaper they already talked about how they batch up packets and stuff like that. Also the whole approach of kernelspace instead of userspace is just for performance.
Actually, I think in the beginning there was even a "marketing chart" with throughput numbers in addition to the chart with lines-of-code numbers?
Edit: performance being a top priority also makes sense strategically: if you want people to use secure software en-masse, then the experience needs to be stellar in UX and performance as well.
I was in the same boat regarding polluting my development environment - nowadays Steam's Wine/Proton stuff is completely containerized and just works ("Steam Runtime").
Ah I did not know that, thanks! - My dozen or so cases have always had a court order attached. Worrying that there are ISPs that hand out data without one...
They need to go and get a court order, and with that they request the personal data from the respective ISP. The whole process is pretty steamlined and partly automated though.
Source: have been through many copyright claims and currently have a supreme court lawsuit pending.
It's actually up and running for a while, with large sums already staked, and the flipping of the switch on mainnet will very likely happen before end of summer. https://ethereum.org/en/eth2/staking/
Yep, lots of interference with my bluetooth headphones. On Linux it gets a little better if you disable the wifi driver option for "bluetooth coexistance" (it's named slightly differently between the various drivers).
I don't actually use wifi, but I suppose it's got something to do with wifi and bluetooth being handled by the same mPCIe card.
It's the COMMITTER_EMAIL and AUTHOR_EMAIL as configured, this is working as intended. If you don't want to add it to your commits, set it to something like "nobody@localhost".