Redhat's head getting too big for it's own hat

Looks like Redhat is putting down it's foot and trying to impose trademark laws to stop people/companies from using it's licenced trademarks such as Hibernate, etc. in advertising their services.

Read Ted Neward's post on it for more details here

Most interesting is this quote:

Although you may offer object
oriented relational database mapping training, you may not use the Hibernate name to promote and advertise your products and services.

So I guess we need to remove any references to their products from our curriculum vitae.

Look like JBoss is having a bit of influence over at Redhat headquarters since the buyout.


I hope the entire open source and developer communities stand up and stop supporting any of Redhat's products. Stop recommending it your organizations, stop submitting patches for their software.

Comments on "How to use Java at a Startup"

Kurt Williams has done a very good writeup of things a startup company should considering when choosing development environments. You can read his blog here

I agree with most of what Kurt says but there is one thing that I would mention.

"Sure it's great for rapid Web development. But what about next year when you need to build a GUI?"

I find that a lot of overly complex solutions are designed/built on the basis of this argument. The counter-argument is that doing something in a quick time frame (ala RoR) and only concentrating on what you actually need now, provide immense benefits in time and cost. But more important is that it's hard to forecast your system's longterm needs so why invest time up front on features that may may never materialize? This may sound ignorant but I think that more often than not, we design/plan/develop to support things that we may need but never end up needing it. What's worse is when you've properly accounted for something but the business requirements have changed so much that you end up doing a major rewrite anyways.

For a startup, speed to market is of essence I imagine. Wouldn't it make sense to get your product out as quick as possible and when it takes off or you get that injection of VC, to then go back and revamp it properly?

I'm not a Ruby fan boy but I have been contemplating the choice of development environment for an upcoming project that Kurt's very post addresses.

Custom content for Sony's PlayStation Home?

Yesterday at the GDC, Sony announced their PS3 killer-app called "PlayStation Home".

You can see the demo here

Anyone have any developer details about this project? I have some ideas for content within the Home universe and would like to get details on how open this environment is to 3rd party content providers.

Can someone point me to an appropriate place to look/ask?