| Sign In/My Account | View Cart |
ONJava 2005 Reader Survey Results, Part 2
Pages: 1, 2, 3, 4, 5, 6
On the specific point, fairness was on my mind when I edited POJO Application Frameworks: Spring Vs. EJB 3.0 and I thought the author was fair in assessing the strengths and weaknesses of the two.
As for impartiality in writing, I don't think there's any such thing, and if there is, I wouldn't want to encourage it. All authors have an opinion, a bias, if only to say, "I think topic X is worth writing an article about." Authors should be free to make their case and have that case stand or fall on its merits. Trying to be "impartial," to set aside the author's value judgments, is a recipe for a boring article. The high number of talkbacks on this one--both agreeing and disagreeing with the article--shows that it captured readers' attention, and that's exactly what we want to do.
What kind of "support" are you thinking of? Like articles on combining two frameworks for a specific purpose?
Thanks. Let me ask this as a rhetorical question: if the real-world use is outside of your realm of interest, would you still read the article? This is one of the things we wrestle with in "case study" type articles--how much work will it take to explain the problem domain to the reader, and will it be interesting?
We haven't looked at the newsletter process for a while. Thanks for the input.
Regarding Eclipse and SWT, have you been following the Eclipse Plugins Exposed series, and what do you think?
Authors maintain the copyrights to their articles, and several have authorized translations to be reposted elsewhere, so you can contact the author directly about this.
True. Our typical article has code examples in the text and a source download you can build and run.
Interesting suggestion, thanks. Have you visited the java.net Java User Groups Community?
Thanks for the opinion. Part 1 of the survey results showed a lot of readers tracking JSF, so that may be a design smell to watch for.
Thanks for the suggestion.
That's an excellent point. Especially with emerging products and projects, it's only natural that there should be flaws that readers would want to know about.
We're trying, thanks.