A few points go for it:
- Exposure: By having a journal on GDNet you inheritly get more exposure than if it was, for instance, on your own website, etc.
- Audience: Those who visit GDNet tend to have a bit higher of a technical background than on most of the other popular blogging spots, as such the audience is more likely to understand your message.
- Unification of Interests: It is in your interest to unify both your source of information (i.e. the articles and forums), and your method of communicating back your results. This can be done in many ways, but a developers journal is a great way to keep track of progress along with updating others, while remaining on topic (and not poluting other areas with OT but pertinant information).
The major annoyances:
- Control: This is my biggest beef with it. I have no real control over the formatting of my posts, often times I have to edit a post several times before publishing it, just because I don't have the control to exactly specify how it should look.
- HTML: You have no ability to use HTML in your journals. "But Washu, I can see you using it right now!" Yes, I'm using what VERY limited abilities you do have. You can't use tables, you can't use divs, you can't use spans. You can use bold tags, teletype tags, italics, lists, and a few other minor tags, along with the GDNet ones. For most people this would be enough, but we are technical people, as such our requirements are often far from the norm.
- Code Highlighting: Ugh. You know, I typically like my code highlighted in a specific way. For instance, I like my numeric literals and string literals colored differently. I like my keywords in blue, my preprocessor directives in italic, and many other little things like that. Without the ability to use HTML, I have to rely on the GDNet code formatter, which...from my crude observations of it, appears to just be a regex that misses keywords, and sometimes highlights things that shouldn't be. Not only that, but why the hell is my C# code highlighted like that abomination Java (no offense intended to you poor bastids who have to use Java, but this is my journal.)!
Now, as you can see, my primary beef with the journal system is functionality wise. But when that is the primary means that you use to control how your information will be presented, and hence conceptualized, to your audience it becomes a major annoyance.