[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]

[@the_void_is_nil](/creator/twitter/the_void_is_nil)
"@SwitchSpace1 @Avamander @Droogstoppel13 @LundukeJournal Predictable iface naming is in fact superior"  
[X Link](https://x.com/the_void_is_nil/status/1982098130687398153) [@the_void_is_nil](/creator/x/the_void_is_nil) 2025-10-25T14:53Z XXX followers, XX engagements


"@waspbr @LundukeJournal Trying something new just because "it's new" as the only justification is the exact same as "it wasn't broken so we fixed it". In software development this has a term: "a time-wasting bad idea""  
[X Link](https://x.com/the_void_is_nil/status/1981835724443005043) [@the_void_is_nil](/creator/x/the_void_is_nil) 2025-10-24T21:30Z XXX followers, XX engagements


"@SwitchSpace1 @Avamander @Droogstoppel13 @LundukeJournal They are actually. You should try actually reading docs sometime; it's very helpful. The legacy naming is literally "whichever one the kernel sees first gets eth0". I manage boxes with 4+ NICs some with multiple interfaces per-NIC. (con't)"  
[X Link](https://x.com/the_void_is_nil/status/1982097435070529654) [@the_void_is_nil](/creator/x/the_void_is_nil) 2025-10-25T14:50Z XXX followers, XX engagements


"@SwitchSpace1 @Avamander @Droogstoppel13 @LundukeJournal Let me know when you hit the thousands multi-region and have contractual liability. You learn that relying on the legacy naming is overhead and dangerous to SLA"  
[X Link](https://x.com/the_void_is_nil/status/1982207062361690539) [@the_void_is_nil](/creator/x/the_void_is_nil) 2025-10-25T22:06Z XXX followers, X engagements


"@eveforamerica I'm familiar with the brand name for an entirely different reason"  
[X Link](https://x.com/the_void_is_nil/status/1982225384885072231) [@the_void_is_nil](/creator/x/the_void_is_nil) 2025-10-25T23:18Z XXX followers, XXX engagements