If you hook up a scope to your outlet (don't be an idiot; to all the non-EE types, don't try this if you don't know how)
I'm pretty sure this is okay if you wet your fingers first and have a bucket of water nearby. Either that or it's putting out a candle—I can't recall...
P.S. I've read all of these posts and chapters in several books and I still don't understand this reactive power/power factor/phase/whatever sh*t...
Patents don't cover concepts. They only cover implementations.
You must be new here. (in the US)
At some point the Slashdot crowd is going to have to face up to the fact that content producers need to get paid if they are going to continue producing. Just like movies - it's easy to criticize the MPAA, but who is going to pay the millions of dollars to shoot a major movie if everyone simply copies content without paying for it?
There's a dramatic difference between these two cases: the MPAA has no good way to stop non-customers from consuming their material, and so they need to be rational, smart, and reasonable if they're going to survive (or possibly they can get the government to bludgeon their customers for them).
News media, on the other hand, can just cut their customers off--it's really no different than selling gasoline in this regard. That's not to say that the Internet hasn't changed the playing field, but newspapers are going to have to adapt, and since there will always be a market for news, the smart ones will survive.
Sure - five years to build a port. Then start on the next for when that port is drowned.
Well, yeah, if you're building serial ports. Try parallel ports for better throughput...
movie ticket. As a result, I don't go to the movies much any more--I don't like what they're doing with my money.
This is dead on. NASA and the DoD pay serious money to be able to run 15-year-old hardware and software--unless you're made of money, you don't want to be doing this.
Best suggestion is to use the most Open Source software and commodity hardware that you can. Your proprietary software vendor may not be around in 14 years, and even if they are, they may no longer offer the software you need to replace/fix/etc.
[Yes, this means you, Microsoft. I designed my enterprise accounting system to run on Bob and I've been hearing about it ever since...]
Government, get out of the way.
Yeah, let AIG run it!
As I tire of pointing out and people never tire of not understanding, lack of regulation does not mean free-for-all, might is right or whatever.
An unregulated nuclear industry does not mean plants can pour waste in other people's property. Since governments regulate commons they must either [A] take responsibility to ensure they are not destroyed or [B] privatize them to internalize the externalities.
Umm, actually A does mean regulation, contradicting your assumption, and B without regulation does mean a "might is right" free-for-all.
Are you sure you don't think the nuclear industry should have government oversight? Would you be willing to send your kids to a school next to a nuke plant owned by AIG and run by Enron?
This is just plain bad design, and not Congress' fault.
If this alarming system--with the same crappy design--had been "directly connected" to the controls, god knows what would have happened.
we're gonna have to think up a new word for what its competitors are doing.
IBM's still on the list, but only because they have generally embraced Linux. Sun has been going "la-la-la-la-la-la-la-la" and it's been getting less and less convincing as time passes.
SunOS was really the Linux of its day at the end, and Solaris was the first clear misstep towards Sun's eventual demise.
I saw a pair of these on some guy's pickup's trailer hitch and I immediately thought of him as more manly. I think that this might work for your netbook as well.
(Plus, first remove any Hello Kitty stickers...)
So in that respect it is exactly like Linux?
No, Microsoft will charge you US$269 to tell you that you're an idiot.
GCC's libstdc++6-4.3 std::vector size() is computed by subtracting the end-begin ptrs. There is no size field!
Okay, but this amount to the same thing, right? (That is, you still need an extra pointer that's effectively encoding the size of the vector, and that field must be updated on every size change.)
Vector should be no slower than array, if it is, you are probably using it wrong. The only exception is if you constantly create arrays on the stack, those would be faster on most platforms than vector because constantly allocating vectors cause heap allocations.
I think this was at least part of what I was doing. If you allocate a vector of small, dynamically determined size in a function, and run that function millions of times, the difference in relative cost between doing it with a alloc'ed C array and a malloc'ed vector could be quite noticeable. The former is essentially free, and I was thinking/hoping that the compiler-plus-STL would optimize this away for the vector case, too, but apparently it's not that smart.
I probably had other things going on as well.
You must be unlucky or the cause.
This would make a great slogan for Microsoft's new ad campaign:
I "washed out" of a PhD CS with an MSCS, and I think most of the parent poster's advice is good. Definitely the bit about not changing after 30 or so. Especially if you get married (or whatever) and have kids, your priorities and possibilities will change radically towards finding one good position and staying there.
I got my BSCS from a department that happened to be outstanding at the moment I went through, even though you've never heard of it. I then foolishly searched for a great CS department to do a CS PhD, (i) without first verifying that I really wanted a PhD and that it would be useful in the kind of work I really enjoyed, and (ii) failing to realize that it's not the department that counts at the graduate level, it's all about the one or two mentors you will have. My grad school has a good enough rep that everyone recognizes it, but the general departmental strategy was "throw everyone in the water and see who doesn't drown". I'm sure that worked for some, but I was completely lost for several years. In retrospect, I'd have been much better off identifying one good person to learn from and studying with them, even if it's at BFE Tech.
Based on that, I'd say that first you should think long and hard about what kinds of positions you'd like to have. If you can pinpoint people who are doing what you'd like to be doing, try asking them for advice.
Second, as the parent said, try to be doing something serious now, and try to identify specific people you'd like to apprentice under at a graduate level.
Good luck.
Your files are now being encrypted and thrown into the bit bucket. EOF
