Kazinsal wrote:
Wikis are not places to dump embeds.
The OSDev wiki is a website for reference. Not a sandbox. It is fine as it is.
That's the problem.
The goal is to show discussions that always reflect the right answers and the right code.
Wikis, forums, Question and Answer (Q&A) sites, blogs and the rest of common websites are dynamic templates with static user-generated content that will get fully static once it stops being a trending topic.
They are more to document snapshots of static things that will never change. They can get more details for information but they are still the same fact.
But to allow for more effective discussions oriented to develop projects and promote good discussions with interesting stuff to do, it would be better to know about a platform that works based on live resources/code, and virtually not using inline code which wouldn't be of interest to show the actual routines of the program as they would get outdated immediately.
But for code, while it may have a development history, it should also be better archived as a particular version and keep discussion updated for the latest version besides the archived snapshots with discussion of each final version. For code in development we also need a mix between live repositories and a platform to keep, review and update comments and discussions coherently no matter how much the embedded live code changes.
In other words, it doesn't consolidate additions to any projects or references that discuss real world code until solving it and leaving a reference that will keep updating over time.
It looks like referencing code from different repositories (Git, SVN, private web sites) in an embed as plain text with and without syntax highlighting and discussing it as it gets developed would be an absolute minimum.
It would effectively align updated comments and discussion with real updated code to be compiled.Without being able to embed live resources we are only left with resources without connection to anything real. They are just like random examples but would never be able to develop real code in a single effective pass.
So what to do?
SVN and Git on the other hand lack discussion.
JSPerf or websites to test any sort of code aren't really what I'm talking about.
I'm referring to embed systematically