That's a very good point and in fact one of the reasons for this entire thread.
QL people are becoming few and far between, so we've made an attempt to dredge out some old data from times when there was much more involvement in such projects.
Why specifically this discussion?
Actually if has a lot to with decisions about what to put onto the motherboard and what not - and where on the motherboard to put things that end up being put on it.
The 'problem' is that the motherboard sees everything, and in fact needs nearly any kind of hardware - on one hand, some sort of boot ROM, basic peripherals etc are all 8-bit, even today. Simpler to route buses, source one component instead of 2 or 4, and speed is generally not an issue. On the other hand, every design is a hole of sorts that the designer digs himself into - so let's do some thinking an at least provide a rope ladder to get out of the hole, if not an elevator, should the need arise. Some semblance of future-proofing can be considered, especially in the 'thinking about it' stage of design, and it's all the more logical if it can be had with minimal extra effort. Hence the wide bus mode ideas, which are based on the existing bus, simply because one does not need then to go through all those decisions again, and, one does not need to support them immediately or indeed in full.
However, since everything can't necessarily be designed 'in one go', or at least not supported from the get-go, some dose of compatibility with the old should be there, so that some semblance of a working system can be built, even though not optimal - at least at first. So, even the working prototype needs a J1 at least at first. One other thing to consider in this light is that certain old style peripherals apparently still have a market, but it's really not that good an idea to just clone more of the old versions, with 10 or 20 years of hindsight into problems and issues they have in use. These are under quick development (or rather re-development, which makes design much faster) and it makes sense for them to have some forward compatibility built-in (or at least forethought, given that there is a prospect for a new motherboard). These are likely to be used in the development of the new motherboard.
The basic idea is to think up something that will satisfy the above goals. Also, there are things that will definitely NOT go onto a formal expansion connector - instead they are connected to the local CPU bus. If that's through some connector or not, remains the business of the motherboard designer.
So, this discussion is actually based on a general idea of a motherboard, which has the basics: CPU, RAM, I/O (Note that something like video actually looks like RAM in this context, though there could be associated I/O). The idea behind this topic is to have a good discussion where to draw lines between various domains - local to the CPU or not, before the _peripheral_ expansion connector or after, etc. So far the discussion has actually been extremely helpful, at least I see it that way
