I think I'm more fed up with people making those quotes "rust will change everything" when, in fact, it will rule out many if not most memory corruption as you said. Reading your comment, I see now it's the mentality "everything need to be in rust" that bothers me the most, which in fact means "rust can bring memory safety" and not "rust will replace everything". Alas I'm seeing it used times and times again as the latter instead of the former.
I'm getting fed up about all those articles "rust x something: the future?", "I rewrote
<cli tool>
in rust it's now memory safe". I get the rust safeties and all, but that doesn't automatically make everything great, right ? You can still write shit code in any language that can RM -rf all your disk, or let security gaps here and there without intending to.
I mounted a disk of a server in rescue mode, since I needed to extract everything (the provider didn't have the option to dump everything as a zip). Then installed an FTP server, added a user/pass, it worked.
But I couldn't access the files of the original disk, even though I could see them. So I just chgrp/chown the original files, since the disk was just "mounted" in the rescue disk /mnt, I thought it was alright (at the time I thought permissions were volatile, stored separately from the files). I could now download the entire disk, yay!
Upon booting the original disk again, a bunch of errors: shell not starting, tools not running, because they were owned by user and not root...
Well we reinstalled all the server from scratch that day.
I created a discord server for an open source project of mine, but grew to dislike it. It got spammed multiple times, people are off topic and talking about their lives in channels that aren't for that, and so I started pushing the community toward GitHub discussions.
Discord isn't searchable, nor archivable, nor public, but GitHub is (I'm aware of another conflict with Microsoft for some people, but to me this is the easiest solution to get contributors and have an easy CI setup).
I haven't had much success yet, but I'm slowly shutting down all links to the discord and will let it die (for outside contributors at least). I might keep it to stay in touch with a few developers, to refine issues and prepare migrations that aren't ready to be turned into public discussions/ issues / pull requests.
I use a plain 34 keys layout based on qwerty for letters, comma/dot/semicolon. The numpad and symbols layers are handcrafted so that every symbol is easy to reach, it's also optimize to type things like <- and -> easily
I understand the philosophy of not wanting to transfer your rights, but I don't understand what's bad about contributing to a project and having your code given to the community (as-in copyright transfer to the organisation).
Would this be because the org/owner can just start selling the code or is there something that I'm missing?
That is, until the community reverse engineer the communication between the tablet and keyboard. It's through the 5 pins, serial iirc? The complicated part would be to produce/find a decent keyboard
This isn't selfhosted but you can use uptime robot. They can send regular http get requests or ping an IP or URL, the free tier can have like 10 monitors I think?
I receive an email when an host isn't available, in 5 minutes usually.
The hori split pads are great, but you can't use them wirelessly. And the adapter that exists to use the pad not on the Switch is wired. Otherwise it's 100% better and have really nice joysticks (now I can't use that as an excuse for loosing on Mario kart...)
That's my point, maybe it wasn't clear enough. I think people that need to transfer a lot of data often to and from their phone can justify taking the Pro model (photographers, video makers, etc)
Do you really use USB-C to transfer data or to charge your phone? It's been years since I used it for data, so I don't think that's a problem, in a world where cloud is becoming the norm.
There is still the journal you could use to recover the old state of your database. I assume you commited after your update query, thus you would need to copy first the journal, remove the updates from it, and reconstruct the db from the altered journal.
This might be harder than what I'm saying and heavily depends on which db you used, but if it was a transactional one it has to have a journal (not sure about nosql ones).
Luckily the GB(A) consoles are the easiest to mod nowadays, to add backlight, rechargeable battery, better audio... IMHO this is still the best way to enjoy GB/GBA games, instead of emulators which can be buggy/force me to stay on the computer (or worse, on my phone)
I think I'm more fed up with people making those quotes "rust will change everything" when, in fact, it will rule out many if not most memory corruption as you said. Reading your comment, I see now it's the mentality "everything need to be in rust" that bothers me the most, which in fact means "rust can bring memory safety" and not "rust will replace everything". Alas I'm seeing it used times and times again as the latter instead of the former.