(_____(_____________(#)~~~~~~
If they release them with a fully open driver that supports standard APIs (OpenGL, OpenCL, Vulkan) and release low-level documentation then NVidia’s proprietary trash will become redundant. Even better if they design them to be simple on a low-level so any programmer can just write their own driver/API/compiler. That would upset current software monopolies and the world would become a better place.
COW filesystems like BTRFS/ZFS with btrbk/sanoid are great for this. Only the initial copy may take a while, but after that it only takes the delta between the source and the destination to synchronize. On my main Server I have the OS on a single drive with BTRFS and all the actual data lives on a 4 disk zpool in raidz2. I have cron jobs set up to do hourly snapshots on both and I keep about a week worth of history. The BTRFS one gets synced to an external drive every 24 hours, while the zpool gets synced to another external 4 disk zpool on a weekly basis.
Next their VPS expires and the instance disappears completely. (I hope not). Reminder to any sysadmin to do regular off-site backups in case something like that happens.
Anyone who runs their own DNS can just add a record to their config (for example in unbound):
local-data-ptr: "37.187.73.130 hexbear.net"
local-data: "hexbear.net A 37.187.73.130"
RIP. It will be a miracle if they can get that domain back.
Interesting feature, I had no idea. I just verified this with gcc and indeed the return register is always set to 0 before returning unless otherwise specified.
int main(void)
{
int foo = 10;
}
produces:
push %rbp
mov %rsp,%rbp
movl $0xa,-0x4(%rbp) # Move 10 to stack variable
mov $0x0,%eax # Return 0
pop %rbp
ret
int main(void)
{
int foo = 10;
return foo;
}
produces:
push %rbp
mov %rsp,%rbp
movl $0xa,-0x4(%rbp) # Move 10 to stack variable
mov -0x4(%rbp),%eax # Return foo
pop %rbp
ret
That’s literally what I’m saying; It’s fine as long as there wasn’t any unwritten data in the cache when the machine crashes/suddenly loses power. RAID controllers have a battery backed write cache for this reason, because traditional RAID5/6 has the same issue.
BTRFS RAID5/6 is fine as long you don’t run into a scenario where your machine crashes and there was still unwritten data in the cache. Also write performance sucks and scrubbing takes an eternity.
I’ve given up on Element a long time ago. I’ve been bouncing between Nheko and NeoChat since those are the most mature Matrix clients that aren’t bloated webapps.
What bugs me more is encryption still is kind of a mess across devices and clients. Also I hate how there still isn’t any alternative Matrix Server that’s not Synapse or Dendrite and isn’t abandoned, doesn’t suck, is relatively fast and supports at least most of the Protocol. Can’t even really blame people because I’ve tried writing my own Matrix Server and Client before but I eventually gave up because the protocol is what I call “A JSON clusterfuck”. Why can’t the protocol be as simple as IRC? Why does it always have to be JSON over HTTP?