- cross-posted to:
- opensource@lemmy.ml
- foss@beehaw.org
- cross-posted to:
- opensource@lemmy.ml
- foss@beehaw.org
Maxim Dounin announces the freenginx project.
As such, starting from today, I will no longer participate in nginx development as run by F5. Instead, I’m starting an alternative project, which is going to be run by developers, and not corporate entities:
You must log in or # to comment.
The name of this project is a death sentence. F5 owns the NGINX trademark. A successful fork of this will need to have a new name.
When Oracle ruined Hudson, the community forked it and renamed it to Jenkins, and Oracle lost their investment. The same should be possible with NGINX (BSD vs. MIT, IANAL).
IMO he would have been better off reversing the letters to something like XNGIN2 or some other clever play on the old theme.
Besides the new name being problematic it’s plain aweful.
Feels like Gentoo ==> Funtoo – Gentoo is a infinitely better name IMO.
He’s russian. Trademarks and copyright doesn’t matter.
That might be true inside Russia, but not in the rest of the world. F5 could sue in the US and force the registrar responsible for the .org TLD to hand the domain to them.
In his place, I would chosen something related but different enough to avoid trademark infringement, like “Freeginx”. IANAL, but I believe sometimes all it takes is one letter to keep lawyers away.
TLDR; F5 owns Nginx. Making corporate over security decisions. New community fork from one of the core devs at http://freenginx.org/. Too new to know if it will be adopted by other mainstream projects that currently leverage/embed nginx.
Note: If you use nginx and are concerned about security, consider a look at projects such as
owasp/modsecurity-crswhich include security layers on top of nginx.That doesn’t seem to be the case. From what I read on HN, the dev quit because he thought it didn’t make sense to submit CVEs for temporary/wip solutions, and F5 thought otherwise.
So as I see it, the developer quit because he didn’t agree that a CVE should be opened for a work-in-progress solution that was live on Nginx.
So basically just drama?
I sympathise with the dude dev but corporate loves corporate; I dont think the project is going to attract much funding if it’s purely a ‘libre’ fork.
I hope they will not switch to AGPL.
Is AGPL really bad?
No, it’s very good, corpo lovers however hate it because it cuts the hands of corpo trash and also lax licenses
It’s really good that I cannot statically link with something GPL or AGPL licensed without licensing my software GPL?
GNU is failing, in the rise of Chimera Linux.
corpo lovers however hate it
(After capitalism is socialism. When corpo can’t exist along with the society, we will help you in political and you will help us to get from poverty to capitalism, to achieve socialism as soon as possible?)
because it cuts the hands of corpo trash and also lax licenses
So *GPL aren’t considered free software, they are just open source, because they restrict modification and redistribution. Then you borned the term FOSS which is superfluous, to get the BSD license and GPL in the same house?
(GNU still illegally use the term “free software”)
Yes it is, that’s the point
Look at the corporate exploitation of free software and see that Stallman was right
Chimera Linux is the point.
But it is project’s philosophy, both BSD and GNU project will flame us if you teach them about licensing things
Disaster comes from our mouth
Lol some shitty distro used by almost nobody, and serves no interest other than corpo lover’s interests
At least I escape unreadable and unmodifiable GNU stuff
I saw your interest in Marxism-Leninism. Marx taught: Labor productivity is the premise for this society to win over the old society (poorly translated because I read translated textboot)
(Năng suất lao động là tiền đề để xã hội này chiến thắng xã hội cũ)
So the communists must learn to do business. Otherwise it is dogma, moralism (and soon become revisionism). Look at Viet Nam, we would have a pure capitalist government if we don’t switch to market economy (reactionalists backed by US would rebel and they are supported by 3/4 Vietnamese poor people). Now poverty has fallen into history.
Does nginx give me anything over apache httpd in the year of our lord 2024? I’ve used both for hosting servers but never really understood the difference, as apache seems to have incorporated the important improvements that nginx made iirc.
Using both, too.
Supposedly NGINX gives you better peak performance and the configuration file format is more popular.
I would guess that peak performance is only a concern when being google/netflix/amazon, otherwise I would bet the bottleneck is somewhere else.
Further, NGINX seems to have become the default reverse proxy for all start ups, companies etc. around 10 years ago and thanks to group thinking by now one has to explain when using something else than NGINX.
What I really miss from Apache is Apaches awesome letsencrypt module w/o the need for certbot. (If somebody knows about a module for NGINX which takes care of letsencrypt w/o certbot, please enlighten me.)
In summary: Technical Apache and NGINX are IMHO mostly interchangeable (outside of peek performance demands), but the market/herd/group think prefers NGINX.
Sorry, but you don’t get to claim groupthink while ignoring state of Apache when Nginx got released.
Apache was a mess of modules with confusing documentation, an arsenal of foot guns, and generally a PITA to deal with. Nginx was simpler, more performant, and didn’t have the extra complexity that Apache was failing to manage.
My personal first encounter was about hosting PHP applications in a multiuser environment, and god damn was nginx a better tool.
Apache caught up in a few years, but by then people were already solving different problems. Would nginx arrive merely a year later, it would get lost to history, but it arrived exactly when everyone was fed up with Apache just the right amount.
Nowadays, when people choose a web server, they choose one they are comfortable with. With both httpds being mature, that’s the strongest objective factor to influence the choice. It’s not groupthink, it’s a consequence of concrete events.
Does Apache have something like nginx’s OpenResty? That may be a significant benefit too.
Maybe mod_lua is an equivalent? I haven’t used OpenResty so there may be something I’m missing.
It looks to be similar. I’m not sure how trivial it is to add this. For nginx it’s basically built in. You just give it the Lua code. It’s also pretty capable. You can basically write a whole API back-end in it, which is pretty good for small APIs or functionalities, like an image resizing API.
It’s weird but I’m siding with the company on this one. With what little context we’ve been given the dev sounds like a stereotypical reddit moderator.
How so?
From what I understood the company who owns Nginx decided to give CVE ratings to experimental features, but those were for the stable branch. The dev disagreed because they were “experimental” but the company wanted to give them anyway because it was the stable branch used in production.
I don’t understand what was so bad about this direction that the company wanted to take that the dev threw a hissy fit about corpos bad, decided to leave, and start his own fork. It’s an insane overreaction IMO, maybe I’ve misunderstood something so IDK which is why my opinion is that the dev is a moron.
