We're looking for your comments on how to best organize the wiki's content.
Wiki scope
Please summarize the below thread in the editing box. You may use any wikitext in your summary. When you finish, click "Save page".
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.There have been a lot of pages created about very general ideas in assembly language programming and embedded systems terminology, and yet that material is covered in far more detail and easily searchable on the internet at large. Do we really need those types of articles? It seems like a 0x10c wiki should focus on the game and how its features differ from the other things out there, rather than copying things explained better elsewhere.
In particular, it seems bizarre to think that this sort of wiki could serve as any sort of useful guide to the programming techniques involved-- and yet those pages are now proliferating. Why?
Those types of guides have good and bad points, but more bad, in my opinion. I like the idea of briefly explaining concepts, but these articles tend to be the opposite. People probably just want to add pages now for the fun of it and as there's no concrete information about the game, other than the CPU, that's all they're adding.
Giving basic examples in a guide with external links to in depth websites could be a possibility. It documents the game, but not the complexities of assembly (which I agree we shouldn't be doing). Articles like Recursion seem completely unnecessary to me, for the reasons you stated.
Although I see reason for lots of documentation on the DCPU-16, such as the hardware pages and info on it's instructions, I agree we don't need pages on general programming/hardware concepts. Something like Recursion shouldn't be on this wiki.
I think I could agree with that if this game was only for programmers. However, I see here a great opportunity to introduce masses of new people to the world of assembly programming. Many players may even be learning how to program for the first time. For the sake of these players, I think it's a good thing to have articles about basic programming concepts.
Granted, it may be best to put them in the guides and tutorials section, but I still think that we should have them. I wouldn't want someone to be intimidated by the prospect of having to 1) search and comb through results in an external search engine for every concept and 2) translate other languages into DCPU assembly. (Remember, we're talking about newbies here.) I think it would be a much gentler learning curve if we had such articles here, with examples in DCPU ASM, and embedded cross-references to other DCPU articles.
PS: In more general terms, I want to cultivate an environment where players guide and help each other out. The articles are just a small part of this vision I have.
Actually, you raise a very good point there. I hadn't really thought about that as much, but we are talking about a game, not CPU simulation software designed for programmers... :P It should definitely be organized into some kind of General Programming, General Assembly, or similar category though. Keeping other aspects of the game, the DCPU-16 specific pages (for example, info on it's interrupt system), and general programming separate is important to keep all the information easily accessible.
