Forgot your password?
typodupeerror

Comment: Moo (Score 1) 3

by Chacham (#47799355) Attached to: Seagate - At least I got a heads up

I wouldn't touch WD.

WD basically invented the hard drive and used to be awesome. Then they started selling garbage. After having a number of their drives fail and seeing online reports of the same, i no longer consider them an option. Same story with Epson for printers. It make me wonder why these great companies decided to destroy the one thing they had: A brand that stood for quality.

Comment: Re:Broadcom... (Score 4, Informative) 141

by Cyberdyne (#47796203) Attached to: Update: Raspberry Pi-Compatible Development Board Cancelled

The choice [of a Broadcom SoC] by the RPi-team was utterly stupid and can only be attributed to incompetence.

Well, Eben Upton's job working for Broadcom was probably a factor there... Personally, I'd trace the idea back before he had that job - I recall a discussion about the Gameboy Advance developer kit in the summer of 2002, and the lack of affordable programmable devices at the time. I suspect he'd have had a real struggle getting anywhere close to the Pi's target price without getting discounted access to the Broadcom SoC he used, though. I haven't spoken to him recently, but my impression was that far from "RPi Foundation pressed Broadcom to stop selling BCM2835 to competing projects" as claimed, it was more "Eben twisted arms and got Broadcom to give RPF a special cut-price deal so they could afford it".

If anyone were to bring out a rival device from a "significantly superior" competitor, I'd be delighted to see it - and I suspect most if not all of the RPF people would too, since it wasn't about making money by selling lots of systems. (Of course, Broadcom didn't buy up the remains of ARM's parent company for nothing, so I'd be surprised to see something much better from a rival!) I was happy to see the Pi being ARM based, as a fan of ARM as far back as the ARM2 I first programmed, but I'm also happy to see rivals like the MIPS32 one mentioned recently: I like ARM, but I also like having a choice of platform, both hardware and software!

Comment: Re:That's nice, but... (Score 1) 373

by Cyberdyne (#47795833) Attached to: Microsoft Defies Court Order, Will Not Give Emails To US Government

But acting like they don't, or even loosing a minor case might set other criminals at ease about the security of their data within the Microsoft infrastructure.

Which, of course, could be exactly what the NSA want - police and FBI priorities may differ, but I suspect the NSA would rather have access to more information, thanks to a false sense of security, even at the expense of not being able to use it in court easily. If they "win", they get to use evidence this time - and they just warned the next hundred criminals to avoid MS servers, because of this case. "Lose", and they can keep reading it all in secret, using the information behind the scenes instead.

Comment: Re:Nice! (Score 4, Insightful) 73

by Qbertino (#47783057) Attached to: For $1.5M, DeepFlight Dragon Is an "Aircraft for the Water"

One single drug run^h^h^h^hdive and the thing has paid for itself.

How long can it dive? What mods does this thing need to lengthen the dive+travel time to a few days or even a week or two, depending on its speed? Extra Oxygen, toilet substitutes, extra battery packs, stronger motors to tug the drugs, etc.

Could maybe be done, but it's not easy. Truth is, I think by now it's actually more feasible for the cartells to get their hands on decomissioned subs and their former crew. Or something along those lines.

Comment: Yeah, impressive list. True. But ... (Score 1) 115

by Qbertino (#47782929) Attached to: PHP 5.6.0 Released

... consider this:

How many people and projects use PHP? How many use another PL? How many fixes and updates would be in line for that other PL if it would have the same userbase. ... When did Ruby finally become UTF8 safe again?

Make it work, then make it beautiful.

If any PL incorporates this philosophy, it's PHP.
And AFAICT they're doing pretty well following it, don't you think?

My 2 cents.

Comment: Re:Obvious Reason (Score 1) 568

by Qbertino (#47782735) Attached to: Why Women Have No Time For Wikipedia

With good reason. It's obvious by this that Wikipedia isn't doing enough to attract women to contribute. Such a small representation among women is shameful and certainly something must be done to address this glaring example of gender bias.

I'd say Wikipedia isn't good enough for *anybody* with more than two braincells to rub together to contribute to. Pseudoexperts deleting content without any explaination at all just because it was posted by anons, flat out wrong content, political scirmishes, lack of seperation of concerns and distribution of power, etc.

Wikipedia might be useful, but it is measurably worse than it needs to be. Try to do some useful contribution as anonymous to see what I mean.
I've stopped contributing to Wikipedia about 10 years ago.

Comment: Not the PSUs? The actual cables? (Score 2) 135

by Cyberdyne (#47763725) Attached to: HP Recalls 6 Million Power Cables Over Fire Hazard

How do you fuck something like that up?

All too easily it seems; my first MacBook Pro power lead caught fire a few years ago as well. This was the low-voltage (hence high current) end, though: in their quest to make everything thin and light, the cable was thin and flimsy, so one of the braided conductors frayed after a while. More current going down a thinner wire meant more heat - which softened the remaining copper and made the problem worse, until arcing started and I got a micro-firework display on my desk. (One of is successors managed to melt the plastic in the plug, that didn't make me happy either!)

On the mains end, even a hefty (for laptops) 300-odd watt PSU is only 3A from a US outlet, half that on the higher voltages elsewhere - usually easy enough to deal with, but one sloppy connection and you can get a tiny point getting very hot indeed. It's worse on the low voltage end: a single cable possibly carrying 20 or more amps, while getting rolled up, folded and stood on in transit, designed to be very light weight - yet also done on a budget. As soon as you start trying to shave weight and cost, I suspect it's all too easy for a wire to be just slightly too thin for the current, or a connection to be a little bit too weak for long term mobile use.

If you were building a high school or college electronics project and said you planned to run laptop currents and voltages through such thin wires and tiny connectors, you'd probably be told off or marked down - but commercially, thin, light and cheap trump safety margins and robustness.

Comment: Re:NT is best (Score 1) 190

by satch89450 (#47753535) Attached to: Munich Council Say Talk of LiMux Demise Is Greatly Exaggerated

>The proper file format for that purpose is usually PDF.

I know that. But the customers want editable copies, and do not want to go through Adobe or anyone else for a PDF editor. The customers want Word files. Now, tell me how to educate the customers, when the competition will do exactly what they want and so my client loses business to that competition, and your comment will be reasonable.

Absent that critical step, my hands are tied. And so are my client's hands tied.

Comment: Re:My opinion on the matter. (Score 1, Interesting) 810

by satch89450 (#47751393) Attached to: Choose Your Side On the Linux Divide

"What's broken exactly?" - PRECISELY.

The Red Hat 6.5 implementation does not work as documented. Either fix the code, or fix the documentation. I've not tried Red Hat 7 yet, haven't gotten a round tuit. Ever try to take System V init code and convert it to systemd? I even tried to A/B between Red Hat 5 code and Red Hat 6.5, and that didn't show the rules.

Comment: Re:snydeq = InfoWorld (Score 4, Informative) 810

by satch89450 (#47751349) Attached to: Choose Your Side On the Linux Divide

I felt it was enough a problem to submit a bug report to the CentOS people: https://bugs.centos.org/view.p... -- the problem I see is that the documentation for systemd and the observed results are different. Further, there are no instructions on how to take a System V init and convert it cleanly to systemd. I don't have a Red Hat Enterprise support license, so I couldn't report the issue to Red Hat. One of the problem of using an alternate distribution.

To this developer's eye, the systemd documentation is not ready for prime time. Note that this bug was reported against 6.5, not 7. I'll be looking at 7 when I get a round tuit.

Chemist who falls in acid will be tripping for weeks.

Working...