152: Daddy Didn't Want the Good Graphics Card

Topics covered
Popular Clips
Questions from this episode
- Asked by 380 people
- Asked by 63 people
- Asked by 50 people
- Asked by 32 people
- Asked by 15 people
- Asked by 12 people
- Asked by 7 people
- Asked by 5 people
- Asked by 4 people
- Asked by 4 people
- Asked by 3 people
- Asked by 3 people
- Asked by 2 people
- Asked by 2 people
Episode Highlights
Rust vs. Swift
The debate between Rust and Swift highlights the unique strengths and limitations of each language. emphasizes Rust's lack of garbage collection, which allows it to handle tasks like graphics-intensive games and operating systems more efficiently than Swift 1. counters by questioning the characterization of Swift's reference counting as a form of garbage collection 1.
Rust is not garbage collected. Go uses garbage collector at runtime. Swift, of course, uses reference counting.
---
The discussion also touches on compiler options, with noting the potential for compiler modes to ignore certain directives, allowing for flexibility in testing environments 2.
Plex vs. Infuse
The comparison between Plex and Infuse reveals distinct approaches to media management and playback. voices frustration with Plex's metadata management, highlighting the difficulty in correcting misidentified media without extensive manual input 3. adds that Infuse may perform better with certain video formats due to hardware limitations in devices like Apple TV 4.
If you have a whole bunch of folders full of video files sitting somewhere on your network, this will go through the folders and play stuff for you.
---
Despite these challenges, both apps offer valuable features for media enthusiasts, with Infuse potentially offering smoother playback for demanding files 4.
Multi-User iOS
The implementation of multi-user capabilities in iOS devices presents both opportunities and challenges. and discuss the complexities of adapting iOS's Unix-based system to support multiple users, noting that initial designs did not anticipate such functionality 5. suggests that while progress has been made, the current implementation may still rely on shortcuts, such as erasing previous user data during switching 6.
Their multi-user switching could basically be erase everything about the previous user and go through a really fast first setup process.
---
The potential for multi-user support in educational settings is acknowledged, but broader application may require significant development 6.
Related Episodes


318: Not a Casino I Want to Play In
Answers 383 questions

36: A Weird One
Answers 383 questions

47: Better Pixels
Answers 383 questions

387: It Might Not Be as Cool as You Think
Answers 383 questions

236: Irresponsible Use of Infinite Terabytes
Answers 383 questions

46: A Compromised Machine
Answers 383 questions

407: It Isn't a Big Grapefruit
Answers 383 questions

333: Pesky Human Issues
Answers 383 questions

481: Accidentally Made It Too Good
Answers 383 questions

489: Very Inappropriate Thoughts About This Computer
Answers 383 questions

93: I'm Not Running a Boarding House Here
Answers 383 questions

331: The Technical Burden of Users
Answers 383 questions

358: Emotional-Support Mac Pro
Answers 383 questions

614: Don't Puke for the Show
Answers 383 questions

45: Give Up On The Retina Dream
Answers 383 questions













