Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Re:Open source failed (Score 2) 447

You're likely to get modded Troll; but this really does remind me a bit of Ford vs. Toyota. For years Ford was fixed in peoples minds as the exploding Pinto company, and Toyota was high quality. Now Toyota isn't what it used to be, and Ford is better... but neither is perfect.

If nothing else this is a good argument against monoculture. We have different systems with different bugs, so it's not a total loss. If the market shares were evenly distributed among 10 different vendors, the black-hat task would be even harder, their impact of success that much less.

Comment Re:for a library... (Score 1) 447

All these higher level virtual machines and interpreters are ultimately written in C

And C runs on top of a processor. Intel FPU bug, anyone? IIRC, there were also some suspicions regarding hardware RNGs possibly being back-doored.

There are no silver-bullets, and a corollary to that is that there isn't just one monster you have to kill.

Comment Re:Consider the GDP (Score 2) 351

Are we going to train them to write PHP

Improv. GO!

... yes, because there aren't enough qualified people here, get them H1B ASAP.

... Backward tribes already use PHP.

... Many of them can only count to 3, so... oh, no problem. Carry on.

... for FacePaintBook?

OK, that's all I've got. Thanks for the setup.

Comment Re:Yet again C bites us in the ass (Score 2) 303

Yes, bounds checking is a hassle in C but throwing out the whole language isn't necessary. We could default to smart pointers and add a new type qualifier for people who want the old behavior. Dangerous code would look like:

int unbound * foo=malloc(1024);

It might be required to have a compiler switch to avoid breaking ABIs that are expecting simple pointers. The bounded pointer would have to be a struct with a slim pointer and a size in it that gets updated whenever the pointer mutates, and raises a signal whenever you add or subtract too much or try to index outside of it. I'm just spintballing. I'm sure there are some detail devils but it doesn't seem impossible or even unworkable. It doesn't sound like an excuse to re-write everything. You could even do something like this as a non-standard extension RIGHT NOW.

For years people complained that C was actually slower than Fortran because of the aliasing problem, and we eventually got the restrict qualifier. So. Don't just dump the whole thing. Fix it.

Slashdot Top Deals

Without life, Biology itself would be impossible.

Working...