Follow Slashdot stories on Twitter


Forgot your password?
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Comment Re:What I don't understand. (Score 1) 56

I think there's a reasonable (flawed) assumption devices provide an acceptable level of physical protection for their batteries, mainly from puncture and external short circuits. At least more protection than padded bags, cardboard or light plastic packing is going to achieve without stringent unenforceable packing standards.

Another condition for transporting in devices is that they cannot turn on, ruling out most of the causes of in-device fires.

Possibly credible if you ignore cheap knockoffs that aren't standards tested.

Comment Re:The only problem that matters... (Score 1) 92

Too expensive is the big problem but it's not the only one. Android has seen many attempts to sell devices with physical keyboard's, outside the ultra low end, where a keyboard can improve on a poor and small touchscreen, the market rejected them all.

For all we claim to want them, on modern devices we don't need them and once that sinks in we choose the smaller, lighter version. I even carry a keyboard case with my tablet yet never bother using it as anything but a case and kickstand.

Blackberry fulfilled a need that no longer exists. It probably would have sank even on their own OS with today's hardware.

Comment Re:You have to know how to secure a Windows 10 PC (Score 1) 982

The scum managed to update my network HTPC this weekend and wiped all my firewall config in the process. Best guess is they noticed it was blocking the telemetry and most update shit and 'fixed' it. Fixed with extreme prejudice.

There really is nothing they won't do to take control of your hardware and it can only get worse till a few class action suits hit them in the wallet.

Comment Re:Thanks, Summary (Score 0) 532

If the mirrors were perfect the input energy would just bounce around forever generating thrust and this would be a perpetual motion machine. We don't believe in them.

So somewhere energy is leaking out of the cavity and the thrust is easily explained if there's any bias to the direction it leaks in. It works because the cavity shape creates a bias to the leakage.

Comment Re:Why conceal it? (Score 1) 740

"The fear the companies have is that there will be non GMO products available at the same price they have been selling theirs at, and everyone will buy that instead"


The vast majority of GM food is designed to be cheaper to grow, not be better as food. As long as you can't distinguish it from non GM food you can't assess a fair price for it. You can't do the arithmetic and work out how much of the saving the patent owning company is siphoning off, or work out if you're getting a good deal.

The industry is afraid the public will realise the cost benefits aren't reaching them, that there's no reason to buy GM.

Comment Re:Automatic Updates. (Score 1) 515

And Microsoft are trying very,very hard to give as many opportunities to make that mistake as possible, simultaneously trying to ensure it's a damn easy mistake to make with deceptive install dialogs.

Trickery, it's still wrong, no better than any other malware campaign relying on the same tricks.

Comment Re:AdBlock brought this upon themselves (Score 1) 317

Since the option is 'acceptable but less effective' or 'no ads, no effect' it's not really a choice.

However 'effective' largely means compared to it's competition in a near zero sum game. Fighting over existing sales not creating new ones. That's how we got in this mess with continuous escalation 'for effect'.

Adblocking and whitelisting just level the playing field, removing the ability for excess. I might consider enabling it when the checkers prove they can do the job right.

What I'm unlikely to ever do is trust the sites or ad middlemen to police themselves. They'll surely try some scheme to bypass adblocker whitelisting. It will be ignored.

Comment Re:What is DevOps anyway ? (Score 1) 166

I've read the propaganda, but still I don't see how it departs from simple common sense

That would be the 'trusting automated testing enough to push potentially catastrophic updates straight to production' part. Not assigning blame to the dev's fixing the resulting mess might be a necessary concession to getting the job done, no one accepting responsibility for such a testing failure, not acceptable.

For many organisations giving the end user faster updates most of the time is a small benefit compared to the risks involved.

Comment Re:I understand the consternation (Score 2, Insightful) 665

1: this infection defaults to enabled in the optional update list, it's trying to get installed 'by accident'. Trying very hard.

2: it's burning 3Gb of my deliberately small C: partition and every time I deleted the installer it just downloaded it again.

That's not looking like any sort of choice to me unless I revert the entire OS to an unsafe state without security updates. Given I don't have a clean ISO for Win8 with Bing that's going to be a challenge.

They truly are scum.

Comment Re:I wouldn't count on failure yet (Score 1) 131

I don't understand why the GUI would even be difficult. There are a finite number of calls. All they have to do is be slavishly followed

There may be a finite number of them (vast but still finite), they're sitting in a sea of asynchronous execution while maintaining internal state. If MS don't just clone Android source, manually reproducing all the subtle interactions adds a huge level of complexity to the task.

Get that all working and you still have to replace the rendering layer or accept the graphics won't render identically, shim the hardware drivers and fake up an interface to hide lots of timing and formatting issues with the hardware.

Then remember, Microsoft has spent years telling people how much more efficiently Windows uses hardware than Android. That's suddenly not true.

It's not easy.

Comment Re: Prone to promise too much (Score 1) 371

Our 'planning task' took a dozen programmers 4 months staring at and experimenting with the codebase before we even knew enough to start splitting the work into tasks. Even then we had things that obviously couldn't be guesstimated with any sort of accuracy or split into small parallel workflows with any hope of measuring progress.

Some projects are just so fscked the only method that works is hitting them with the sharpest sticks you can find till they give up.

Slashdot Top Deals

grep me no patterns and I'll tell you no lines.