Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment Re:We vote on leaders not lightbulbs (Score 1) 1146

LEDs are hard in most places, but it is getting better.

I'm a fan of CREE can lights. High CRI, a good coating, and built-in trim makes them look better than the previous lights. I haven't had them very long, but so far they are handling brownouts better than anything with a ballast. The remaining CFLs tend to discolor (toward pink???) and dim significantly if they are not fed exactly the right voltage. The biggest downside is that the LEDs cost about 10s the cheapo "pink" CFLs, which adds up quickly. It will take years to see any cost savings even with 100% survival rate of the LEDs.

Comment Re:Why not quantum entanglement? (Score 1) 236

sampling at 50 times a second

Using quantum entanglement to achieve zero transmission delay, and then only looking at it once every 20 milliseconds? You may as well just use fiber, as half of the time you will still receive information ahead of a polling-based QE system. Now, the benefit for the QE system increases as the fiber distance increases, so your idea still makes sense for mutli-planetary HFT. Just... not between Chicago and New York.

Comment Re:Yes. (Score 1) 1216

Now profits jump as production triples and the bonuses take his pay to 20 times that of the janitors.

The hot shot CEO will know to take enough to put him to the 12x limit, and then distribute the remainder evenly across the entire company. That is, give everyone a single percentage of his/her salary as a bonus, preserving the 12x ratio. He could conceivably only give the bonus to the lowest-paid employees to maximize his own bonus, but that would alienate the overwhelming majority of the company.

There's no need to raise salaries or wages in order to comply with a relative cap on total compensation. In fact, I think it's pretty irresponsible to raise anyone's salaries based on a windfall year for the company as a whole; precisely for the reasons you specified.

Comment Re:-Wall (Score 1) 470

If the compiler decides it can delete a conditional because it's always true or always false, I most certainly do want a warning!

What if the conditional is based on a macro that is user-defined, to enable or disable functionality at compile-time? Or what if the conditional is based on template parameters, for C++? I see those use-cases on a regular basis, and the relevant code depends upon the compiler to properly optimize out the conditional and dead code for performance.

Comment Re:Inflammatory Subject (Score 1) 470

I basically distrust pointers, but especially any pointers on which the user does arithmetic. Some people think that's a snazzy way to move through an array.

In C and C++, all array iteration is pointer arithmetic, so your "some people" is really everyone. Always remember that foo[n] is equivalent to n[foo] is equivalent to *(foo+n).

Comment Re:wrong two words (Score 1) 740

Tax these millisecond trades and they'd go away or, at least, the volume would drop significantly.

I recommend against that. The profit margin on these "news" style trades is so high that a tax would not impact them. A new tax will reduce volume, but it won't do diddly-squat about this particular issue.

Instead of the paltry fines that the SEC levies on the cheaters, they ought to take the entire transaction away from the guilty party.

Busted trades can hurt the cheaters' counterparties, so you are effectively punishing all market participants by doing this. Better to just force the cheating company to disgorge all profits from the trade. They can keep the position they acquired, but fraudulent proceeds go to the regulatory agency instead.

Comment Re:Relative (Score 1) 356

10x the productivity, 10x the bugs.

I wholly disagree. If someone cranks out a lot of buggy code, it's arguable that the functional value of the code is also bundled with a lot of technical debt. So, if you are measuring 10x the functional value, then yes you may have many bugs. But a real productivity metric should account for technical debt, and therefore the hypothetical 10x developers are probably both producing more functional value and fewer bugs. In fact, maybe your best 10x developers are the ones who produce the same functional value as everyone else, but find and preemptively fix bugs like a well-oiled machine.

Slashdot Top Deals

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Working...