Live data from Hacker News

Do svidaniya, Igor, and thank you for Nginx

nginx.com

11–20 of 366 posts

Re: Do svidaniya, Igor, and thank you for Nginx

#11
Impressive. I thought the only way you were allowed to quit working on an open source project was to commit a new version where you delete everything and introduce a chunk of code to put clients into an infinite loop. I'm impressed Igor was able to find an alternative. /s

(More seriously though, his work is impressive and I hope his next adventure is at least as fulfilling).

Re: Do svidaniya, Igor, and thank you for Nginx

#12
post #4

Here are relevant Russian discussions on OpenNET[0] & LOR[1]. N.B. From Nginx company history on Wikipedia: > On 12 December 2019, it was reported that the Moscow offices of Nginx Inc. had been raided by police, and that Sysoev and Konovalov had been detained. The raid was conducted under a search warrant connected to a copyright claim over Nginx by Rambler—which asserts that it owns all rights to the code because it…

[deleted]

Re: Do svidaniya, Igor, and thank you for Nginx

#15

People need to stop with this Cloudflare captcha madness. I literally accessed nginx.com a few hours ago and now it hit me with a captcha again.

Cloudflare uses a heuristic trust model where it pulls multiple trust signals from the client. It can use several things (including stable IP address, cookies, and I think even a bit of JavaScript grabbing a nonce from local storage).

If you run with a lot of "identity fuzzers" (browsing through Tor, JavaScript off, cookies banned), Cloudflare can't build its trust heuristics and needs to challenge-response more often. I suspect there's overlap between HN readers and use of those sorts of tools, so I think there is a disproportionate number of people around here who run into this issue (whereas most "regular" folk almost never see a Cloudflare challenge / response).

Re: Do svidaniya, Igor, and thank you for Nginx

#16
post #7

I really take for granted how well Nginx works across a number of web backend functions. Some of the container/orchestration world has tried to supplant the need for it as a reverse proxy, but you get so many goodies out of the box just by sticking this in front of your app, and for very little overhead. I remember the pre-Nginx days and all of the struggles people routinely ran into with options like Apache or other…

I mean there was lighttpd before nginx and they have/had pretty similar structures, weights, etc.

I feel like I knew at one point why it got so thoroughly supplanted by nginx but I don't remember now why that happened.

Re: Do svidaniya, Igor, and thank you for Nginx

#17
post #3

To non-russian speaking users: "Do Svidaniya" means "Goodbye".

To add a bit more, "svidaniye" means a date, and "Do svidaniya" literally means "till [our next] date". In English, "see you" or "see you later" translates closest to the original phrase in Russian.

Re: Do svidaniya, Igor, and thank you for Nginx

#19
post #3

To non-russian speaking users: "Do Svidaniya" means "Goodbye".

To add a bit more, "svidaniye" means a date, and "Do svidaniya" literally means "till [our next] date". In English, "see you" or "see you later" translates closest to the original phrase in Russian.

"Do svidaniya" sounds more formal than "See you" though.

Re: Do svidaniya, Igor, and thank you for Nginx

#20
post #9

It still surprises me that NGINX beat out Apache so quickly even though Apache had way more modules and was/is entirely free vs. NGINX which is more or less "open core" with some nice features requiring commercial licensing.

On the other hand, the unreadable weird-ass pseudo-XML configuration files of Apache made anyone touching them wish for something better. I also expect ngx_lua did a lot for adoption, the fact that you could always "shell out" to lua if you needed was a huge boon even just for peace of mind.

> On the other hand, the unreadable weird-ass pseudo-XML configuration files

If I have one gripe about NGINX it's that its configuration is a still-half-baked DSL that has quirks you wouldn't expect and when they error you don't get great feedback.

Examples: You can have an if clause, but no else attached. You can't have an if clause with multiple conditions. Finally, "if [might be] evil." 1

You end up writing a bunch of partitioned control flow statements and you're never really sure at what level of config hierarchy they would best be applied.

I love the product but Apache's XML versus NGINX's semi-declarative, hierarchical blocks aren't night and day better.

1 https://www.nginx.com/resources/wiki/start/topics/depth/ifis...

Post reply on HN