Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Compare cell phone plans using Wirefly's innovative plan comparison tool ×

Comment Re:I've gone through four iPhones due to this issu (Score 2) 222

A "failure" here includes an app that crashes. In your case you're saying the touch screen has failed to work, 4 times in a row, and somehow you know it's about to be 5 times.

The chance of a failure involving the touchscreen is statistically (from the report you didn't read) 3%. Raising 0.03 to the fifth power gives a failure rate of 0.0000000243.

Still going with Occam.

Comment Re:I've gone through four iPhones due to this issu (Score 1) 222

Well, literally hundreds of millions of people (per year) buy iPhones (last 12 months was 215 million) and don't have this problem.

I could see you getting a bad phone - shit happens. I could (just about) see you getting *two* bad phones out of two. There is no way I'd buy that you got three successive phones that failed in the same way, as for five ? Well, I'll be charitable and say you must be the unluckiest person on the planet. Is your name Brian by any chance ?

For reference: "In line with the firm’s fourth-quarter report, a study that analyzed smartphone failures during the first quarter of 2016 determined that Android devices cause far more problems for their owners than iPhones. According to Blancco Technology Group’s new data, 44% of Android phones experienced failures between January and March of this year, compared to 25% of iPhones"

Occam's razor says I still think you don't look after the phone, assuming you're telling the truth. Sorry.

Comment Re:So much for Apple's "better design" (Score 1, Troll) 222

Yep, in an nutshell.

You sell 215 million (how many phones Apple sold in the last 12 months) of *anything*, and there's going to be a tiny percentage of them that go wrong in some pattern-like way. Even 0.001% of 215 million is 2150 people with a problem, and although a failure rate of 0.001% is pretty damn good with such a complex device, that's still enough for "many" people to come up with a common problem and someone to get some ad-revenue from the click-bait headline.

(Also own an iPhone, a 6+, and haven't seen any issues)

Comment Re:So much for Apple's "better design" (Score 0) 222

Oh for crying out loud.

There are literally (and I use the word correctly) *billions* of BGA chips out there, in all environments from the most benign to the harshest around, from industrial levels of vibration to space exploration (including the launch). Shock, horror, in a sample size that large, some of them fail, well cry me a river. There is no human technology that is 100% perfect, but soldering chips, yes, even BGA chips to boards is pretty damn close.

As for not doing them at home, I've done BGA chips at home many many times - you can actually do them with a toaster oven, but if you want a good (i.e.: ~100%) success rate, you could always get one of these. If you look past the truly egregious website, there's a really well engineered product there, which guarantees alignment as the chip is placed. I've got one and frankly I prefer doing a BGA chip than soldering a QFP by hand (of course the machine does QFP too...)

Inspection, now, that's a different beast. I've thought about getting an old dental XRAY machine off eBay, but who knows if it's strong enough. One day I'll remember to take one of my boards along to my dentist and get them to take a snapshot of it. At the moment, I'm too busy building a laser-cutter anyway.

Comment Re:Best response to telemarketers (Score 3, Interesting) 105

When a call says "Internat" in the caller ID, I answer in French and refuse to speak anything other than French. (The only people I know who are abroad and phone me by conventional means are French - all those living further afield use Skype.)

It's quite fun. My French isn't that good, but it's better than that of the average scammer.

Comment Re:Other poll ideas (Score 1) 544

Does it count if I used to help manufacture the original CGI cards for IBM PCs?

Don't you mean CGA rather than CGI?

I used to maintain an application which used its successor, the original EGA card, in IBM XT machines. That involved some quite clever assembler in order to be able to write text to the screen at an acceptable speed. The in-built BIOS/MS-DOS functionality was unusable crap.

Comment Re:Blame Digital's RT11 for the backslash (Score 1) 141

Would dir /s produce a listing of all subdirectories of the current working directory?

Yes. A space followed by a slash would always be interpreted as a switch introducer.

Directory separators generally occur in the middle of a string, the only exception being when you want to talk about the root directory of a drive, without specifying which drive you want.

You use "C:/" to mean the root directory of C. It would be quite natural to use ":/" to mean the root directory of whatever drive is current.

It's not as if all this hadn't been done before - Microsoft were just never very good at reading manuals and learning from what had gone before. (See their totally brain-dead handling of daylight saving time.)

Comment Re:Blame Digital's RT11 for the backslash (Score 1) 141

And indeed, it was used as a switch character in VMS too. The error however was in changing the directory separator character (which in underlying MS-DOS is still "/") to the totally unsuitable "\".

I remember the early OS/2 development kit tools, where clearly a dictat had gone out to the developers saying that both "-" and "/" were to be used as switch characters. The trouble was, they hadn't done it properly by implementing some library code, but instead each tool developer had done it himself. The end result was that some accepted "-", some accepted "/", some accepted both, and some would take one or the other, but not both in the same command line. A horrible mess.

It would not have been hard though to allow "/" to be used as a switch character to COMMAND.COM, whilst still retaining its use as a directory separator.

Comment Re:But Backspace as Browser-Back really sucks. (Score 2) 141

Agreed - it was a really stupid mis-feature in early browsers which has unfortunately been carried on and some people have become used to it and don't want to lose it. Although "Backspace" and "Go back" both contain the four-letter sequence "back", they actually do completely different things and the key should never have been overloaded to do something so totally different.

It probably seemed like a good idea at the time to the person who thought of it, and unfortunately he or she implemented it without really thinking it through. Much pain has thus been inflicted.

It's a bit like the twit at Microsoft who decided to change the directory separator understood by COMMAND.COM from "/" to "\" because he wanted to use "/" for something else. (N.B. it was only ever the command shell which required this. The underlying OS has always understood "/" as a directory separator.) It seemed like a good idea at the time, but it similarly wasn't thought through and has caused endless pain since.

Comment Re:1995 (Score 1) 225

10B-2 phase, which gave you all the disadvantages of TR

I'd agree it gave you some, but never quite all.

I remember walking the length of the network at my first job, carrying a terminator, unplugging each device in series to figure out where the problem was.

True, but the terminators had the advantage that they were passive devices. Once you had a good set of cables and terminators, they then very seldom went wrong. The BNC connectors had a very positive latching action and you could be confident that they would stay together. You then just had to indoctrinate users with the idea that their hands would be chopped off if they unplugged any of them.

TR on the other hand relied on very active components in the MAU, which had a high failure rate. That awful sound of an MAU continually clicking as it tried to remember how to do networking.

Comment Re:1995 (Score 2) 225

Basically it's what you want to run your Nuclear Power Plants, live-saving medical devices and bizarly expensive "failure is not an option" Space Equiment with.

The design intention was to produce something more reliable, but the implementation failed miserably. Those clunky connectors where you could never be quite sure that they'd mated correctly. Lost tokens resulting in periods of no connectivity. The fun game of going into your comms cupboard and unplugging each lead in turn from the MAU in order to plug in that magic reset gadget, which might then restore connectivity to your LAN. Token Ring was a train-wreck with an awful lot of money pushing it to big business.

Comment Re:1995 (Score 4, Insightful) 225

The point of Token Ring was to have plugs and sockets where it was impossible to put the plug in the wrong way around - or the right way around.

And indeed, you could simply plug two plugs together.

I used to do quite a few joint pitches with IBM sales-folk back then, and it was amusing to watch the show as they addressed the question of which networking hardware to go for. The plot was always the same. At early meetings they would say, "IBM sells both Ethernet and Token Ring and we recommend whichever is most appropriate for each customer. We'll need to learn more about your particular requirements before we can say which one is more suitable for you." Then, several meetings later when lots of things had been discussed, but nothing really relevant to the networking hardware the message would become, "Now we've had a chance to assess your particular requirements, we can say that for your particular case Token Ring would be better." It was always Token Ring, and never any explanation as to why.

The real point of Token Ring was that IBM owned it and they didn't own Ethernet. It set out to solve a problem which didn't exist if you designed your network properly in the first place (overloaded Ethernet provides poor service to everyone) and introduced far more of its own. Like so many IBM technologies, it was a mess. Don't get me started on APPC.

Comment Re:Invitation-only (Score 2) 39

Yep, they ought to let you in to the "invite" group if you find something and they didn't "invite" you. For feck's sake Apple. Oh, wait, that's the 3rd paragraph in TFA.

Seriously, this is how Apple do it - they start a small project off to get experience, then they roll it out. I can't see the problem here...

Slashdot Top Deals