Slashdot Mirror


User: gnugie

gnugie's activity in the archive.

Stories
0
Comments
34
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 34

  1. Simple Advice on How Would You Handle a $1,000,000 Coding Error? · · Score: 2, Funny

    He should blame the requirements.

    There's always a mistake in the requirements.

  2. Not even close on Porn Beats Search Engines in Internet Traffic · · Score: 1

    I'd have to get a HELL of a lot more than the 50 Megabytes of spam I get daily to counter the pr0n.

  3. From Scratch? on Ken Brown Responds to His Critics · · Score: 2, Insightful

    Ken has a funny definition of "from scratch".

    I guess in Ken's mind, in order to bake a cake "from scratch", you couldn't use a cookbook to devise a recipe, would have to grow your own wheat, crush it into flour with your bare hands, add sugar from your own sugar beets, and bake it on a rock in the sun.

    Previously, I'd just thought him a shill. This is sheer idiocy.

  4. Re:What? What? What11!11?1 on Embedded RTOS Maker Raises Linux Security Issues · · Score: 3, Insightful

    OS dude's got the quote wrong:

    "It costs us $500 to $1,000 a line to review our source code. It would cost _us_ billions of dollars to review Linux."

    That's why he's losing business.

  5. Re:give us a break on Embedded RTOS Maker Raises Linux Security Issues · · Score: 2, Insightful

    IAWTP.

    If the Gov't requires the vendor to audit the code that stringently, why wouldn't they put the same requirement on the embedded Linux provider?

    In that case, it's the vendor's responsibility to audit to the gov't requirements. I'm going to seriously doubt it'll cost $500/line, but it should already be a part of the quote.

  6. Re:Liability on Smart Cars to Save Stupid Drivers? · · Score: 1

    In the States, the liability is one of the largest problems. In Europe and Japan, for the most part, the driver is still responsible for what the vehicle does.

    The methods discussed in the article exist mostly because of the liability. Monitors the driver's eyes or hands, and watching the road in front for obstacles are engineering problems that have been solved already (for the 99.9% cases, anyway).

    The REAL issue with this technology is how to use that information. You can't take over the vehicle, because then you're liable for the .1% cases, so you have to invent some way to convince the driver to take action.

    Sounds, lights, and vibrations are all that are left (unless you wanna try smell or taste).

  7. Re:What gets me... on SCO Changes Tune, Again: Linux Now Just a Riff on Unix · · Score: 1

    When being a decent human being is enough to put food on the table and a roof over my kid's heads, I'll work on it.

  8. Re:24Ghz link/chip or core speed? on Radar/Wireless Transmitter on a Chip · · Score: 1

    Measuring the size of the object isn't enough.

    If a car started braking over a cloud of pebbles, no one would use the features.

    Current radar-based cruise-control technologies have to do things like measure the targets, determine the speed (and direction) of the targets, and determine if the target is legitimate. Then, the system must determine when/how to throttle the engine and when/how to apply the brakes.

    Basically, the radar's the easy part.

    And it's not something that costs millions of dollars, either.

    And, of course, no

  9. Re:Collision aviodance on cars at last on Radar/Wireless Transmitter on a Chip · · Score: 5, Informative

    Both Cadillac and Jaguar sell vehicles with Radar-based Adaptive Cruise Control, which will brake for you if needed.

    Check out the Cadillac XLR.