Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Do svidaniya, Igor, and thank you for Nginx

nginx.com

Post reply on HN
Print view View original

161–170 of 366 posts

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

#161

Post by qbasic_forever »

khazhoux wrote: post #158
qbasic_forever wrote: post #33

Earlier quoted context omitted.

The web changed. We moved away from static HTML pages and CGI scripts to monolithic application servers in java, ruby, python, etc. Apache excelled with these static content sites and simple auth scenarios (remember .htaccess files?) but became painfully complex proxying application servers. Nginx was doing exactly what was needed at exactly the time it was needed.

And yet interestingly, nginx started in 2002, which was still old-school internet. So really, it was ahead of its time.

2002 was the start of the glory days of java web monoliths, like big monstrosities with spring, Rails, Django, etc. came a couple years later and monolith app servers really started to take off.

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

#162

Post by mmaunder »

“Igor has chosen to step back from NGINX and F5 in order to spend more time with his friends and family”

I wonder what this is really about.

Either way Nginx is the reason myself and many others were able to survive without raising venture capital because we didn’t need a massive horizontal cluster of Apache servers consuming 20 to 100Mb per concurrent connection. Personally I scaled above 100k current connections on a single front end nginx box with 6 Apache application servers on the back end in 2007 thanks to Igor’s incredible work. He really has made a massive contribution to the fundamental plumbing of the Web and should be recognized for it.

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

#163

Post by _8j50 »

_8j50 wrote: post #66

I still remember when it was new and so small a novice can review it without a headache. It was to me the answer to attacks like slowloris and C10K problem. And the config, by far much more pleasant than apache or IIS. I use it to reverse proxy all the time! Thank you Igor and best wishes.

[flagged]

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

#164

Post by xdennis »

smarx007 wrote: post #17
mobilio wrote: 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.

Many indo-european languages use something like "see you again" in their goodbyes. Specifically, notice the V and D from the Proto-Indo-European root "weyd-"[1] meaning "to see":

* arriVeDerci (Italian)

* auf WieDersehen (German)

* ¡hasta la Vista! (Spanish)

* do WiDzenia (Polish)

* do sViDaniya (Russian)

* la reVeDere (Romanian, (because I'm Romanian and it seems like an important language to mention))

[1]: https://en.wiktionary.org/wiki/Reconstruction:Proto-Indo-Eur...

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

#165

Post by [deleted] »

tentacleuno wrote: post #145
cft wrote: post #114

Earlier quoted context omitted.

Most requests in reality are GET. So if you first check for G, if (m[0] == 'G') { r->method = NGX_HTTP_GET; break; } else if (m[0] == 'P') { switch(m[1]) { ... } } else if ... this should be fast enough.

How would this work if the method field was something like "Gibberish"? Would this have any security vulnerabilities?

[deleted]

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

#168

Post by NateEag »

tiffanyh wrote: post #119
stormbrew wrote: post #16

Earlier quoted context omitted.

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.

It was believed that lighttpd leaked memory quite badly, and there was also a period of time where the development/updates on lighttpd dramatically slowed down. Both of which wasn't a concern in the early days of nginx. https://serverfault.com/questions/330413/lighttpds-memory-le...

My memory is hazy but I think I remember running into an actual memory leak in lighttpd circa 2008.

We were serving dynamic content via FastCGI, IIRC.

This was a long time ago and I'm pretty hazy on the details, but I'm pretty sure I remember finding memory leak bug discussions on the lighttpd website around that time, and no clear answers on how to avoid it.

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

#169

Post by torstenvl »

xdennis wrote: post #164
smarx007 wrote: post #17

Earlier quoted context omitted.

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.

Many indo-european languages use something like "see you again" in their goodbyes. Specifically, notice the V and D from the Proto-Indo-European root "weyd-"[1] meaning "to see": * arriVeDerci (Italian) * auf WieDersehen (German) * ¡hasta la Vista! (Spanish) * do WiDzenia (Polish) * do sViDaniya (Russian) * la reVeDere (Romanian, (because I'm Romanian and it seems like an important language to mention)) [1]: https://…

wieder means "again" and has nothing to do with sight.

sehen means "to see" and does not have your PIE root.

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

#170

Post by xdennis »

tick_tock_tick wrote: post #99
petre wrote: post #47

Earlier quoted context omitted.

They are breaking the web, plain and simple. Google with AMP, Cloudfare with their idiotic capchas.

What's the alternative? Abusive traffic is the norm rather then an exception. This gets into the same argument when people say they don't need a CDN; it's a relic from when bad actors were rare.

If all I'm doing is requesting an HTML page, why do they have to send me a CAPTCHA? I understand that my request is coming from an IP belonging to a VPN and maybe someone used the same IP nefariously, but I doubt they requested the same page I have.
Post reply on HN