Alias does not change the root dir, according to Nginx documentation. This was what made us believe that through eventual exploit, it could be possible to reach the active root dir through a completely different path as set per alias. In addition to that, having an erroneous document root communicated to CGI components such as PHP or mod_perl can lead to problems. We're still following Nginx development, in case things evolve.
We used something just like that to map users' home directories, but it doesn't solve the problem of not being able to set a unique root directory for each user case. Nginx accepts just one root dir setting, and it can't be conditionally set (or overwritten in a later if-else scenario) by putting it inside a location clause. One solution is to globally set /home as the definite root for all user location cases, but this does not sit alright with me - the document root should just not sit outside the target's home.
I wasn't aware that this was a Q&A or issues tracker for Nginx, which is why I never had the intent of bringing details up. My apologies for posting these things in the official Nginx resources. The sarcasm is on the house.
One problem that comes to mind is Nginx' inability to have multiple root dirs set for one and the same host depending on what location directive will be in use, for example when wanting to set unique root dirs during userdir mapping - which also happens to be something that Nginx can't do as properly as Apache. Another problem I can recall is how some configuration scenarios require an abundance of PCRE matching clauses to fulfill, which in turn causes Nginx a tangible but most noticable delay for each request that happens to match the implied regexp portion. I am not sure why this is the case, and I am not sure why it isn't so in Apache, where regexp clauses introduce no noticable stall.
Did I hit a nerve of some zealous Nginx user when mentioning the fact that Nginx isn't a silver bullet? :) I'm sure you can downvote this comment, too! Knock yourself out!
Looking forward to a day when I can give Nginx another try when its feature set has matured in more directions. Its unfortunate lack of fine-grained versatility in some areas of configuration forced us to stick with Apache's httpd after trying to replace an old Apache setup with Nginx - everything looked much better in terms of resource efficiency, until we hit the problem of simply not being able to translate a few specific configuration scenarios from Apache to Nginx, forcing us to deem Nginx as a definite no-go for our case.
The proper term for this effect is "raster bars", from how you traditionally did the effect by waiting for the raster line register to hit a certain vertical position on the screen, and then changing f.e. the background color of that scanline, then wait for the next line, change the color again etc. The name "copper bars" came out of the Amiga scene from how you could easily and without involving the CPU do this effect (and much more) on the Amiga using one of its co-processors, nicknamed the "Copper".
"We currently do not ship internationally", anyone? That message right there, when I'm shopping online, annoys me to no end. Clever way of doing business.
I used to be a Perian user, but its complications and shortcomings made me ditch it in favor of MPlayer OS X Extended, which eventually led me to the better MPlayerX. I am in favor of Perian's solution of being a nifty QT plugin, though.
I wonder how many percentiles of the Windows number comes from Windows' re-re-re-re-install-ish nature. "Dang, my FPS is low, I gotta "format Windows" again."
If you want something smaller, faster and tons more efficient for OS X, I highly recommend MPlayerX instead. It's everything VLC is, and more, with none of VLC's bloat.
That's no guarantee for anything. It's already out in the open that Huawei has close ties to the Chinese government and military. The point OP is trying to make is that Chinese telecom cannot be trusted as the Chinese government is actively indulging in systematic deployment of espionage frameworks on this level - by infiltration through business.
This method is not the least uncommon or "advanced" with those who still program assembler - in particular with the coders in the so called demoscene of lower level machines like the C-64 and Amiga - most often for creating unrolled loops to save a few cycles on removing the increase/compare/branch portion (or similar) of the loop.
This was pretty cool, but I couldn't help being struck by how utterly poorly it performs, especially as soon as you add just a handful of objects and two light sources. Sure, it's written in JS, but JS has come a long way in terms of performance, and so have our computers.
This demonstration instantly makes me think of Blizzard's Diablo II from 2000, which features an identical effect during gameplay, with a seemingly infinite number of shadow-generating obstacles and as many light sources casting shadows as there are players on the screen, and it runs perfectly smooth even on a 500mhz P3.
Why? The snippet of code is simple and functional enough to escape the need of being fiddled with ad infinitum ad absurdum. I can't see a cloud of maintenance need hovering over it.
I guess this is an ok way to save some tiny, tiny amount of bandwidth and server resources now and then when a user makes a mistake - but one should still not, under any circumstances, refrain from server-side verification.
The upgrade procedure takes but minutes in itself. The time you take to save and then write your old configuration files back to /etc and whatnot is on your hands :) Sure, upgrading OpenBSD's core system files isn't as smooth as doing it on f.e. FreeBSD via its package manager, but it's definitely not about hours.
"Material: Tough Recyclable Plastic" - Does anyone happen to know exactly WHAT plastic it uses? I'm also curious about the whole activation requirement for the printer. It made me raise an eyebrow.
Couldn't have said it any better. Just look at how your post was downvoted for simply pointing this sensitive fact out. The action speaks so loud and clear. In every social construct and gathering you always find that group of "socially immechanical" people who, with every means possible, try to assert some kind of status or rank over others. In the case of HN, it's done by downvoting posts of users holding a different opinion than your own.
I think that's good advice, and I would like to send it along also to the tiny-minded portion of users here on HN who campaign personal, pityful battles on others by systematically downvoting their posts for no apparent reason, as well as those who just can't seem to let things fly, but rather just have to hammer down on users with opinions they simply don't agree with.
I think the karma system as it stands now is problematic because of how it simply enables the generally grumpy crowd of HN to fuel their own overgrown negativity.
APM trivia: there was a brief moment in-between two patches in Heroes of Newerth - a popular DoTA clone - in where moving your "hero" to a new location on the map counted as an action. Players simply stepping around rapidly right where they were standing would increase their APM indefinitely.