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


Forgot your password?
Slashdot Deals: Prep for the CompTIA A+ certification exam. Save 95% on the CompTIA IT Certification Bundle ×

Comment Re:I Don't Listen to Radio (Score 2) 160

The BBC does not advertise (other than promoting its own services) nor are the channels funded by the licence fee legally available outside the UK. The adverts you are referring to are presumably courtesy of the crooks who are 'stealing' the content and reselling it in their own wrapper.

Comment Keep kids out of it (Score 2) 146

A number of the BBC stories amount to publicity-seeking parents violating the privacy of their non-censenting children by allowing them to be named as subjects in, particularly health-related, stories.

Note for parents: Children are not your property. Even if you think that publishing self-serving stories about them in the media or on the web is your prerogative they will eventually grow up and decide that you had no f***ing business so to do.

Comment European Data Protection Law (Score 3, Informative) 130

As this is a European company it is subject to European data protection and privacy legislation. Many countries have given their enforcement agencies quite significant enforcement powers to punish abuse and there is pressure for the penalties to be increased to the point that non-compliance is not going to be viable business model:


Comment Ten pieces of feedback 100 000 times (Score 4, Insightful) 236

Mass release of technical preview software is is showing contempt for users and developers by wasting both sides' time by duplicating effort. In my experience the best way do it is to initially release to a small sample of users an fix the issues they raise. Then release to a somewhat larger sample and fix the issues they raise, etc. If you are getting more than a handful of duplicated reports then you are ramping up too fast. If you are getting reports in at a rate that exceeds your developers capacity to evaluate them and, if necessary, follow up with the user then you are ramping up too fast.

Comment Re:Pull the disk (Score 1) 466

I don't even see why there are so many other posts about Kermit, laplink, file transfers, PCMCIA, etc etc. Worst case is that the hard drive has a proprietary connector and you have to solder an adapter on.

Because rule #1 when trying to get data off twenty-year-old hardware is "If it's working, mess with it as little as possible."

Comment Go with the majority (Score 4, Insightful) 165

In my experience, if you are upgrading legacy code that assumed straightforward ascii then utf8 is the
way to go. It was invented for the purpose by someone very smart (Ken Thompson). If there were a 'Neatest Hacks of All Time' competition utf8 would be my nomination.

The only real issues I've encountered are the usual ones of comparisons between equivalent characters and defining collating order. These stop being a problem (or more precisely 'your' problem) once you abandon the idea of rolling your own and use a decent utf8 string library.

You might have mail.