When will the 64-bit meme end?
32 bits are enough for casual use.
fucking casuals
>>54999238
>waah progress is being made
because its there. its like asking why people started using Unleaded gasoline.
>>55000028
Poor comparison, neither 32-bit nor 64-bit processors are harmful for your health.
>>55000066
>I drink my gasoline
>>55000101
>I don't breathe air
>>54999238
You said it yourself: "enough for casual use". I'm not a casual and want to tinker with every little thing I can to make my PC experience the best it can be.
31 bits is enough for mainframes
>>54999238
The Nintendo 64 is an overrated console with maybe 10 good games.
>>55000116
You don't breathe air???
>>54999238
Not with amount of RAM Chrome likes to gobble. It's almost as much as OPs need for cock.
>>54999238
Might as well format all your drives to FAT while you're at it.
just going to post this
>03:14:07 UTC on 19 January 2038
>>55002028
>tfw 32-bit OpenBSD is already safe
What a god-tier OS
but doesn't 64 bit give some speed benefits? I remember back in the day, with my old Athlon64 computer, I tried comparing oggenc on 32 bit Ubuntu with 64 bit ubuntu, on the 64bit version it encoded the same file almost twice as fast.
>>54999238
I'm not a filthy casual
>>55002001
that's actually still salvageable, just needs some contact cleaner ass-blasted on it and pins bent back in place.
(thermal paste doesn't conduct electricity)
>>55002001
I could fix that.
>>55002198
fuck off louis
>>55002181
Lots of thermal pastes do in fact conduct electricity.
Huge numbers, in fact. The whole "ceramic paste" thing is pretty new, you god damn child.
>>54999238
Linux is making a new architecture that is 32-bit but runs on 64-bit CPUs and uses the full 64-bit instruction set. The computers of the future will probably have most apps like this and only apps that needs >4GB of virtual memory will be 64 bit.
>>54999238
8-bit is enuff.
http://hackaday.com/2016/05/11/mike-szczys-ends-8-bit-vs-32-bit-holy-war/
(it is acctually a bretty nice talk)
>>55002273
heh
>>55002001
Whoever that is in the background, they have a really cute waist.
>>54999238
what is memory mapped I/O?
using 1-bit bus would also be enough, so long as your CPU is running at least 128Ghz. your motherboard would be small, but would be melt pretty soon. You'd also have to invent a new CPU architecture to interpret the temporally distributed instructions.
It's a trade off, how fast can CPU's go, vs how many wires can we fit on one motherboard.
>>55005655
>1-bit
Shouldn't it be an analogue computer?
>>55005655
HOW IS SATA FASTER WHEN THE CABLE IS SMALLER???
>>55005779
>Shouldn't it be an analogue computer?
Not necessarily.
You can do quite a bit with a serial architecture, so long as you don't need speed.
>>55005810
>>55005655
>serial architecture
Serial data transfer is not "hurr durr 1-bit" you fucking idiot.
PCI Express x1 is also serial with only one data lane, but it's not a 1-bit bus.
>>55005796
GAMEBOY POCKET SHOULD BE CHEAPER BECAUSE IT'S SMALLER >:(((((((((((((((
>>55005830
>Serial data transfer is not "hurr durr 1-bit" you fucking idiot.
I'm sorry, I don't quite follow you.
There are actual CPUs that were built with single-bit buses.
>>55005830
PCI Express x1 is serial and has more than one data pin, therefore all forms of serial communication require more than one data pin.
Here's a secret message in morse code for ya :^)
... .--. . .-. --. .-.. --- .-. -..
>64-bit meme
x86-64 and AArch64 legitimately improved on their 32 bit equivalents in many ways aside from just making the registers twice as wide and handling more RAM. With PowerPC or MIPS (such as the MIPS64 CPU used in the N64), you would have a point to say that 64 bit is more of a meme. With the majority of consumer devices though, which run ARM or x86, the 64-bit extension is objectively better even if the amount of available RAM was kept constant.
