Path: ...!feeds.phibee-telecom.net!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.arch
Subject: Re: Byte Addressability And Beyond
Date: Fri, 3 May 2024 22:32:22 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <v13olm$p9ih$9@dont-email.me>
References: <v0s17o$2okf4$2@dont-email.me>
	<2024May3.171330@mips.complang.tuwien.ac.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 04 May 2024 00:32:22 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="3e71a75fbbcf81b4a78150d90a6a33ff";
	logging-data="829009"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/y+BbfVfBp15JVOinv2+XM"
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
Cancel-Lock: sha1:gNdDXDKhLgop3uUI3+zLhvcrgFs=
Bytes: 1487

On Fri, 03 May 2024 15:13:30 GMT, Anton Ertl wrote:

> Lawrence D'Oliveiro <ldo@nz.invalid> writes:
>
>>But why stop there?
> 
> Others have provided good answers for that.  Here's another one: Given
> the requirements (based on the predecessors), there was not reason to go
> beyond byte addressing.  And looking at history, this seems to have been
> the right choice.

That applied back in history, when we had fewer addressing bits to play 
with, what about now?