[Commentary] Top 10 Reasons why Servoy went Open Source
by David Workman
Data Mosaic
The recent announcement of Servoy Open Source (SOS) is generating a healthy amount of discussion, disagreements and planning amongst a number of us longtime Servoy developers. A couple of the Waves I'm on have grown so big they could be used to run browser javascript speed tests with.
The one thing that we all agree on (including Servoy it seems) is that Servoy at minimum rolled this initiative out well before it was ready. It's missing everything except for the "Here it is and this is how to get it running. Don't forget steps 17 and 18: pat your head and rub your stomach."
To help clear up the big bomb of confusion Servoy has generated with their "open source" "release", I thought it would be helpful to shed some light on why Servoy went open source. (If you need more help than this, we sell an open source therapy package that is guaranteed to make you feel warm and fuzzy about this whole mess for only $12,000 US.)
Ladies and gentlemen...drum roll please....The Top 10 Reasons why Servoy went Open Source:
10 Our biggest customer recently mandated open source tools. They said jump, we asked how high. Thankfully it wasn't that high.
9 No one buys out developer tool companies unless they are either open source or very, very sexy. The great personality thing just wasn't cutting it.
8 SaaS tastes yummy when sprinkled with open source.
7 After flogging the hell out of SaaS, PaaS, and the cloud -- our sales department needed a break. Open source sells itself.
6 The new owners of Sybase: "Servoy-who?"
5 We believe in open source, we've been involved in open source for years. And we especially believe in the open source that we don't pay for and the open source that you do pay for. Win-win for us-us.
4 We've decided that we really do love all three-and-a-half of you Servoy developers. Here's the open ticket system, faster bug fix releases, more thorough upcoming feature testing, transparency from us, etc. -- that you've been asking for for years. Now please go forth and multiply.
3 We've come to the realization that our pricing structure is incomprehensible. We don't remember if we did this intentionally or not but two additional pricing choices should clear things up. If not, here's the number for Servoy Sales....
2 Attract shower-avoiding parent's-basement-dwelling Java programmers. We know you're out there and we need you. (Memo: the iPad thingee is just a temporary fad with no camera.)
1 Build a vibrant Servoy developer community. We could have blown up the antiquated SAN program and given the recently anointed "developer liaison" a job description that involved liaison-ing with developers. But why exert ourselves when open source is community-in-a-can: just pop the lid.
Comments (10)