Become a fan of Slashdot on Facebook


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:The chilling thing about Ted Unangst's analysis (Score 1) 301

If 2), then it was deliberate, and the tinfoil-hat crowd is right for once.

Well, it would be one very inefficient way of introducing a backdoor. The custom allocator stuff in OpenSSL is very old, but the heartbleed bug is quite recent, so someone would have had to plant a backdoor-seed if you will and then wait for many years for that tree to grow fruits. Could be done, but it doesn't sound likely.

Comment Re:brighter? (Score 2) 376

The control system in my car reacts to bumps in the road, and turns the beams in the direction the car is turning.

This is what car manufacturers claim, but it's nowhere near true. The typical slewing time for the optics looks to be about 0.5 seconds from "standard" to "dipped", and that's way too slow for reacting to bumps/potholes when you're going faster than 30. I regularly get blinded by Audis, BMWs and Volvos with factory HIDs, but Mitsubishi seems to be worst. It could perhaps be that they are just worst at controlling chromatic abberations (since blue light blinds you more).

Comment Re:brighter? (Score 1) 376

I sincerely doubt that is true. In Norway (which is not in the EU but strives to comply with EU regulations as far as cars are concerned) the limit has been in lumens for almost ten years. It's commonly called "E-marking" which is lumens and directionality combined and dumbed down for the regular person. Ordinary (non-HID) high beams are typically 12.5 points each, good external pencil beams are 40 points each, and you're at most allowed to have 100 points active simultaneously.

Comment'll be able to scream, 'fire the lasers!'" (Score 1) 376

There is no way these could be "better" than existing solutions, at least not for high beams. There are stringent restrictions on how much light you are allowed to emit in which directions, and if you've bought some $400 Hella Rallye Compact's you're touching that limit no matter how bad your stock headlights are. The only usefulness here is that BMW will perhaps be able to make more exotic looking headlights.

Comment Re:GCC isn't an IDE, Codebench source is free (Score 1) 1098

Well, maybe because it's the strictest checking compiler you can get for Fortran? It certainly has helped me find bugs that gfortran, ifort and other have missed. You seem to be unaware of the fact that despite gfortran being free and quite good, there are at least five (that I can remember without googling) commercial Fortran compilers available today, e.g. from Nvidia/PGI and from Intel, that are quite popular in the scientific community.

Comment Re:stretching indeed. Recommending != selling (Score 1) 1098

Well, yes and no. Their product is by definition useless without a C compiler. Many (most?) people will use what's recommended, so many (most) people are using nagfor with gcc. A Core i7, on the other hand, works fine without a C compiler of any sort (as long as you only run precompiled binaries, which is true for (definitely this time) most people). But I see your point.

Comment Re:GCC isn't an IDE, Codebench source is free (Score 1) 1098

I'll give you an actual (but perhaps a little stretching-the-rules) example though:
NAG's Fortran compiler. It costs money. It's a Fortran-to-C compiler, and they recommend gcc if you don't have any other preferences. To me (as a compiler user) it's not a great difference if they make a Fortran-to-C compiler where I must provide the C compiler, or if they just shipped a C compiler and did the translation "in secret".

Comment Re:Oh yes (Score 1) 459

Really? To what end?

Well, why not? I found my right-hand little finger was cramping often. Coul be 'cause I use an "ergonomic" keyboard, which is quite good except the slightly bad position of the BackSpace key.

I see you've bound it to the Compose Key. That's utterly useless to me, since I very rarely write non-ascii characters (with the exception of æøå, and those I have dedicated keys for). When I want to write greek/fraktur/whatever, I write
$\alpha \to \infty \implies \sum_0^{\infty} n = -\frac{1}{12}$ etc. and then have the rendering engine (LaTeX) take care of it.

Slashdot Top Deals

backups: always in season, never out of style.