Domain: jboss.org
Stories and comments across the archive that link to jboss.org.
Comments · 201
-
Re:Cred, where on cred is due... sigh>> could you tell me a good book to look at for building Java/Linux apps?
No, Java consists of so much stuff, it's simply not possible to cover all of them in a single book. What areas are you interested in? Web app? Distributed app?
Anyway, Below is a list of popular and free Java stuff you may want to have a look
- Build Tool - Ant (http://ant.apache.org/)
- Unit Test - JUnit (http://www.junit.org/)
- Application Framework - Spring (http://www.springframework.org/)
- Security Control - Acegi (http://acegisecurity.sourceforge.net/)
- UI Framework - JSF (MyFaces) (http://myfaces.apache.org/)
- J2EE/Web Server - JBoss/Tomcat (http://www.jboss.org/)
- OR Mapping - Hibernate (http://www.hibernate.org/
>> i've been playing with it for years (java coding in both windows and linux) and buying various books that look interesting and every time i play with it for a few hours i keep feeling like i'm fighting the system rather than actually getting work done.
The Java community is extremely strong. If you ask the question precisely, most of the time you will get the answer.
>> with .NET i've never actually bought a book and i can build large complex projects fairly intuitively (google for help from time to time).
If you can build the applications "fairly intuitively", I can't see how "large complex" these applications are. -
There is a suprise in Aspect-J
Having tried Aspect-J in a production environment, I found an unhappy surprise.
When you move beyond the trivial examples, you will encounter Aspect-J's long-standing bugs that simply crash your IDE every five minutes. For example, this P1 critical bug makes Aspect-J unbearable:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=4421 5
I've heard of JBoss AOP being used successfully in production (http://www.jboss.org/products/aop). -
JBoss is LGPL
Why we use LGPL. Ironic that Microsoft supports this.
I guess it's much easier to work with an existing company than reuse code from projects such as Geronimo, Apache's J2EE server. They could embed the code into their applications under the business-friendly terms of the Apache Software Foundation license. But then, Geronimo is adopted by IBM. -
Marc Fleury response
-
Re:Better than it sounds
-
At least he is being quotedas himself this time...
At least he is being quoted as himself this time, rather than yet another JBoss astroturfing...
(yeah, cheap shot, but not as cheap as the barrage of JBoss "enthusiast" posters back in the day...) -
Re:He just puts it more bluntly, than other skepti
Here is a link to a relevant page on the jboss site:
http://www.jboss.org/company/pos
So, he obviously seems to think you can make money writing "open source" software.
Lately, I am thinking that a more interesting question is one that should be on the minds of Free Software users...
What are some important factors that I should look at in assessing "the total development environment" of the software I am depending on?
all the best,
drew
http://yp.peercast.org/?find=bysa&Submit=Search -
Re:PHP vs JSPHandling input from an HTML form and storing it to a database doesn't really need OO, does it?
I guess the answer is "it depends".
;-)If I'm doing anything half-ways complex in web-to-db, yes I do want OO. I'll choose OO DB access in the form of Hibernate, JDBC, JBoss and EJBs and XDoclet. And I'll build my UI with an MVC-based JSP/Servlet framework, usually home-grown, but maybe using JavaServer Faces or Struts.
In my opinion, this kind of OO sophistication makes building even half-ways complex projects better.
Sam
-
Re:Marginal effect on Linux
-
Re:JOnAS
It would be interesting to see a neutral evaluation of the three open source app-servers: Geronimo, JOnAS and, of course, JBoss. Judging just by the number of users JBoss should be ahead, but which one is actually better?
... my vote still goes to JBoss but I haven't even tried the others. Should I? -
JBoss and Jetty
JBoss moved away from Jetty because Mort Bay is part of the Core Developers Network which forked from JBoss. Jboss now supports Tomcat.
-
Re:Why not use JBOSS?If you are wanting a free J2EE application server, why not use http://www.jboss.org/?
Indeed. I see the question as being "when you can't cope with your expanding J2EE app server needs yourself, who do you want to call in, IBM or JBoss ?"
Note that's jboss.com... IBM isn't the only for-profit company involved in open-source J2EE app server products here. Maybe that's what you're missing. Or maybe you're just missing the concept that someone might look to an outside company for help with their app server, rather than hiring more guys like you and I.
-
Why not use JBOSS?
If you are wanting a free J2EE application server, why not use http://www.jboss.org/?
What am I missing here?
Def -
Re:This points to one of the pieces of the puzzleThis is already beginning to happen. The money comes from sales of service and support, not from voluntary contributions.
I would like to give you a real world example:
In the company where I work we are selling a (closed source) mission critical J2EE application suited for thousands of simultaneous users.
This application run on the Open Source (LGPL license) J2EE server JBoss. The reason we selected JBoss instead on one of the many closed source competitors was quality, not price. The price of even the most expensive J2EE servers is peanuts compared to the price of our application.
But a company like where I work (where mission critical applications are deployed on top of Open Source software) needs the best possible technical service and support for the Open Source software it runs on top of. One day of downtime is estimated to cost up to about US$3 million for the average installation of our software.
For JBoss a group of core developers saw the need for technical service and support for companies like mine. They formed a company to give service, support and application development advice.
Of course the company I work for is a customer of JBoss Inc., and we are very happy with their services. In one case we reported a problem with JBoss server clusters. After some communication we got down to the root cause of the problem, and within a few hours they had a patch ready that solved a race that could lead to a distributed deadlock condition.
I don't think that JBoss Inc. directly contributes money to the JBoss project. But they contribute a lot of resources. They have most of the core JBoss developers on their payroll, and these developers are also working on the JBoss project. They host the bug database of JBoss, and recently they also starting hosting the CVS repository.
Disclaimer: I may be biased since I contributed code to JBoss years ago, but I have never been affiliated with JBoss Inc. (except that I work for a company that is a customer of them).
-
Re:Market share
Wrong market. WebSphere is an application server, not a web server. Yes, it has a web server included with it, but that's not its raison d'etre. You'd be better off comparing it to BEA's WebLogic Server or to the open source JBoss Application Server or the free Sun Java System Application Server.
In terms of market share, the last nubmers I saw had WebSphere first, with WebLogic close behind.
Eric
J2ME programming overviews and stuff -
Re:What about JBoss?
JBoss uses both JMS and JGroups, an excellent open source reliable multicasting library/protocol stack.
According to the project plan the goal is to have JMS for client-server structure communication, and use JGroups for peer to peer structure communication.
I highly recommend JGroups for your intermachine networking needs! :-) -
How does this compare to Hsqldb?
I have been playing around with Nukes, a Java CMS/Portal framework (kind of from the JBoss group).
One nice thing is that you can download a version of Nukes that includes JBoss, Nukes, and even an embeded DB - Hsqldb. You can also use it with MySQL and Postgres if you like.
So does anyone know how Hsqldb compares with Cloudscape?
Downloading Nukes with an embedded DB is really nice to be able to play around with the system right away without any configuration work and is a good example of why an embedded DB can be useful. -
Web or GUIFirst figure out if your app is going to be totally web delivered. If it is a web app, your managers points are moot. A J2EE web app is _not_ any slower then a ASP.Net web app. Second, why would you pay for an app server? What small office will have money for that? You can use Tomcat or JBoss both are excellent. If you went with an ASP.Net web app, your customers will now have to buy some MS Windows _server_. Well, you could run your ASP.Net app on Linux with Apache and Mono. Mono is great under Linux for ASP.Net apps in C# or VB.Net (uggh).
Heck, you could offer your customers a "turn-key" solution. Put together a cheap server running Linux with Tomcat for J2EE or Apache/Mono for
.Net. Sell that for a fair price. Your customers just have to plug it in and turn it on. Your customers will have no extra license fees from MS to worry about. If you have any half decent developers on your team, they could write _standards compliant_ HTML and then you don't need to worry if your clients are hitting your web app with IE, Firefox or Safari. If your customers have a net connection, you can plug it into this Linux server you sell them and charge a small annual maintenance fee for support. If there is a problem, just VNC or SSH in and fix it.If you go with a fat GUI client, then I personally would do it in Java with SWT (the toolkit used by Eclipse) for the GUI. SWT is very fast and lightweight. You can even get good SWT GUI designers to make coding easy. By going with Java for the GUI, you don't have to worry about what OS your customers use.
If you go with
.Net, then you should use Mono and GTK# or QT# for the GUI. That won't lock you into just MS Windows for your customers. You would be able to deploy to Mac, Linux and Windows. I know my doctor uses an iBook. She carries it into the exam room all the time and manages all her patient records from it. So if you went with an MS-only solution, you would lose customers like her.If you are developing an internal only solution, then use what you want. However, if you want to sell software (especially as a small company), you really should give your customers the most choice. If you went with a fat GUI client, you could sell a turn-key solution that ran Linux with Mono. Again, your customers will have no license fees to worry about, just your bill : )
I work as a senior programmer for a fortune 500. A few months back we went through a similar situation. However, we don't sell software, so everything we develop is for corporate use only. We had two camps. The J2EE camp and the
.Net camp. We even hired three outside consulting companies to help make the choice. All three companies said that our web apps should be done in J2EE. However, politics won out and now we have different groups doing different things. Some are doing J2EE and some are doing ASP.Net C# and I get to be involved with both.IMO, your senior manager should have no say in the technology used, just the features. The technology choice should be done by those who are going to _implement_ the technology.
"My senior manager recommended using
.NET. His argument is that most desktops he has seen in hospitals already run Windows, the development time will be cut down for this small to mid-size project, rich desktop clients are possible and there will be no application server costs involved. He also contends that .NET has more templates and abilities than J2EE (which is simply 'web targeted' in his opinion.That sounds like he has already be "won over" by some MS sales guy.
.Net development is not going to be any faster then J2EE. .Net might even be a little slower at the start because you have -
Not an answer... an opinion...
I cannot give you an answer for your particular situation, but I can tell you my opinion, based on my real-world experience.
I am the chief architect for a major application developed by the U.S. State Department, and used by foreign governments for the licensing of hazardous materials.
We use J2EE, and have been since 1999. JBoss is our application server. We used to use Weblogic, and were technically happy with it, but JBoss does everything we need, and has licenses and costs more favorable for our end users.
Our application is a bunch of domain objects and custom business logic, presented by the J2EE server as a bunch of sessions beans (some stateful, some stateless). We have a swing and a web-based client. Most of the rich interaction is done with the swing client, with mostly browsing and canned searching from the web-based client.
We do NOT use Entity beans - and I don't suggest anyone use this part of the EJB specification... For data persistence we use The Versant Object-Oriented Database. For data persistence, I'd recommend this, JDO, or Hibernate talking to the relational database of your choice.
We are very happy with the choices we have made. There is a TON of information out there about J2EE, we are happy with the performance we get, the skills are readily available, and there are plenty of vendors building tools in that space. J2EE is obviously a realistic choice for the kind of work you are doing - and has been for many years.
I do not know much about
.NET... only because that isn't where my career has taken me, not because of any dogmatic stance. My major concern about using it for this kind of work is that there is no 'application server'... .NET is tied to the windows platform. I know there are projects like Mono, but realistically, if you are using .NET, you are buying into Microsoft, their tools, and their solutions. With J2EE, I can upgrade my operating system and my application server independently - choose from different vendors for both, play them against each other for cost/support benefits, etc. With .NET, you just won't have these long-term options.I am the president of the Northern Virginia Java Users Group. While some may say this makes me biased, I'm not an employee of Sun or anything... I work for a relatively small company. I am involved in the NovaJUG because I happen to know and like Java, and like to teach. I also occasionally speak at conferences such as the No Fluff, Just Stuff Software Symposiums. I'm not going to leave my email address or anything, but there is enough info in this to track me down. IF you would like to discuss this further, drop me a line.
-
Re:Parent rewritten with some HTML code
J2EE is overengineered for everything, and darn too complex to learn.
It took me one week as part of a work placement in a summer holiday to learn all about EJBs. Either it can't be that hard, or I'm a genius. ;)
Oh, and I think it's a little contradictory to argue this line, then argue along the lines of just doing some no-brainer form-filling with the application server.
J2EE is about more than just shopping carts, and thus it WILL take longer to learn than a system that's suited to running an online shopping cart.
Java AS suck RAM big time (and CPU too). BEA advises customers to use open-source technology (Apache) to server static content, cuz' it would kill the server.
That's because application servers are not web servers. Sledgehammer and nut spring to mind.
PHP actually is running the internet far more than java has ever been
See above. Java is about running applications that just so happen to have a web front-end. PHP is about hosting websites that just so happen to have some application logic behind them.
J2EE only has it place in big enterprises that are willing to get it becuase the big bucks it costs come with some big name company that offers support.
"the big bucks it costs" - *COUGH*
even in enterprise contexts, the largest part of the majority of apps is pretty stupid form entry and validation
If that's the case, you don't need a big server cluster to manage it...
-
Tomcat is NOT a J2EE server
It is useful for not only those using Tomcat or those working with servlets/JSP/J2EE
...
As a J2EE programmer, I find the reviewer's statement to be a bit misleading.
Tomcat is not a J2EE server. The J2EE specification deals with Web Components (Servlets, JSPs) and EJBs (various EJB types and related services). Tomcat only satisfies part of the the full J2EE specification by serving Servlets and JSPs. Therefore, Tomcat is only a Web Container.
JBoss is an example of a J2EE compliant app server. -
Re:Still no operators...
> Its' not the case in Java where it sounds like there's only 1 way to do each thing
I take it from this comment that you haven't actually tried java. You can "explorate" to your hearts content, and there are many ways of doing the same thing (some obviously better than others)
> mostly because of the plethora of APIs (WebLogic, etc.) that corporations force you to use over it...
Now this comment just has me bamboozled... You mean that Weblogic holds sway over you and force you to code in one way over another? Surely weblogic is just an appserver? Which runs code designed to the standard J2EE API spec? The same as using Tomcat , JBoss or Geronimo or even Hibernate? (All of which are free and opensource, and follow the same J2EE spec that Weblogic does -- they just solve separate parts of it, and can be combined to do it all if you require)... I fail to see how this is a corporation forcing you to use one method of coding?
Sure, if you are only going to look at one way of achieving your goals, then there is only one way to go... -
Re:Linux Abologists AboundI'd hate to be the one to point to this out, but the article has nothing at all to do with Linux on the desktop/workstation. The article was describing the "failure" of Linux as an E-commerce and Web application server.
That being said, this article really describes the failure of Combe to properly implement the platform. In this particular instance there is no way to place the blame of this failure on Linux.
If you want to see some proof of just how successfull linux can be as an e-commerce platform have a look at JBoss and IBM.
-
Re:Their 'Software Partners?'
PeopleSoft , vmware, HP, Trustix , MySQL , SAFLINK , FTI , Constant Data , SurfControl , Software AG , Agnitum , Volante , JBoss , FalconStor , Intershop, Tarantella, Software AG and Bull ,
etc..., etc..., etc...
Google is your friend: 703,000 for novell software partner. (0.58 seconds) -
Use in Critical Production
I am the architect for Tracker, a project funded by the U.S. State Department and deployed in 9 countries.
This is a Java (J2EE) application using JBoss as our application server. We need to develop as well as deploy on Mac OS X, linux (Redhat 9), Solaris 8, and windows XP.
We use Cygwin on windows in both development and deployment environments, so that all of our scripts (administrative, start, stop, build, etc) are completely cross platform. Works like a champ. No complaints in production at all, although their installer interface seems a little wierd to me. It would be really useful if I could get some kind of report stting the exact configuration of a machine.
-
Re:Yawn.Another fast, small Java database is Hypersonic SQL.
hsqldb is a relational database engine written in Java, with a JDBC driver, supporting a rich subset of ANSI-92 SQL (BNF tree format). It offers a small (less than 160k), fast database engine which offers both in memory and disk based tables. Embedded and server modes are available. Additionally, it includes tools such as a minimal web server, in-memory query and management tools (can be run as applets) and a number of demonstration examples.
Another interesting, open source Java database is McKoi SQL Database, a GPL-licensed Java database with all kinds of nifty features.
Mckoi SQL Database is an SQL (Structured Query Language) Database management system written for the JavaTM platform. Mckoi SQL Database is optimized to run as a client/server database server for multiple clients, however it can also be embedded in an application as a stand-alone database. It is highly multi-threaded and features an extendable object-oriented engine.
Things are getting interesting for JBoss developers: JBoss ships with HSQL, supports McKoi nicely, and now we get Cloudscape thrown into the mix. Sweet. -
Re:ok, let's get it all out of trhe way at once
-
Re:ok, let's get it all out of trhe way at once
Get with the times, man! If she was using JBOSS, she would never have gone crazy and thought rowing across the atlantic was a good idea. Instead she could have optimized her use of open source middleware products and customized her architectures and applications for greater performance and efficiency! She would soon have been a multi-millionaire! Instead, now that she's here she has to row back. She definitely should have been using JBOSS. I'm not an employee of JBOSS, so you can trust me. JBOSS doesn't even have employees, I swear!
-
Re:ok, let's get it all out of trhe way at once
Get with the times, man! If she was using JBOSS, she would never have gone crazy and thought rowing across the atlantic was a good idea. Instead she could have optimized her use of open source middleware products and customized her architectures and applications for greater performance and efficiency! She would soon have been a multi-millionaire! Instead, now that she's here she has to row back. She definitely should have been using JBOSS. I'm not an employee of JBOSS, so you can trust me. JBOSS doesn't even have employees, I swear!
-
Re:ok, let's get it all out of trhe way at once
Get with the times, man! If she was using JBOSS, she would never have gone crazy and thought rowing across the atlantic was a good idea. Instead she could have optimized her use of open source middleware products and customized her architectures and applications for greater performance and efficiency! She would soon have been a multi-millionaire! Instead, now that she's here she has to row back. She definitely should have been using JBOSS. I'm not an employee of JBOSS, so you can trust me. JBOSS doesn't even have employees, I swear!
-
Re:ok, let's get it all out of trhe way at once
Get with the times, man! If she was using JBOSS, she would never have gone crazy and thought rowing across the atlantic was a good idea. Instead she could have optimized her use of open source middleware products and customized her architectures and applications for greater performance and efficiency! She would soon have been a multi-millionaire! Instead, now that she's here she has to row back. She definitely should have been using JBOSS. I'm not an employee of JBOSS, so you can trust me. JBOSS doesn't even have employees, I swear!
-
Re:ok, let's get it all out of trhe way at once
Get with the times, man! If she was using JBOSS, she would never have gone crazy and thought rowing across the atlantic was a good idea. Instead she could have optimized her use of open source middleware products and customized her architectures and applications for greater performance and efficiency! She would soon have been a multi-millionaire! Instead, now that she's here she has to row back. She definitely should have been using JBOSS. I'm not an employee of JBOSS, so you can trust me. JBOSS doesn't even have employees, I swear!
-
Re:ok, let's get it all out of trhe way at once
Get with the times, man! If she was using JBOSS, she would never have gone crazy and thought rowing across the atlantic was a good idea. Instead she could have optimized her use of open source middleware products and customized her architectures and applications for greater performance and efficiency! She would soon have been a multi-millionaire! Instead, now that she's here she has to row back. She definitely should have been using JBOSS. I'm not an employee of JBOSS, so you can trust me. JBOSS doesn't even have employees, I swear!
-
Re:ok, let's get it all out of trhe way at once
Get with the times, man! If she was using JBOSS, she would never have gone crazy and thought rowing across the atlantic was a good idea. Instead she could have optimized her use of open source middleware products and customized her architectures and applications for greater performance and efficiency! She would soon have been a multi-millionaire! Instead, now that she's here she has to row back. She definitely should have been using JBOSS. I'm not an employee of JBOSS, so you can trust me. JBOSS doesn't even have employees, I swear!
-
Re:ok, let's get it all out of trhe way at once
Get with the times, man! If she was using JBOSS, she would never have gone crazy and thought rowing across the atlantic was a good idea. Instead she could have optimized her use of open source middleware products and customized her architectures and applications for greater performance and efficiency! She would soon have been a multi-millionaire! Instead, now that she's here she has to row back. She definitely should have been using JBOSS. I'm not an employee of JBOSS, so you can trust me. JBOSS doesn't even have employees, I swear!
-
Re:ok, let's get it all out of trhe way at once
Get with the times, man! If she was using JBOSS, she would never have gone crazy and thought rowing across the atlantic was a good idea. Instead she could have optimized her use of open source middleware products and customized her architectures and applications for greater performance and efficiency! She would soon have been a multi-millionaire! Instead, now that she's here she has to row back. She definitely should have been using JBOSS. I'm not an employee of JBOSS, so you can trust me. JBOSS doesn't even have employees, I swear!
-
Re:Why just wikis?
You forgot the link: JBOSS.
-
Re:Why just wikis?
Why not normal discussion boards and blogs?
As an employee of JBOSS, I'm shocked and appalled at your suggestion. Fortunately, JBOSS is working on a new JBOSS solution to overcome this problem using JBOSS. We at JBOSS are passionate that our JBOSS technology will prevent even non- JBOSS users from taking advantage of boards this way.
-
Re:Why just wikis?
Why not normal discussion boards and blogs?
As an employee of JBOSS, I'm shocked and appalled at your suggestion. Fortunately, JBOSS is working on a new JBOSS solution to overcome this problem using JBOSS. We at JBOSS are passionate that our JBOSS technology will prevent even non- JBOSS users from taking advantage of boards this way.
-
Re:Why just wikis?
Why not normal discussion boards and blogs?
As an employee of JBOSS, I'm shocked and appalled at your suggestion. Fortunately, JBOSS is working on a new JBOSS solution to overcome this problem using JBOSS. We at JBOSS are passionate that our JBOSS technology will prevent even non- JBOSS users from taking advantage of boards this way.
-
Re:Why just wikis?
Why not normal discussion boards and blogs?
As an employee of JBOSS, I'm shocked and appalled at your suggestion. Fortunately, JBOSS is working on a new JBOSS solution to overcome this problem using JBOSS. We at JBOSS are passionate that our JBOSS technology will prevent even non- JBOSS users from taking advantage of boards this way.
-
Re:Why just wikis?
Why not normal discussion boards and blogs?
As an employee of JBOSS, I'm shocked and appalled at your suggestion. Fortunately, JBOSS is working on a new JBOSS solution to overcome this problem using JBOSS. We at JBOSS are passionate that our JBOSS technology will prevent even non- JBOSS users from taking advantage of boards this way.
-
Re:Why just wikis?
Why not normal discussion boards and blogs?
As an employee of JBOSS, I'm shocked and appalled at your suggestion. Fortunately, JBOSS is working on a new JBOSS solution to overcome this problem using JBOSS. We at JBOSS are passionate that our JBOSS technology will prevent even non- JBOSS users from taking advantage of boards this way.
-
Re:Why just wikis?
Why not normal discussion boards and blogs?
As an employee of JBOSS, I'm shocked and appalled at your suggestion. Fortunately, JBOSS is working on a new JBOSS solution to overcome this problem using JBOSS. We at JBOSS are passionate that our JBOSS technology will prevent even non- JBOSS users from taking advantage of boards this way.
-
Re:Why just wikis?
Why not normal discussion boards and blogs?
As an employee of JBOSS, I'm shocked and appalled at your suggestion. Fortunately, JBOSS is working on a new JBOSS solution to overcome this problem using JBOSS. We at JBOSS are passionate that our JBOSS technology will prevent even non- JBOSS users from taking advantage of boards this way.
-
Re:Why just wikis?
Why not normal discussion boards and blogs?
As an employee of JBOSS, I'm shocked and appalled at your suggestion. Fortunately, JBOSS is working on a new JBOSS solution to overcome this problem using JBOSS. We at JBOSS are passionate that our JBOSS technology will prevent even non- JBOSS users from taking advantage of boards this way.
-
Re:Why just wikis?
Why not normal discussion boards and blogs?
As an employee of JBOSS, I'm shocked and appalled at your suggestion. Fortunately, JBOSS is working on a new JBOSS solution to overcome this problem using JBOSS. We at JBOSS are passionate that our JBOSS technology will prevent even non- JBOSS users from taking advantage of boards this way.
-
Re:Why just wikis?
Why not normal discussion boards and blogs?
As an employee of JBOSS, I'm shocked and appalled at your suggestion. Fortunately, JBOSS is working on a new JBOSS solution to overcome this problem using JBOSS. We at JBOSS are passionate that our JBOSS technology will prevent even non- JBOSS users from taking advantage of boards this way.
-
Re:Why just wikis?
Why not normal discussion boards and blogs?
As an employee of JBOSS, I'm shocked and appalled at your suggestion. Fortunately, JBOSS is working on a new JBOSS solution to overcome this problem using JBOSS. We at JBOSS are passionate that our JBOSS technology will prevent even non- JBOSS users from taking advantage of boards this way.
-
Re:What?
slashdot has a cool new feature that can solve all of your problems in one simple step! Using a soon-to-be-patented technology called "Article Summaries", all of the information that would have helped you is easily available at your finger tips!
You may saying to yourself, "WOW! I would pay ten bucks for that!" Well, it turns out you can have this information for FREE! All you need to do is look directly below the headline of any story, and you will find this useful summary! Here is a free sample:
comforteagle writes "JBoss [link to the website for the company mentioned] head honcho Marc Fleury has laid down the law about Astroturfing in the aftermath of being accused of the practice without actually admitting it was done. 'Our visibility and success puts our customers and partners in a situation where you expect and demand that employees of JBoss Inc. hold themselves to that higher standard. Let's put the professional back in professional open source. "Astroturfing" is hereby banned at JBoss, starting with me.'" jg21 writes "After the Slashdotting of the whole issue, the wider community took up the theme. LinuxWorld's editor in chief took to task those who sought to "pollute the knowledge space," and then Richard Öberg and Cameron Purdy took up the theme with a call to raise the cyber-bar when it coms to integrity. Now JBoss's CEO has recanted: there will be no more fake posts from JBoss staffers, he says. Hmm, time will tell."
I can only hope this feature will avoid further confusion!