I'm really happy for nginx to get the recognition that it deserves and I'd love nothing more than see the people behind it being able to make a living doing nothing but nginx.
But when I read about funding, about founding a real corporation and everything else that's going on, I'm afraid that at one point, nginx will do a MySQL and become open-core.
It's not that I'm not willing to pay for software in general, but I would love to have flexibility when I'm chosing my infrastructure. If the need for an additional server arises, I want to just start it and not matter about buying licenses and entering keys.
This is one of the main reasons, I prefer my infrastructure to be open source.
"But, open-core is also open source", you might say, but none of these projects ever end up getting a good community behind them. Many talented people would not sign a CLA and they would not want to invest their time into something that's "tainted" by a "better" enterprise edition.
Also, often times, submitted patches would not get accepted because the submitted feature is conflicting with an enterprise-feature - maybe even just one that's planned for somewhere in the future.
So in the end most of these open-core projects are exclusively developed by the same people who do the enterprise version and have a vested interest in selling enterprise licenses, degrading the "open" edition to nothing more than a trial version.
I would hate to see this happen to nginx. Not because there are no open alternatives (there are), but because nginx is elegant, fun to work with, fast and, above all, stable.
Let's hope that a pure support-based revenue model is going to work out for them.
(edit: nginx is released under a very liberal license, so it's entirely thinkable that, nginx would be OpenSSH'd: OpenSSH AFAIR started as a fork of the last Free version of ssh. And now just look where OpenSSH stands compared to non-free ssh)
I would hope most of us would want Igor Sysoev to at least put $10-$100m in the bank. He has easily created that much value over the past few years for hundreds if not thousands of companies.
If it turns out that nginx becomes less usable, or the free version becomes too expensive, a competitor will crop up. But we should want people who are gods of open source to figure out business models that enable them to become richly rewarded, and not just make a living. Maybe that's open-core, maybe it's a talent/showcase acquisition by Google or Facebook (as opposed to Oracle), but we should want these guys to become quite wealthy to inspire people.
nginx is one of the best pieces of software ever written.
Igor deserves a truckload of money, and it's good to see him going out on his own instead of being acqui-hired and never seeing the light of day again.
I feel the same way. Nginx has been the little ngin that could, supported by a bunch of talented hackers dedicated to bringing something to the table that the big-time servers, even the open source ones, couldn't. Nginx's history of being the lightweight, faster competitor to Apache (a shining example of success in the open source world) practically defines its identity.
I just hope that nginx doesn't sell out. I don't think it will, because I can't see what it has to gain for becoming exactly like its competitors when it already has a substantial user base. Of course, as you stated, dividing the userbase between enterprise edition users and free edition users could cause some software development political issues that could stifle progress.
Nginx is one of those rare products where I felt no need to upgrade from the now-ancient 0.7.6 version because it just does everything I need well. Truly an amazing little piece of code, on par (in my books) with venerable oldies like qmail.
It's worth keeping an eye on the current development version goes stable. 1.1.4[1] introduced preliminary HTTP/1.1 reverse proxying which means persistent connections to the backend and thus less overhead.
That is also true. You can use that version for as long as you want! The company I work for uses a newer stable version of nginx in production, but I think I actually make use of a directive that was introduced after the 0.7 series. Even so, as a small company with only a few customers, we're okay sticking a little closer to the edge. At this point, there's no compelling reason for us to upgrade past where we are (I think 0.98) unless I want bug fixes for things bugs we haven't seen.
I almost agree, i.e. second-level-legacy 0.7.x line is good enough for most of web needs, so indeed there is no really strong urge to upgrade to the current stable, though some nice features came later. What I do not agree is keeping really old 0.7.6 instead of upgrading to safer and more stable 0.7.6y (and if you do, going to the latest 0.7.69 is obviously the best solution).
Upgrading to at least the latest minor version (0.7.6y as you say) may indeed be a good idea since there have been some security vulnerabilities discovered e.g.
My computer club has used nginx since it first came out in 2004. We also had a bit of contact with Igor to get it running on Solaris. Since then it has been a very reliable piece of web infrastructure for us, and I wish Igor and the rest of the team the best of luck. I have high hopes that really great things will come out of this.
> (edit: nginx is released under a very liberal license, so it's entirely thinkable that, nginx would be OpenSSH'd: OpenSSH AFAIR started as a fork of the last Free version of ssh. And now just look where OpenSSH stands compared to non-free ssh)
Wasn't nginx imported into OpenBSD base not too long ago? I imagine worst case scenario they just keep maintaining their version (like they did with apache).
However, I am hopeful for Igor. I have used (and benefitted from) nginx quite a bit. I wish his endeavor the best!
If that happens it is pretty safe to predict that nginx will be forked immediately. Once it gets forked it can get community support without anyone worrying that they are supporting a paid version for free, and the enterprise people will have absolutely no control over features. Mysql got forked. And if you say that the mysql forks do not get sufficient community support (actually I do not know if that is the case) the reason is more likely the presence of a better sexier alternative (postgre) than anything to do with Oracle.
It is very hard to lock down free software if it is something popular or needed.
But when I read about funding, about founding a real corporation and everything else that's going on, I'm afraid that at one point, nginx will do a MySQL and become open-core.
It's not that I'm not willing to pay for software in general, but I would love to have flexibility when I'm chosing my infrastructure. If the need for an additional server arises, I want to just start it and not matter about buying licenses and entering keys.
This is one of the main reasons, I prefer my infrastructure to be open source.
"But, open-core is also open source", you might say, but none of these projects ever end up getting a good community behind them. Many talented people would not sign a CLA and they would not want to invest their time into something that's "tainted" by a "better" enterprise edition.
Also, often times, submitted patches would not get accepted because the submitted feature is conflicting with an enterprise-feature - maybe even just one that's planned for somewhere in the future.
So in the end most of these open-core projects are exclusively developed by the same people who do the enterprise version and have a vested interest in selling enterprise licenses, degrading the "open" edition to nothing more than a trial version.
I would hate to see this happen to nginx. Not because there are no open alternatives (there are), but because nginx is elegant, fun to work with, fast and, above all, stable.
Let's hope that a pure support-based revenue model is going to work out for them.
(edit: nginx is released under a very liberal license, so it's entirely thinkable that, nginx would be OpenSSH'd: OpenSSH AFAIR started as a fork of the last Free version of ssh. And now just look where OpenSSH stands compared to non-free ssh)