People still make 32bit software

You might be enjoying anal sex

write critical parts in 32bit x86 ASM

People still use Python 2

what? it points to a memory location
of course OS can manage that but really...

This
x32 ABI should be standard in most programs

Yep, it's great. Runs on anything.

yes
to this day /v/-tier stuff is ported to 32- and 64-bit archs at once

>thinks coffee-makers should have 16GB RAM
OP you are genuinely retarded
please leave Jow Forums and never come back

packing structures full of pointers is going to trash data cache on x64 dipshit. it depends on what you're doing. go back to electron tutorials and stop posting here

>thinks op is talking about coffeemakers
Imagine being this brain dead

when the fuck do you even do this

whenever you use linked data structures or write classes with pointers to multiple objects?

>moving the goalpost
kys. op said software, he didnt specify that it had to be for desktop computers or anything so fuck off

somehow I have the verb "packing" connected with serialization

people make more 8-bit software than ever, thank arduino fucks for that

>people still use operating systems
NIGboards.4channel.org/g/GERS HAHAHAA
FUCKIN BRAIN WAVE POSTERS IN THE HOUSE TONIGHT!

>worries about trashing the cache
>using heap allocation
lmao

>he didnt specify
So why did you pretend he specified that?

You pulled that goalpost out of your ass. Who named coffeemakers? You did

t. webdev

you can be cache-efficient on heap memory, are you serious? do you think all inner loops in game engines and OS kernels operate on stack memory or BSS?

i suppose i wasn't clear
>using random heap allocation you need to store pointers to
L M A O

>people still make single-threaded software

Attached: 1383251754401.gif (192x333, 2.53M)

l-lewd

again, you can have a nice linear array of structures or class instances that have pointers to other data, for example hot/cold split where you keep hot, frequently used data directly in the linearly allocated structures and cold, infrequently accessed in separate memory pointer from the main structure. on x86 you pay 4 bytes less per instance.

x64 is a valid choice if you're primary concern is security or you need to work on large data sets and you are on OS that doesn't have PAE

that sounds reasonable, I'm not arguing against x64

Mostly bloatware programmers need 64 bits. Problem is, there are so many of them. Apple 2 with an 8-bit processor was enough for the first spreadsheet, back in the day of real programmers.

even in these days of 53-bit physical address extension, if you're even moderately competent, 4GB is still a substantial address space (and you get it all if your kernel is 64-bit native, because it relocates system libraries out of reach, with it handling the protected-to-long mode transition)
t. 8gb of core should have been enough for a while

Tom Jennings got the backbone of FidoNet into a .COM file.

u mad bruh?

Attached: neofetch-2018-12-08-04-10-12-3108.png (1024x768, 229K)

based and redpilled

i do this with a patched windows 10 on a recent laptop
>underpowered mobile-tier cpu
>long mode code runs like ass on it as a result
>patch out licence check for big-core PAE support
>all 8GB now available