scurry
@scurry@lemmy.world
- Comment on Unity's Plan Won't Work, but Someone Else's Will | TechnoFeudalism in Games and Beyond 1 year ago:
MonoGame/XNA used to be more relevant 10 years ago, but not so much any more (funnily enough, in large part because Unity ate their lunch).
- Comment on Whatsapp has begun working on support for third party chats (Telegram/Signal) 1 year ago:
Anyone can build an implementation of the Signal client, but few do already because Signal actively works to prevent them from working with the Signal infrastructure, and likely will continue to do so. It’s one of the more common complaints about Signal, but it was built on the assumption that centralized services would be easier to use and to make private if the platform holder wanted, as well as more robust against attacks. They could well be wrong, and people just haven’t thought of and deployed the right tech, but it’s neither here nor there; I’m doubtful they can be convinced on this, and I’d doubt they’d be made to open up anyway by this regulation, meaning they’re not obligated to.
- Comment on Whatsapp has begun working on support for third party chats (Telegram/Signal) 1 year ago:
Awaken from thy slumber XMPP! Bring us new and better implementations and standards, and the network effect we once enjoyed now solidified by law.
- Comment on Google Chrome now targets ads based on your browser history, here's how to turn that off 1 year ago:
I’ve never used Edge — is it really that bad?
- Comment on libmem_cpy-strnrrn-std-clib_Cmvaeffc_ld-TWA_nif.aarch64(32bit)2-0.13.2-23.2.so.7(3).1.1.gz.conf 1 year ago:
At one point it was both. At one point they internally added support for longer file names in DOS, and then a later version of the filesystem also started supporting it. I think that on DOS and Windows (iirc even today), they never actually solved it, and paths on Windows and NTFS can only be 256 characters long in total or something (I don’t remember what the exact limit was/is).
- Comment on libmem_cpy-strnrrn-std-clib_Cmvaeffc_ld-TWA_nif.aarch64(32bit)2-0.13.2-23.2.so.7(3).1.1.gz.conf 1 year ago:
I agree, and these conventions are being followed less over time. Since the 1990s, Windows world, Objective-C, and C++ have been migrating away (to mixed results), and even most embedded projects have been too. The main problem is that the standard library is already like that, and one of C’s biggest selling point is that you can still use source written >40 years ago, and interact with that. So just changing that, at that point just use Go or something. I also want to say, shoutout to GNU for being just so obstinate about changing nothing except for what they make evil about style. Gotta be one of my top 5 ‘why can’t you just be good leaders, GNU?’ moments.
- Comment on libmem_cpy-strnrrn-std-clib_Cmvaeffc_ld-TWA_nif.aarch64(32bit)2-0.13.2-23.2.so.7(3).1.1.gz.conf 1 year ago:
Yes. Memory and storage were at a very high premium until the 1990s, and when C was first being developed, it wasn’t uncommon for computers to output to printers (that’s why print() and co are named what they are), so every character was at a premium. In the latter case, you were literally paying in ink and paper by the character. These contributed to this convention that we’re still stuck with today in C.
- Comment on Some veteran YouTube staff think Shorts might ruin YouTube 1 year ago:
The article indicated that, apparently, Shorts is even more unprofitable than regular YouTube. So they don’t even have that going for them
- Comment on It's not just you — no one is posting on social media anymore 1 year ago:
McBane thats the joke.gif
- Comment on It's not just you — no one is posting on social media anymore 1 year ago:
That’s a bit cruel to Gary, Indiana, don’t you think?
- Comment on In an alternative universe 1 year ago:
I’d just like to interject for a moment.
- Comment on Remember your training and you will survive 1 year ago:
Go for the door at the back. Its contents will spill out and it won’t have the momentum to hurt you anymore.