You must login to post a comment. Don't have an account? Register to get one!
WYSIWYG annoys on me on forums these days. Personally I find its faster to use BBCode to format my posts instead of using the WYSIWYG approach. It tends to be more accurate too. Then again, I am used to HTML coding by hand (since WYSIWYG HTML editors tend throw in lots of crap tags) as I prefer my code to be clean. I have never used MediaWiki, then again, I have never posted or edited any Wiki articles although having got to used to both HTML and BBCode, I can probably pick up MediaWiki pretty easily. If I have an issue with BBCode (that is pretty rare) then plain text with some HTML tags works just fine.
WYSIWYG can be a problem for downlevel users, but there are some very good ones out there these days. For example, Telerik's Editor control (while certainly not free), is extremely powerful and very hard to break.
That being said, I am familiar with BBCode, MediaWiki, and HTML, so whatever happens I can live with. Wiki markup is probably the easiest to work with of the choices, once you learn it.
I favor BBCode myself as it's relatively close to HTML, which I know, without the security risks of plain HTML. I've never been able to understand wiki style coding and it's never been intuitive for me.
I find WYSIWYG editors to be too buggy or unpredictable most of the time.
Could support multiple types though, this commenting system seems to. Or is that too much overhead?
I despise WYSIWYG editors for the web. They are, without exception, slow, awkward, and difficult to use. For example, when in the middle of a list, there's generally no clear way to end the list and continue with a paragraph.
While I don't particularly like BBCode or Wiki markup, they are, at least, completely transparent. My personal preference is for plaintext with some HTML, with the backend software handling basic things like paragraphs and line breaks.
really security is about the same for all of them. Each method, other than raw html and to some extent wysiwyg, are whitelist based approaches.
WowAce.com & CurseForge.com Adminstrator
Check out my new addon, OneChoice, it helps you pick quest rewards faster.
Developer of Ace3, OneBag3, and many other addons and libraries
Project lead and Mac developer for the Curse Client
from a security perspective bbcode is way easier, its a whitelist based aproach where you specify how it should work and so you dont have to worry about implementing a sanitizer for html tags which can have malformed html due to the liberal html parsing policies of many modern web browsers (and so, so many vectors of attack)
I also am in general against using wysiwyg. I honestly expect a lot of problems, extension limitations, diffs would become fairly useless, etc.
Not to mention if the graceful failure path was to inputting raw html.