Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: Re:Why the hell do phones not have a firewall?? (Score 1) 614 614

I thinking about doing a captcha. "Dial the the number you hear spoken after the tone."

.

Background noise and effects could be added , but it's uncommon enough at the moment that I doubt the robot calls would be able to cope with it even when the spoken voice clear.

Comment: Re:POD? (Score 1) 210 210

I've got a nice eBook reader which I bought for reading the sort of scholarly articles I can get from the ACM digital library, and other web sources.

I still find myself using printed copies purely because I can *much* more easily flip between pages, and can organise the pages on the desk the way I like as I try to follow the argument (and a self printed copy is better than a bound copy here, because the binding restricts the layouts).

I use a ebook reader/printed copies rather than the screen to give my eyes a rest, and a change. The point is that a single format is not the best for every use, so I think the death of the printed book is overhyped and it will just become another media format (and probably a niche one). But books do have some major advantages over the other formats. They don't require any support technology to read, they are stable for a long time , are not as fragile as an ebook screen, and they are cheaper than an ebook reader. All of which may be important to your needs.

Novels, I prefer in ePub/Mobi formats since the reader I have is has a form factor which allows it to fit into a pocket better than the massmarket paperback format. And this is depsite having a screen approximately equal to the pages size, the ebooks thinner form factor work better given the way most pockets are constructed.

Comment: Re:A simple resolution (Score 1) 285 285

I completely disagree.

There is no reason for the OOXML specification to use date formats based on the old .xls format. The issue about keeping bug for bug compatibility is about in-memory representation, the standard specifies on-disk representation. They do not have to be the same you know...

Microsoft have specified a new on-disk representation which continues to have a madness just to simplify their load/save implementation. The fact that it is due to compatibility with an ancient bug from a competitor is completely irrelevant. They could have specified the OOXML standard to be clean and dealt with any issues in their save/load code, or elsewhere in excel.

Programming

When Rewriting an App Actually Makes Sense 289 289

vlangber writes "Joel Spolsky wrote a famous blog post back in 2000 called 'Things You Should Never Do, Part I,' where he wrote the following: '[T]he single worst strategic mistake that any software company can make: They decided to rewrite the code from scratch.' Here is a story about a software company that decided to rewrite their application from scratch, and their experiences from that process."

Comment: Re:Use the Coax as a wirepull for the cat5 (Score 1) 608 608

Unfortuantely you aren't quite right.

The different impedance is sometime enough to trip the collision detection circuitry. Also the drivers are actually low impedance as they deliberately drive current into the cable , and have high impedance detectors.

It's all about the collision detecttion..., I have seen it work though - but you've got to be careful or lucky.

Comment: Re:Pining for the good old days (Score 2, Insightful) 280 280

True.

Except that doesn't account for having a method (destructor) which will be called when your variable goes out of scope.

Then you have generic's on top of that.

And in c++0x, auto, lambda and rvalue refs. There a whole lot more to c++ than objects.

[Note: I program in both. & python & perl &......]

Comment: Re:Not Samba? (Score 4, Interesting) 409 409

But since you haven't posted anything more we can't be sure.

What did you investigate? What samba tuning parameters did you try?

Last year I had a very similiar problem, which actullay turned out to be network card driver issue. I upgraded from the stock debian stable kernel to one from testing and the problem went away.

My point is a single example without actually knowing what was investigated - is just a worthless anecdote.

"If you own a machine, you are in turn owned by it, and spend your time serving it..." -- Marion Zimmer Bradley, _The Forbidden Tower_

Working...