@coriander I caved and bought a phone without a headphone jack two years ago. at the time it was tough to find quality phones that still had them because god has forsaken us. maybe its different now, i dont know.
@coriander i really miss my headphone jack but the google pixel 7a has served me very very well otherwise. wasnt cheap though, and im sure they're at some ungodly expensive new version at this point
@wallhackio @coriander i am pretty sure you bought a 7 pro??
@aescling @coriander oh it was a 7 pro. i have reported myself for lying.
@wallhackio @coriander the a line is by design not supposed to be that expensive
@aescling @coriander extremely Unaware behavior not to know the name of the phone i currently own and use for hours a day
@wallhackio @coriander i genuinely do not understand not caring enough about what hardware you’re using to just not know these things
@aescling @coriander i like code i dont care about hardware
@aescling @coriander the hardware is just a vessel for the parts i like
@wallhackio @coriander you built your own pc
@wallhackio @coriander what’s your cpu and graphics card
@aescling @coriander i dont remember
@wallhackio @coriander what is wrong with you.
@wallhackio @coriander i know roughly how much you spent on that shit. how do you not even care to know this??
@wallhackio @coriander hardware conditions the way software is written and rewritten. you should not be ignoring this shit as a developer by trade
@aescling @coriander you are correct but i dont care
@aescling @wallhackio @coriander I mean. Technically? But unless the goal is literally "works on my machine", that's kind of not the point. Knowing how it works in general is going to be way more useful for most developers than knowing how much L2 and L3 cache you have, or the cross-core read delay matrix. (There are developers who need to know those things! Even most of them are broadly not programming for their own desktops though.)
@aschmitz @wallhackio @coriander this is fair; i agree
@aescling @coriander too much work