Please: Deeper articles Impartial authors (Spring x EJB3 was a classical partial approach!)
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.
The Java tecnology is becaming bigger and bigger, but there is so much frameworks, API's, etc. It is good, but would be better if there was a support for integrating all them, in the same local, like in ONJava.com site. It would be valuable for beginners and advanced developers!
What kind of "support" are you thinking of? Like articles on combining two frameworks for a specific purpose?
Articles about real world use of Java technologies would a great addition.
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?
make your newsletters prettier! plain text is unpleasant to read and look at imho. keep up the great work!
We haven't looked at the newsletter process for a while. Thanks for the input.
Eclipse and SWT all the way, Java all the way and last but not least, Linux and GNU packages are simply brilliant to be free of use.
Regarding Eclipse and SWT, have you been following the Eclipse Plugins Exposed series, and what do you think?
I would like more freedom to translate your articles into other languages
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.
More examples - we're all up to our ears in manuals - examples can communicate concepts faster.
True. Our typical article has code examples in the text and a source download you can build and run.
Pay more attention to user's groups, theay are great!
Interesting suggestion, thanks. Have you visited the java.net Java User Groups Community?
I'd like to NOT see articles comparing spring/hibernate to EJB 3.0 until the spec clears. In particular, until the spec clears, all bets for EJB 3.0 are still in the air. I'd like to see less about JSF because (in my limited experience), it looks, feels and smells like EJB 2.0 on the web - most people I know, work with, talk to, etc - just aren't using it. They're sticking with struts because it gets the job done.
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.
Architecture, architecture, architecture. How to use is great but there is a huge hole in architeture, testing, and optimization. :)
Thanks for the suggestion.
push for real world examples when introducing new technologies, don't be afraid to show when a framework doesn't do everything, or does have issues.
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.
Ultra-high quality articles needed.
We're trying, thanks.