Difference between revisions of "HardwareComparisons"
From Sega Retro
(Created page with "This is a long-term idea - the raw numbers can be stored in a cargo table, so in theory most of these pages will look like this: <pre> '''Mega Drive vs. SNES''' and then des...") |
|||
| Line 27: | Line 27: | ||
-[[User:Black Squirrel|Black Squirrel]] ([[User talk:Black Squirrel|talk]]) 16:12, 19 December 2017 (CST) | -[[User:Black Squirrel|Black Squirrel]] ([[User talk:Black Squirrel|talk]]) 16:12, 19 December 2017 (CST) | ||
| + | : I'd probably just have a single "Mega Drive vs. comparable consoles". Storing specs as a cargo table is a good idea, but how would we deal with consoles that have multiple CPUs (which is most of them)? My first thought was to have a separate table with component specs, and then have the console table store "cpu1=680000" and "cpu2=z80". - [[User:Hivebrain|Hivebrain]] ([[User talk:Hivebrain|talk]]) 15:53, 20 December 2017 (CST) | ||
Revision as of 16:53, 20 December 2017
This is a long-term idea - the raw numbers can be stored in a cargo table, so in theory most of these pages will look like this:
'''Mega Drive vs. SNES''' and then descriptions about marketing and whatever
...
==Technical comparison==
===Graphics===
SNES looks pretty, Mega Drive not so much
{{compare|Mega Drive|SNES|graphics}}
===Audio===
SNES has that horrible string-like sound that every bloody game uses, Mega Drive not so much
{{compare|Mega Drive|SNES|audio}}
...
basically you'd only have to maintain one set of numbers per console, and a "compare" template would pull out those numbers on demand. How that's all done, I haven't decided, but it's totally possible.
This could be extended to pricing and numbers of units sold and territories sold in. Maybe go nuts and explain the compositions of plastics used in the shells and where microchips were sourced from - make it ridiculously definitive, because why not.
this might sit around for awhile though
-Black Squirrel (talk) 16:12, 19 December 2017 (CST)
- I'd probably just have a single "Mega Drive vs. comparable consoles". Storing specs as a cargo table is a good idea, but how would we deal with consoles that have multiple CPUs (which is most of them)? My first thought was to have a separate table with component specs, and then have the console table store "cpu1=680000" and "cpu2=z80". - Hivebrain (talk) 15:53, 20 December 2017 (CST)