Slashdot Mirror
Most Expensive JavaScript Ever?
ekran writes "A while ago Opera Software needed more servers. Not just a few servers either — they were planning Opera Mini's growth, implementing Opera Link, and My Opera was also growing quickly.
Most of the major hardware vendors grabbed their specs and came back with offers and sample servers shipped all the way to Oslo for testing. One of the biggest vendors, however, did not do their homework. They shipped the server, but when the Opera sysadmins started up the web-admin interface, they were met with a JavaScript statement that managed to piss off the whole company including the CTO. The script, apparently, locked out the Opera web-browser."
it's not HP as the link to what they actually buy shows they bought HP blades (http://www.digi.no/504306/her-kjores-egentlig-opera-mini&bid=6)
my money is going on Dell.
if (is.opera)
{
window.location.href="config/error.htm";
}
Conspiracy theorists unite!
Free Martian Whores!
48V DC is an odd beast, with odd standards going back to the early days of the Bell System.
In a 48V DC system, the positive side is grounded. This is to prevent corrosion on phone lines in the ground that happens more readily if the system is negative ground.
Since positive is ground, the "live" wire is negative, or -48VDC. Since this is the wire you don't want to lick, or allow to touch the chassis when powered, it is colored red in many deployments. The black wire is ground, you can lick* it all you want.
* -48V DC won't really sting you much if you just touch it unless your hands are wet or you touch it with a wet part of you like your tongue.
A bit of exploration gives one possibility. This page, on Dell DRACs , which have a web interface, shows that the web interface supports really only IE and firefox, and those only on 32 bit machines.
Ah yes, Dell Remote Access Controllers have a shitty as hell web interface that only seems to work in IE. I think it's supposed to work in firefox but it never has for me.
Photos.
(b)If deploying a system like this, IEC says the positive wire should be BLUE and the negative should be GREY. If the wires are completely isolated (i.e. neither is grounded or connected to PE) the positive wire should be BROWN. In the US (Opera isn't in the US) the wiring convention is WHITE for the return and BLACK for the negative wire. Just DON'T ever use red and black and reverse their normal functions. 48V can make very impressive arcs.
From scarped cliff or quarried stone she cries "A thousand types are gone, I care for nothing, no not one."
Generally you can free up the file handles. http://technet.microsoft.com/en-us/sysinternals/bb896655.aspx
Got a file stuck? Open a cmd prompt, run 'handle filename' to get a list of file handles for that file. then 'handle -c <HEXHANDLE> -p <PID>'. There ya go, file is forced closed and you can delete it.
Do you Gentoo!?
Some of their ethernet switches block non-IE browsers as well. I forget which is which, but I think the PowerConnect 6000s warn about the browser but let you through, and the 5000s just refuse to let you in when running firefox on linux.
My experience is from a few years ago and perhaps they have fixed their firmware since then, I know I filed a complaint.
Or just use Unlocker: http://ccollomb.free.fr/unlocker/ , it catches failed attempts to delete/move files and pops up a window showing you what's locking the file.
What time is it/will be over there? Check with my iPhone app!
Browser detection is almost always the wrong way to do things anyway. Test for existence of specific JavaScript properties/methods on objects to find out if they exist. You can generally check for IE-specific behavior just by testing for the presence or absence of JavaScript properties/methods.
if (document.getElementsByClassName) {
/* IE and old browser version */
elts = document.getElementsByClassName("resulttablerow");
} else {
}
By doing this, you won't have to do a browser check at all and your page will "just work" for any browser that implements either the standards-compliant behavior, the IE behavior, or both. You can do the same thing for CSS properties by trying to add the property, then going and trying to read it back for verification. If it isn't there when you go back and check for it, the browser doesn't support the CSS property.
I'm not familiar with Opera's behavior, but in my experience, roughly 99.5% of CSS and JavaScript that works with FireFox also works with Safari and vice versa (as long as you don't try to use bleeding edge HTML5 or CSS3 features). Any browser check that only tests for FireFox is almost always just guaranteed to make a bunch of users mad for no reason.
Check out my sci-fi/humor trilogy at PatriotsBooks.
Opera web site is actually a pretty impressive piece of code. It has all that nifty stuff like drop-down menus, and yet it also renders perfectly in Lynx (with menus as lists) - disable CSS and JavaScript in your browser, and you'll see. Meanwhile, it validates to XHTML 1.0 Strict.
It shouldn't be surprising, however, given that Opera guys are pretty keen on all Web-related standardization efforts - they've played a big role in initiating HTML5 effort (and are still very active in its development), before that they've participated in past W3C HTML/CSS standardization efforts, and they push for open standards (such as SVG) otherwise.