Posted by Sacha in IT, JBoss.
From RHT’s Q3 report:
Total revenue for the quarter was $194.3 million, an increase of 18% from the year ago quarter. Subscription revenue for the quarter was $164.4 million, up 21% year-over-year.
Non-GAAP adjusted net income for the quarter was $33.5 million, or $0.17 per diluted share…
For reference, analysts estimates projected revenues of $188 million and earnings of $0.16 per share – without taking in account the recently settled 5 years old lawsuit.
Great work, onward,
Posted by Sacha in English, IT, JBoss.
It is with GREAT pleasure that I’ve learned that the JCP EC had approved the final ballot for Weld and EE6!
This really finishes the work started with EE5 and clearly positions EE6 as the most powerful and yet the easiest to use Java runtime environment, clearly ahead of Spring and its XML logorrhea. Furthermore, the definition of a powerful Web profile without the hassle of some of the most legacy EE specs (IIOP anybody?) will give fresh air to the too many IT teams building (and attempting to maintain) their own Tomcat on steroids.
Yet, a spec with no implementation is hardly usable (for my own sanity, please don’t mention the EE5/JBoss5 drama), and so I’m very impressed that JBoss already released JBoss 6.0M1 which contains some of the most important EE6 bits. Jason’s blog entry here, Dimitris’ here. Congratulations guys, the move away from 5.2 was a smart decision.
Yet, when closely looking at the Weld and EE6 votes, only one company didn’t vote for both JSRs: SpringSource/VMware. They didn’t politely cast an “Abstain” and explain the reason why in the comments, no, they simply didn’t cast a vote at all. How to interpret that non-move? Well, maybe they “forgot” – this happened to me at JBoss for a couple of “less critical” votes – and so I went to look at SpringSource’s official news and PR page, SpringSource’s official blog and even Spring “.org” page: nada, nothing, no official position (and Rod Johnson hasn’t blogged in more than 3 months – so no help from there either).
I don’t think this silence is clever as this will make people speculate that either i) SpringSource is still debating internally what their official stance should be or, worse, ii) that they will retain from giving an official stance for as long as possible to keep all options open and possibly change their opinion down the road as they see fit. Or maybe SpringSource didn’t cast a vote because VMWare refused to sign JCP’s JSPA agreement for some reasons related to their IP. Who knows?!? (disclaimer: I don’t)
In order to keep the worse rumors at bay, I think that SpringSource should clearly state ASAP i) why they didn’t vote and ii) what their official stance on EE6/Weld/etc. is. and iii) whether VMWare/SpringSource is still part of the JCP.