Live data from Hacker News

Nginx to Be Acquired by F5 Networks

nginx.com

301–310 of 408 posts

Re: Nginx to Be Acquired by F5 Networks

#301
post #263

Earlier quoted context omitted.

Their ad-targeting infrastructure likely has some secret subtleties to it.

Meh, not really. Cookies all the way down.

They can and do jump the incognito mode regarding ad cimplaints. I have proof.

Re: Nginx to Be Acquired by F5 Networks

#302

Earlier quoted context omitted.

Every company that has ever acquired anything says this exact same thing. Then the deal closes and it’s back to bottom line numbers.

In this case how does f5 make or lose money from Nginx?

I guess this[1] image from the F5 article gives an idea of where nginx fits from their perspective. F5 is a huge company (4000~ employees) that already likely has thousands of boxes running nginx. If you're going to continue using nginx as a critical piece of your business you might as well secure its future.

[1]: https://www.f5.com/content/dam/f5-com/page-assets-en/home-en...

Re: Nginx to Be Acquired by F5 Networks

#303
post #262

Earlier quoted context omitted.

Dataflow is based on oss Apache airflow. I don’t know how well it’s doing in the wild but every IT admin I’ve worked with are super excited to use it.

Airflow and Dataflow are not related. Google open sourced dataflow as Beam - https://beam.apache.org

Dataflow it's self isn't open source. Beam is not open source Dataflow, however you can use the Beam SDK with Dataflow as a runner.

Re: Nginx to Be Acquired by F5 Networks

#305

Earlier quoted context omitted.

oooh tell us more! or have a private conversation on your multicolored bike on the way to the cafe serving tri tip today!

Partial information is better than none.

aphorism rejoinder:

disinformation is worse than no information.

Re: Nginx to Be Acquired by F5 Networks

#307
post #49

I guess that signals it's time for nginx users to check out possible alternatives - just in case, if things turn out for the worse. I can recommend having a look at https://varnish-cache.org/ - while its performance might not be 100% up to par with nginx in some (very, very high-end) scenarios, it has many other fortes that nginx (at least in its FOSS release version; I've never used nginx plus) just cannot match in…

The replacement should be written in a memory-safe language. Including the TLS library. "There is more to life than increasing its speed."

Does it start with an "R" and rhyme with "repeated-so-often-its-been-ground-into-the-dust"?

Re: Nginx to Be Acquired by F5 Networks

#309
post #296

So...what is the future of enterprise open source? Is there a future for enterprise open source? If you start a company and open source your core/clients, your product becomes part of AWS, and AWS runs you into the ground. If you mix in proprietary licenses to protect yourself, AWS forks your core, adds in open-source licensed clients, then runs you into the ground (and you lose open-source contributors/supporters as…

is there such a thing as available source, closed license?

Yes. Source code is copyrighted and you can make it available under any licence you like, including a proprietary one.

Re: Nginx to Be Acquired by F5 Networks

#310
post #205
post #49

I guess that signals it's time for nginx users to check out possible alternatives - just in case, if things turn out for the worse. I can recommend having a look at https://varnish-cache.org/ - while its performance might not be 100% up to par with nginx in some (very, very high-end) scenarios, it has many other fortes that nginx (at least in its FOSS release version; I've never used nginx plus) just cannot match in…

Given how widely used nginx is, wouldn’t a community maintained fork be the most likely outcome of things changing for the worse?

The antithetic case here has precedence too (node/iojs amongst others) - "org realizes its share of the base tech has outlived its 'welcome' to no real financial benefit". But I guess a more pressing question is: can a corporate entity be "hands-off" enough so that its subsidiary has room to work as effectively as it had prior to its acquisition?

I don't have the wherewithal to get at these arguments from any angle (and I'm certain I'm missing many others).

Studious maintenance of the base code and branches/PRs besides build tried/true code bases and I hope that we're not being torn of that practice from this buyout; but only time will tell ...

Post reply on HN