Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×

Comment Bitcoin: DON'T STORE (Score 1) 228

A lot of people are starting to put their money in bitcoin so they can actually have some control over it for once.

As a way to do fast person-to-person transaction, bitcoin protocole (and other crypto-coins) is a good idea (it's like cash transaction, but over the internet, although a bit slower. Or for EUropeans: it's like SEPA, direct payment without an intermediate, except that it's a bit faster).

But please, unless you're a gambler DO NOT store money as BTC (nor any other crypto-currency): its value fluctuate too much (1 BTC is 500$, perhaps 10$ tomorrow or 1000$ the day after tomorrow) , also if you rely on an on-line service ("web wallet") rather than your own bitcoin-protocol client ("wallet" software) there are risks out of your control (think about MtGox and similar scandals).

Otherwise cryptocoin protocols are really interesting, by making an intermediate un-necessary. (There's no "bitcoin company" handling the actual transaction, unlike Visa/Mastercard), and complete freedom of choice for each end-point of the transaction (both the merchant and the client can use any wallet software, exchange platform, payment processor, etc. as long as both end-point follow the bitcoin protocol. Just like any of them could be using any european bank for an online payment as long as both banks support SEPA)

Comment Incoming too? (Score 1) 228

Are incoming messages expensive too?
In EU, incoming SMS are free wherever you are (home network or roaming).
Us european tend to keep an older phone around. Swap your *home* SIM card into the old phone and put whatever you use when abroad (SIM with plan in target country, prepaid SIM for target country, or just some random sim that is cheap while roaming like XX-Sim).
We're still reachable on the usual number (can get message for free, can also acept calls but that has roaming charges), and have the travelling option on the main phone.

The Banks I've seen simply contact you instead of relying on complex tracking (you receive an SMS: "your credit card has been used in an usual place. Please contact us"). Just call the bank back and either authorise the payment or announce a stolen card/number.
Other banks alternatively use a side-channel confirmation (3DSecure, for example) while shopping online.
It has the advantage of being less invasive and not require an active collaboration of Phone provider. (you only confirm when a flag is raised, you don't need the bank and the phone provider continuously monitoring you).

Comment Testing facility (Score 2) 134

The interesting part, is that the guy is building a test-farm infrastructure.

The kernel benchmarking/bissecting stuff could be automated and could become part of the normal development project.
(Having the test farm continuously benchmark key linux project (llike kernel, mesa, etc.) while they are developed).

That is going to be:
- a very valuable ressource for linux development
- a service that can be sold or that can be sponsored by big player (Valve co-financing the mesa/gallium continuous benchmarking ?)

Comment AMD's official stance (Score 3, Informative) 134

And that's AMD official stance:
- once the opensource drivers get good enough, support for older cards gets removed from catalyst, and radeon is pointed as the official go-to solution for older cards.
- so catalyst = drivers for the current generation of cards (unless you want to beta test the bleeding-edge development) and radeon = drivers for all the previous generation (unless you want specifically a card that still isn't phased out yet, probably because the current openCL support is better in catalyst).
- that's also part of the reason why AMD has opensource driver developers on their payroll.

Comment Their more than "do" (Score 1) 134

Interestingly Valve doesn't merly influence the market by their game being a reason.
They actually do directly help progress with actual code.

See reports on the same Phoronix website of various OpenGL 4.x extension being added to Mesa by Valve.

One day, when the Mesa finally achieves full opengl 4x compliance, you'll know it's partly due to developer on Valve's payroll (in addition to those on Intel's and AMD's payrolls, and the independent volunteers in Nouveau project, and the thousands of other contributors - some corporate other independent).

Comment Business with whom?... (Score 1) 138

It doesn't matter in his case - if he wants to run a business, he might not even get a chance to prove that the issue is outdated, if it still ranks highly in google searches.

On the other hand, I think it would be highly unadviseable to do business with bank that bases its decision simply on a search result page, without even investigating *when* did the event referenced happen? To me, this sounds like very lazy practice and poor judgement and is going to bring problems down the line.
Better to ask for money loan from a bank that does proper investigations.

Comment Combine it with the other announcement. (Score 4, Insightful) 216

The second part 'threat to the country's national security' on the other hand is such a broad term, it is basicly a blank check where they can fill in any sentence for any crime as they wish.

Now combine this with the other announcement: "UK Seeks To Hold Terrorism Trial In Secret" so such "threat the national security" rule also means that the trial get to be secret.

So I guess it's really about the second part, and the first part is only there to give it more weight: 'HACKERS MIGHT KILL YOU!'

Yup. To me it sounds like "You do something we don't like with a computer? We get the right to disappear you! For Life! Cause, you see, it's a matter of national security. Thus the trial is secret, and the sentence is life"

Comment copyrigth trolls (Score 1) 191

and copyright trolls will join the **AAs to make such car not-street legal (even if it has nothing to do with the driving on street)
and will sue presumed-fraudulent drivers automatic al. ...so just after the Nth scandal of **AA making fools of themselves after issuing a C&D letter for reason of torrenting against the IP address of a networked laser printer, prepare yourself to read about a warning issued for reason of unlicensed washer fluid against the VIN... of a lawnmower.

Comment Differnet perspective (Score 4, Insightful) 80

AMD's perspective is that Mantle is less problematic:
- Mantle's spec are open.
- Also it's just a very thin layer above the bare hardware. Actual problems will mostly be confined in the actual game engine.
- Game engine code is still completely at the hand of the developer and any bug or short coming is fixable.
Whereas, regarding GameWorks:
- It's a closed-source blackbox
- It's a huge midleware, i.e.: part of the engine itself.
- The part of the engine that is GameWorks is closed and if there are any problems (like not following standard and stalling the pipeline) no way that a developer will notice and be able to fix, even as AMD are willing to help. Whereas Nivida could be fixing this by patching around the problem in the driver (as usual), because they control the stack.

So from their point of view and given their philosophies, GameWorks is really destructive, both to them and to the whole market in general (gameworks is as much problematic to ATI, as it is to Intel [even if it is a smaller player] and to the huge diverse ecosystem of 3D chips in smartphone and tablets).

Now, shift the perspective to Nvidia.
First they are the dominant player (AMD is much smaller, even if they are the only other one worth considering).
So most of the people are going to heavily optimise game to their hardware, and then maybe provide an alternate "also ran" back-end for mantle. (Just like in the old days of Glide / OpenGL / DX backends).
What does Mantle bring to the table? Better driver performance? Well... Nvidia has been into the driver optimisation business *FOR AGES*, and they are already very good at it. What is the more likely, that in case of performance problems developers are going to jump on mass to a newer API that is only available from one non-dominant PC player, and a few consoles, and completely missing on any other platform? Or that Nidia will patch around the per problem by hacking their own platform, and dev will continue to use the ?
In Nvidia's perspective and way to work, Mantle is completely irrelevant, barely registering a "blip" on the marketing-radar.

that's why there's some outcry against GameWorks, whereas the most Mantle has managed to attract is a "meh". (and will mostly be considered as yet another wanabe-API that's going to die in the mid- to long-term)

Comment "Quirks mode" all over again? (Score 3, Insightful) 80

to me it sounds like again like the beginning of Internet Explorer vs. Firefox compliance to HTML standards.

Down to the detail of how it pans out:
- one company being the popular one (Microsoft, Nvidia), so everybody code to their platform (IE, drivers) and end up unknowingly produce bad that code that happen to rely on the peculiarities of this platform (the non standard assumption of Nvidia's drivers, the weird re-interpretation of HTML done by IE's engine). When there are problem, they tend to hack their own code.
- the other company being the underdog (Mozilla, AMD) making a platform (Firefox, Catalyst) that tries to follow the open standard to the letter (HTML5, OpenGL), but in the end other person's code (websites, code) behaves poorly, because it breaks standard and relies on quirks that aren't present in that platform. The users complain of problem (broken HTML rendering worse under Firefox than IE, non-compliant openGL code's performance being more degraded on AMD then Nvidia hardware).

Funnily, if past history is any indicator, on the long run AMD's approach is better and either them or one of their successor is bound to manage to bring opengl-compliance more important than driver tricks.
(the fact that AMD is dominating the current iteration of consoles, might help bring more power to them)
Interestingly the embed world might one also end up helping just like it did the browser wars (Internet Explorer was far less prevalent in embed machine like PDA/Smartphone/Tablet than on desktop and the problems with broken HTML became much more apparent, and compliance with HTML5 [sure to run on as much platforms as possible] was determinant. Also the embed eco-system mostly centered around compliant engine (like Webkit)) due to the same factors (extremely heterogeneous ecosystem hardware-wise, where Nvidia is just one player among tons of others with their Tegra platform. compliance with OpenGL ES is what is going to be determinant as the embed platforms are going to need a lingua franca to insure that porting an engine is as smooth as possible and works easily on all smartphones/tablets, no matter if they boast PowerVRs, Vivante, Lima, Adreno, etc.)

Maybe we might need something along Acid test and w3c conformancy test to exercise drivers and test game code for standard non-compliance.
(That partly exist as "piglit" - the test suite that freedesktop.org uses to test opensource mesa and gallium drivers).

Comment All the others? (Score 3, Informative) 17

Compared with?

Nearly "all the rest":

- Intel only has an official open-source driver on Linux (only Windows gets a proprietary one). Their driver works, although it has less features than all the binaries (older version of OpenGL support).

- AMD has very decent *open source* drivers. Althought their *closed source Catalyst* isn't as good as Nvidia's binary, AMD's opensource Gallium3D is very good. It has sometime problems with the latest cards (indeed currently, it has problems with the latest generation of GCN 1.1 Volcanic Island cards), but runs otherwise good, and for older cards is better to the point that AMD drops support for old cards in Linux Catalyst and officially points to the opensource driver for supporting older hardware.

Meanwhile:

- Nvidia might have the best closed source driver (though still not collaborating nicely with standards, but this situation is slowly evolving), with full latest OpenGL support, etc. with decent stability...

- ... the nouveau driver is very bad. Not the authors' fault, as they could only rely on reverse engineering to get it working. So it's good that nvidia is finally making some baby-steps in the direction of helping nouveau.

Comment No levers to control all small parts in motor. (Score 1) 583

How about that truck carrying those huge metal pipes?

You, your robot car and anyone else is required to always stay at a safe breaking distance for anything in front. Legally, you should be keeping a safe distance *even in the absence* of metal pipes, so if anyone in front needs to break due to a sudden apparition of a kid, you won't rear-end them.
The robot car is less likely to be tail-gating than the average asshole.

kid decides to step into the road at the last moment, you saw him running down the driveway from behind a line of parked cars on the side of the road. Did the computer? of course not.

you'd be surprised, but that technology is *already* in production at several constructor (Volvo is equipping it as a standard).
Cars currently on the street are able to spot the kid and apply emergency breaking if needed. (If you ask: yes, that can currently be overridden simply by forcing otherwise on the car's gas pedal). In the next following year, such technology and other similar collision avoidance system are going to be mandatory for new cars in EU.
Now the small killer detail? You can extend the system by putting more cameras. Said volvo has also camera under the side mirror *constantly* monitoring blind sport all the while you drive.
Human driver? No way to graft extra heads/extra pairs of eyes, so only possible to concentrate and whatch one single target. Either whatch in front of the car *OR* whatch either of the side for blid sport *OR* get distracted while fumbling with audio/phone/whatever. Consumer level cars currently on the street are able to monitor all this *continuously, without ever interrupting*.

Did it see that huge pot hole?

Actually google's car have managed to total 700'000km without any pot hole-related problems, so one could decude that their solid-state lidars work as intended.

Speed is 'a' factor, but not always 'the' factor in accidents, although the cops love to say it is (to help justify keeping the limits lower so they can rake in more cash)

Speed *is* the dominant factor simply due to physical laws like E = 0.5mv^2 each increase of speed squares the amount of energy involved in case of crash, or kinetic energy that you must dump during an avoidance manoeuvre. (See comment above about never tail-gating to avoid rear-ending).

A computer can compute and keep a safe distance from anything in front to be able to break in case of emergencies. And unlike a driver who might get distracted (and hence needs reminders), a computer keep continuously keep an "eye" on that too in addition to watch for everything else. (Some simpler forms of this are already in production in automatic cruise controls on cars currently on the street. The only difference is that these car can only keep safe speeds regarding other cars [= They will slow down not to rear end a car]. They currently can't anticipate safe speeds for upcoming turns on the road, without having signs hinting a top speed that the camera can read [= they aren't able to slow down before a sharp turn]. Whereas google cars have repeatedly demonstrated to successfully adapt speed to road ahead)

If that aforementioned truck is about to jackknife

...which by it self would *NOT* be a problem if you kept a safe distance from the truck in front of you *AS REQUIRED BY DRIVING LAWS*.
(If you were stupid enough to tail gate a truck, you deserve anything that happens to you next)
(And the aforementioned collision-avoidance system could actually save you under some circumstance - simply due to having much faster reflexes than you and being able to apply emergency breaking before you even start to realise that you're on a collision course)

it might actually be more prudent to get out from around it which will probably mean violating the speed limit.

...again at which point you were probably already violating laws regarding safety distance.
Also, don't forget this nice thing called "inertia". Hint: the truck is currently already moving forward and very heavy. Jackknifing can't realistically be the trailer suddenly accelerating on its own. It's much more likely the truck breaking, but the trailer's breaks failing and the trailer still moving forward at its initial speed. Keyword here is "still moving forward". As the trailer is moving forward, the safest course would be to break and stop before reaching it... provided you have enough room to break (I hope you were keeping a breaking distance, didn't you?). Or hope that your collision-avoiding system would be already applying the breaks for you.
Starting complicated Hollywood manoeuvre around a truck that is about to fail catastrophically doesn't seems very safe...

It would also take a human to see the fact the truck is in trouble.

It also takes time for the human to process its input and it also requires that the human will react in a correct maner (and won't try something stupid).

All the computer can do is react by hitting the brakes after it detects the truck blocking the way...

Actually, the computer would already have started reacting long time ago, when it already did notice the change in relative speed to the truck. As soon as the distance between the two decreases, car with modern automatic-cruise-controls and collision-avoidance are already slowing down.

gl with that, even if it was following a 'safe' distance.

not "if". Modern cars, already "do" keep safe distance unless you hit the accelerator.
and the definition of 'safe' distance is that distance which allows you to stop in case of emergency (always assume that the vehicle in front of you could be hitting breaks at any time, like trying to avoid the kid from point 2 or trying to avoid a fallen object).
Due to the way inertia works, if you kept your distance you can always break in time if you kept your distance.

(Or you should change hobby, as following trucks that transport exotic matter in- and out- of area 51 doesn't seem a very sage one).

In fact electronics can help you in more circumstance. Like if you aren't actually following the knife jacking truck, but driving in the opposite direction in another lane. As a human, you probably aren't constantly monitoring all incoming truck just for the chance that it might be knifejacking. You probably will notice only once the incident is well underway. And there's a big chance that you'll collide (in a very bad manner, again due to inertia, due to the relative speed as you're heading toward each other, and that this relative speeds counts squared), while on the other hand, as a human you might find some creative way to attempt to avoid (if you are reactive enough).
Meanwhile, a modern car will detect it much earlier (As soon as the truck steps a bit out of its lane, into yours, moden car will simply treat this as a standard "object on the lane, currently on a collision course), the car will automatically slow down, sound a warning and prepare to be able to do an emergency breaking if the need comes. And you'll be informed much earlier, and will have time to react (like changing lane, which will also be easier as the cars was continuously monitoring your blind spot anyway).
And that's only a modern car. For google cars, google has already shown their on board software to be able to consider obstacles on the road and re-plan a different route to avoid them. By the time the truck's trailer is realy sideways, the google car would have moved away, on farthest (rightest if you're in a right-driving country).

As chaotic and inconsistent as humans can be, I think we're better off fixing the newfound inattentiveness

But there are a few other things:

- do not underestimate how far we've already reached *right now, as of today, with currently street-legal cars*. The fact that you couldn't imagine how this would be done on an Apple][ two decades ago, doesn't mean that it's not routinely deployed using modern hardware.

- a human can get stressed. There would be a difference between a well seasoned stock-car pilot who'll know to keep calm and has experience nowing how to react. And the terrified random six pack joe, who might start a stupid manoeuvre in a panic (like ramming his car into the one next to him while trying to avoid something in front, whereas simply keeping distance and doing an emergency break would have been the correct course of action). A machine won't. A machine can be programmed to react as the best stock car pilot.

- we are speaking long term progress. wheel-less cars isn't something that is going to happen tomorrow or next week. It's also not only going to be produced by google alone (BMW, Volvo, MB, Tesla, ... all have plans toward automation). By the time wheel-less cars become common, there would be lots of other cars with varying degree of automation. In case of complex problems, the faulty vehicle (Truck whatever) might as well have bordcasted a warning around and all the autonomous cars might as wall have decided to follow the hint and move away to safety. When speaking about extreme far-out development of automation, think networks, not single individual. Otherwise you might sound as someone complaining that the loud motors of sports cars will scare all the horses pullings the carts around it.

- blackboxes can still give valuable information, programs in an autonomous car can still be updated. Even in the tragic case of an accident, all the remaining autonomous cars can be made better.
By the time wheel-less cars become popular, very probably it would be much safer to let computer handle everything than putting behind commands someone who might be over-confident, inexperienced, or plain stupid/drunk.

Slashdot Top Deals

We can predict everything, except the future.

Working...