Slashdot stories can be listened to in audio form via an RSS feed, as read by our own robotic overlord.


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Such a stupid question (Score 1) 336

by DrXym (#49187097) Attached to: Would You Need a License To Drive a Self-Driving Car?
The day when we have self drive cars capable of navigating from one point to another in a timely fashion with no intervention from the passenger is so ludicrously far off that yes of course there will be a driver, and yes of course that driver will require a licence, and yes of course that driver will have to be concious and not under the influence of anything.

It is trivial to envisage situations that occur every single day during a commute that would baffle a self drive vehicle and would cause it to want to hand control back to to a human.

The closest that we are likely to come to driverless cars are those operating on closed loops, e.g. between airport terminals where the road layout and the number of parameters is manageable. Even then there is probably some guy sat in a booth somewhere who can take over the controls if the car does something dumb or gets confused.

Comment: Re:FDE on Android doesn't work as of yet (Score 1) 119

by DrXym (#49172013) Attached to: Google Backs Off Default Encryption on New Android Lollilop Devices
I bet virtually every SoC has the hardware. Whether it exposes this hardware to the kernel in a stable manner through a driver is another matter.

I bet the performance hit on battery or IO would be neglible if it were functioning properly. Maybe Google has had problems with some chipsets.

Comment: Re:Compiz is the bug. It needs to die. (Score 1) 51

by DrXym (#49171413) Attached to: NVIDIA Fixes Old Compiz Bug
X is arcane. There is a strong desire to get rid of it because it's inefficient (network, CPU, GPU), filled with obsolete APIs that nobody uses and an increasing number of extensions designed to work around this brain damage.

Hence the drive to replace it with Wayland. People who still need X can run X over Wayland.

Comment: I should think the choice is obvious (Score 1) 392

by DrXym (#49170467) Attached to: Ask Slashdot: Which Classic OOP Compiled Language: Objective-C Or C++?
I'm not even sure what a "classic object oriented compiled language" is meant to mean or why it should be the criteria for programming something, but given the choice of C++ or Obj-C then C++ is the answer in virtually every case. Obj-C only makes sense when targetting iOS / OS X or some niche like OpenStep and whatever merits Obj-C might have as a language it would be insane to use it anywhere else.

Comment: Re:FDE on Android doesn't work as of yet (Score 3, Interesting) 119

by DrXym (#49170165) Attached to: Google Backs Off Default Encryption on New Android Lollilop Devices
Most SoCs have encryption circuitry so I doubt it has any appreciable effect on performance or battery providing its done through hardware. In Linux disk encryption is via dm-crypt which in turn is via the crypto api so Android could probably use that to provide blanket crypto in addition to whatever crypto is done higher up by apps or user storage.

Comment: The reason I don't like it (Score 2) 145

by DrXym (#49164315) Attached to: Google+ Divided Into Photos and Streams, With New Boss
I think G+ looks great visually and in terms of what it is (a Twitter/Facebook a-like) I guess it's okay.

The problem for me is that it nags me constantly. Do I know these people? Do you want to connect to these people? Are these groups of interest to you? Tell us about yourself. Naturally it doesn't offer options to hide these panes or put them away in a "discover" section where they're out of sight. They're always there nagging me.

I don't expect to give my fucking life story over for a glorified feed and so I don't use it much at all. Another issue for me is that I used to use iGoogle as my home page. They canned that service and some other related ones, presumably because they thought people would use G+ instead if they removed the alternatives. It didn't work for me because I want a page with news headlines and some other RSS stuff I read and some wall of stuff is simply not what I want - so I use My Yahoo instead.

Comment: Blame email clients (Score 4, Insightful) 308

by DrXym (#49126051) Attached to: Moxie Marlinspike: GPG Has Run Its Course
The first mistake made by email clients is they added support for a broken-by-design protocol called S/MIME which used asymmetric encryption through the entire message and was thus cripplingly slow. The ciphers were also covered by patents and had weak key lengths. Messages were signed with a cert like https, and were required to be signed by a CA. And you couldn't get a key unless you paid a CA for one. Oh and keys expired meaning you might have multiple dead keys to maintain if you wanted to open an old email. And no email client or ISP actually offered to give you a key or set you up with one so you had to figure this all out for yourself. And functionality like search / filtering broke on encrypted mail because the client never bothered to maintain an encrypted index of the plaintext that could have allowed it to work.

Then PGP / GPG solved a lot of this bullshit, starting with generating keys for free but email clients never bothered to give it proper support. Instead they offered up some plugin APIs and unsurprisingly PGP / GPG ended up with half assed implementations too. Even fairly good extensions like Enigmail didn't integrate with the client as closely as they should.

And by this point cloud based email took off and crypto fell by the way side. If you want to use crypto in GMail then you have to cut and paste and clearly it's too much effort.

So I really don't blame GPG here. If the first thing an email did during setup was ENCOURAGE a user to create a key; and by default published that key; and attached the key sig to outgoing emails; and automatically looked up incoming email addresses; and automatically encrypted content when all recipients had their own key; and didn't hobble functionality for any of this (e.g. search still worked). THEN this wouldn't even be a problem. Encryption would have been the default and it would be an irrelevance if it was PGP or GPG was under the covers.

If at first you don't succeed, you must be a programmer.