Follow Slashdot stories on Twitter


Forgot your password?

Comment: Re:20 Years (Score 4, Insightful) 361

by jareth-0205 (#49749841) Attached to: How Java Changed Programming Forever

20 Years of write once and test everywhere! And now thanks to Android there are over 18000 distict Andoid platforms to test on too!!

What you call 'fragmentation' I call 'variety'. And since Android app crash rates are actually lower than iOS ones (ie a platform with much lower 'fragmentation') then it clearly isn't the problem that you think it is...

Comment: Re:Not easiest to read, but forgiving... (Score 1) 399

by jareth-0205 (#49744305) Attached to: The Reason For Java's Staying Power: It's Easy To Read

A problem with Java and C# is that it is possible to create memory leaks in those languages, but since people rely so much on garbage collection they don't think about it and get bit in the ass. Event handlers shared across processes are particularly dangerous.

I mean, yes, you can't get away with not knowing anything at all about memory management in Java, but singling out edge cases that are a problem vs the vast majority of cases where it's superior is sort of missing the point. Rather like saying that wearing shoes is a problem because you sometimes get a stone in them, far better that you should always go bare feet and constantly make sure you don't step on anything sharp.

Comment: Re:"Easy to read" is non-sense (Score 4, Insightful) 399

by jareth-0205 (#49742735) Attached to: The Reason For Java's Staying Power: It's Easy To Read

I am tired of hearing languages are "easy to read". If a piece of code is well written and identifiers are well named anyone who is accustomed to the syntax or syntax that is SIMILAR will be able to read it. The point is that C style syntax have been what the majority of programmers have been used to so it has become a staple. However, if it was down to pure logic and an understanding of the English language Ada, Pascal, and (Visual) Basic would be the most readable.. and who here thinks that -- we've all been brainwashed by CS101.

Clearly a language can be easy or hard to read - Or do you think well-written Brainfuck is easy to read? Since programs are written by actual flawed humans who make stupid mistakes or have weird style preferences sometimes, it's generally a good idea to have a language syntax that doesn't let them shoot themselves in the foot.

Comment: Re:It was an app on a WORK-Issued Phone! (Score 2) 776

Am I missing something?

That the request in the first place is immoral? That being tracked outside your job is a infringment on a normal wish for privacy? That you are having to jump through hoops (basically, lie) to keep your employer happy? What do you think will happen when they learn of your faraday bag and decide to adjust their expectations accordingly? (ie expecting that out of signal = you have switched off the phone) You'll be in exactly the same position, you've only 'bought' yourself a few months of freedom, at most.

Comment: Re:It was an app on a WORK-Issued Phone! (Score 1) 776

The reason we have laws is to protect the weaker party from stronger parties. Employers are usually in a stronger position (there are always other employees, the employees have a pressing urge to eat) so agreeing to something does not just make it OK. If you are strongarmed, it's hardly a fair exchange.

Comment: Re:It was an app on a WORK-Issued Phone! (Score 1) 776

That's a great point but it does seem like a company should have the right to enable GPS tracking for company assets.

You know, it really doesn't. Companies don't feel the need to track every pencil that goes out of their office, the only reason they're tracking the phone is because it's easy and has a person attached to it. If you can't trust your employee to take care of a company asset then you can't trust your employee for much at all.

Comment: Re:It was an app on a WORK-Issued Phone! (Score 1) 776

It is important to note, however, that putting the phone in the Faraday bag emulated loss of signal, instead of loss of power, since the program in the phone reported these conditions differently, and so also were the interpretations of these conditions by management.

OK, you may have got around the problem for you, but other people are still being screwed, and management are still having silly expectations. Having some balls and switching the thing off on your own time is better for everyone.

Comment: Re:Some good data... (Score 1) 434

by jareth-0205 (#49627675) Attached to: Google Can't Ignore the Android Update Problem Any Longer

I love the regularity of this type of article, and the complete lack of justification why suddenly *now* it's necessary whereas demonstrably before now it has not been required.

It's not perfect, but the Apple model of effectively forcing old hardware into uselessness (ie becoming so slow with the latest OS) isn't exactly perfect either.

Comment: Re:Is this Google's fault? (Score 1) 434

by jareth-0205 (#49627667) Attached to: Google Can't Ignore the Android Update Problem Any Longer

When there's a new version of iOS, I get it the day it's released.

And I have seen every generation of iPhone eventually be upgraded into uselessness because the hardware is too slow to run the operating system. What's worse, because the majority do get upgraded, app developers quickly stop supporting old OS versions and those people who don't upgrade *still* end up with a useless smartphone because the apps stop working. It's not all bread and roses in the iOS model either.

Air pollution is really making us pay through the nose.