@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 @aescling I think the 7a might have had a headphone jack. I know the a line did for longer than the other two.
@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.
@aescling @coriander there was a ryzen amd thing and some nvidia card
@wallhackio @coriander i know roughly how much you spent on that shit. how do you not even care to know this??
@aescling @coriander too much work
@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 @wallhackio @coriander I built my computer and could not tell you what CPU I have off the top of my head. I have a decent guess at the brand. Couldn't tell you the memory speed.
(I could tell you the GPU, since I upgraded that only a few years ago. But not the SSD model, despite that being even newer.)
I don't think everyone thinks too often about the specs for things that work fine for them.
@wallhackio @aescling okay in Caleb's defense here I also always forget my CPU and GPU
@wallhackio @aescling Tho I can at least tell you it's an i7 and an RTX 20-series
@coriander @aescling oh yeah i had an RTX
@coriander @wallhackio @aescling pipping in here to say I could not give less of a shit about the name of the hardware I use. I stopped knowing what the difference between phones was when they started having letters. I built my own pc but I have no idea what any part is or it's specs. I care about my hardware only so far as it does the shit I want it to do and I ignore it as much as possible otherwise. If they wanted me to care about these things they'd use names that aren't simultaneously extremely similar yet also gibberish.
@wallhackio @aescling okay but like
It's your phone
@aescling @wallhackio I had a 3a. Loved it. One of the best phones I've ever had
@coriander @aescling my 4a's screen starting peeling off, exposing electronics underneath, and the touchscreen never stopped functioning for 6 months. i only bought my 7 pro because the 4a's battery life became Fucked
@aescling @coriander maybe i did i dont remember