5

Good catch. I can see no compelling reason to keep them separate. If others agree, they can be merged.


5

clone has a very clear and different meaning. Think IBM PC clone as the prime example - a computer that is itself retro that mimicked (to varying degrees of compatibility) another computer of its time. Yes, you can "clone" a retro computer today with either retro or modern hardware (or even a simulation in software), but that is something entirely ...


4

The linked question is about measuring time on Atari 8-bit computers, using Atari BASIC. The question contains a number of screenshots of different dialects of BASIC, but they are just benchmarks from other computers used to illustrate the aim of the requested code. Think of it as "How would I write code equivalent to this in Atari BASIC?" — the example code ...


4

Yes, rename the tag to [software-cartridge] Some cartridges, such as Super Mario World and Star Fox, are not pure ROM cartridges but contain other hardware. In this case, rom-cartridge would be a misnomer. Likewise, firmware-cartridge would be a poor choice for cartridges containing only userland software.


3

I don't remember what I was thinking while I was writing that. Fortunately, I do remember that I was trying to populate a large number of tags, so the rest of the wording provides enough information for me to deduce my thought processes. For questions regarding MS-DOS, the Microsoft Disk Operating System. This tag wiki excerpt doesn't really give much ...


3

I'm not convinced. Not every OS loaded from disk was named as a DOS so a dos tag could exclude some systems. The operating-system tag covers all cases, as well as the good old tape-loaded OSs like those I cut my teeth on.


3

I am all for abolishing meta tags, but... it's not a meta tag. Manufacturer tags are currently being used for tagging questions about machines that are obscure enough to not have their own tags. The interfaces tag could be used in a similar way - for questions about obscure interfaces that do not have their own tag. That way, if and when individual ...


3

I very much agree with Wilson's answer (already upvote). Yes, the ussr is useful. Except the need for a warsaw-pact tag. That would be rather pointless and not adding any clear definition either. For example most would consider Yougoslav designs part of that group, except, the country wasn't part ot the treaty ... and so on. And more important in a technic ...


2

To my mind, ussr is useful, yes. The USSR is not like other countries when it comes to electronics and other technology (except perhaps the other countries in the Warsaw Pact -- maybe the tag should rather be warsaw-pact!) because of how imports were strictly regulated and industrial reverse-engineering was so important over there.


2

Hypothesis It appears that the tag was removed from all questions, yet still had an entry in the synonyms table. This put the website in an undefined state, because different parts of the website did different checks to determine whether a tag exists or not. Wild speculation This then fixed when Chenmunka did something, for reasons. I don't see why this ...


2

It would seem reasonable to have a separate tag for ProDOS. After all it was somewhat different from the original Apple ][ DOS and, from memory, it was more prevalent on the Apple /// than on the ][. I would keep to our convention of keeping the manufacturer in the tag, so apple-prodos would be preferable.


2

As ever, we should avoid meta-tags. A tag snapshot would be a meta-tag. It fails the tests of being specific and of being able to be the only tag on a question. The term has different meanings in different contexts and so would just be confusing. I'm not keen on your emulator-xxx suggestions either. What is wrong with the existing tags emulation and ...


2

Shouldn't we create a tag on "Electronika BK" Makes sense. Thus added as electronika-bk to cover all models (0010/11). This machine seems to pop up often on retrocomputing With just three questions so far the term 'often' is maybe a bit ahead of time. As of now, it doesn't make much sense to restrict it to the BK-0010 series or put in synonyms.


2

Rename the tag to [rom-cartridge] The tag should be renamed to rom-cartridge because many people think of the software (fimware, really) in them as "ROM" software, even when it's internally distributed in easily rewritable form, e.g., flash memory. (After some thought, this is my favourite of the options, followed by firmware-cartridge, but in the ...


2

Well spotted. The tag wiki is clearly wrong. All reference to batch languages should be removed.


1

The community that grew up around the project now called SBC v2 calls itself RetroBrew Computers. While it's a coinage, it does capture the idea of old technology, but in homebrew ways. Obviously Raspberry Pi or Arduino would be out of scope … I wouldn't be so sure. Arduinos and Raspberry Pis find a whole raft of uses as high-performance interface chips, ...


1

When I was growing up in the 90s, the books I read drew a distinction that a bug originated in software while a glitch originated in hardware. (eg. bad connections like you'd get from cartridge tilting, broken traces, failed capacitors, etc.) If we want the tag to be meaningful, I'd go in that direction.


1

To me, glitch seems just a gaming-specific synonym for a software bug, especially one that: keeps the game running (this is probably the most important property); violates the intended game mechanics; results from a low-level problem such as overflow, race condition or memory corruption, as opposed to a logic error (e.g. sequence-breaking a puzzle); may ...


1

'Glitch' isn't a real term, but a placeholder for various symptoms/assumptions/impressions. Using this as a tag would make any search rather useless. If a real symptom/impression/etc is found, than this may be useful as tag, but 'glitch' should not.


1

Yeah, go ahead. If we've got two questions about such a clearly-defined topic (i.e. any future questions on the topic would obviously use the tag), then we should definitely have a tag for it. One question? Maybe, maybe not; how likely is it that we'll have more questions on this topic? Is it a useful tag? But if you've already got two questions, and more ...


1

We should never create tags just for the sake of creating tags. Tags should always be created on need. If we get Dragon questions then we should have a tag for them, otherwise there is no point.


1

I haven’t noticed this discussion before. I have actually created dos, but I defined it to apply to DOS systems on x86 computers only. I believe this is justified as they share a common ABI and therefore maintain a certain degree of compatibility between each other, but since not all of them were actually derived from Microsoft code, they shouldn’t be lumped ...


1

Certainly Identify this questions are on topic, after more than one confirmation question already here on meta... Are identify this questions on topic? I am in two minds about identify-this without a suffix as being a bit broad. It would certainly need a wiki that mentions the existing identify-this-computer and identify-this-game tags. However, on the ...


Only top voted, non community-wiki answers of a minimum length are eligible