• 0 Posts
  • 24 Comments
Joined 3 months ago
cake
Cake day: April 13th, 2024

help-circle


  • The lede by OP here contains this:

    […] addition to Xcode 16 […] is a feature called Predictive Code Completion. Unfortunately, if you bought into Apple’s claim that 8GB of unified memory was enough for base-model Apple silicon Macs, you won’t be able to use it

    So either RecluseRamble meant that development with a feature like predictive code completion would work on 8 GB of RAM if you were using Linux or his comparison was shit.











  • Sometimes it really annoys me if a perfect spot for a proper “whom” is missed. Even worse though is a misplaced “whom”. Both instances are easy for me to spot because we decline pronouns quite a lot in German.

    Edit: Sorry that’s not a construction, so much as just an error. For constructions one thing that gets on my nerves is if you try to tell someone about your previous state of mind to clear up a misunderstanding like “I thought the water had boiled already” and then they say “no” to tell you that your assumption was incorrect. This is annoying because first of all the information they are conveing is already known to you by the time of this discussion and secondly in the grammatical sense they are actually disagreeing with your state of mind, not the content. I always have the urge to say: “Yes, actually, I’m telling you that’s what I thought, you can’t disagree with me about what I was thinking.”




  • Lolita by Vladimir Nabokov

    It’s so creepy because you read the repeated sexual abuse of a minor through the eyes of the perpetrator who continuously justifies his acts and misrepresents Lolita’s reactions. He’s a very unreliable narrator. First he even becomes her stepdad to have better access to her. Then her mother dies, through a car accident just before she can call the police on him. Again this is recounted through Humberts eyes, so I’m thinking it was actually murder.

    I haven’t finished the book yet, it’s kind of hard to read. It’s been a few years, and I should be somewhere in the middle IIRC.




  • AV1 is based on VP9. Google made VP9 and it’s open source and royalty free.

    Google just joined the Alliance for Open Media and gave their VP9 as a starter for AV1 instead of making some other successor called VP10 or something on their own.

    During development of AV1 Google contributed a lot to libaom, the reference implementation in C++, but since this codebase grew together with the codec it is not the most clean design. Also the reference implementation benefits from being clear more than being fast.

    Therefore, instead, these days the later projects rav1e (encoder in rust, started by Xiph Foundation) and dav1d (decoder in C, started by the VideoLAN non-profit) are the fastest, because they started from a green field approach when the wire-format for AV1 was mostly fixed and they focused on speed.

    I think overall Google’s stance on the Alliance for Open Media makes sense. As part of the new media streaming techno bubble they (as well as Amazon, Facebook, even Microsoft) have an interest in getting an interoperable royalty free codec into the market, and spread it as far as possible, to avoid the rent seeking behaviour of the old guard, Moving Picture Experts Group (MPEG) from Hollywood and similar groups. For every device that wants support for H265 the OEM has to pay a license of around 1 dollar currently.