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


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:You can't have it both ways. (Score 1) 91

The markup you are looking for is H1/H2/H3/...

HTML has had those since the very start. The current crop of web browsers stink at how they display it: They could so very easily display a TOC based on the headings, and provide controls for navigating sections. They don't, but that's not the markup language's fault.

Comment Re:tabs4lyf (Score 1) 300

Why would you care? You can make your editor show whatever indent you like. Just tell it to display leading spaces double-wide or half-wide or whatever you want.

Your current editor may not have that feature, but it could have. As long as the format stored on disk uses spaces, then it is trivial to infer which indent was used. Emacs (and many other editors I'm sure) can do that part already. So even if spaces are used on disk, your editor UI could display it to you exactly as if tabs were used.

But it doesn't work the other way around: If tabs are stored on disk, then the information is just not there. You can't reliably guess the indent the previous author used. That's why the files stored on disk need to use spaces.

Comment Re:We don't need a new language (Score 2) 300

The next thing missing are animation actions

FTFY. If you go down that road, it'll never stop. There's always going to be one more feature that's missing, and with new features comes bugs, and with bugs come security holes.

At the end of the day, you need something that's Turing-equivalent, so you can recombine known features in new and interesting ways. I just hope CSS doesn't end up being that Turing-equivalent something.

Comment Re:Breakthroughs are NOT plannable projects (Score 1) 474

Actually breakthroughs were planned, 20 years ago. Everyone was used to CPU speed doubling every other year, so they planned accordingly, and that included pouring enough resources into R&D to make it happen. Because everyone knew that if they didn't, two years from now their product would be obsolete because someone else would have made a breakthrough.

Comment Re:Using SHA-1 in this day and age is just lazy (Score 1) 203

1. This is not a security issue.

Says Linus. As the saying goes, anyone can design a security system(*) that they themselves cannot break, but that doesn't mean others cannot. Linus is no exception to that rule.

All the mitigating factors he mentions are good points, and he's right that the sky isn't falling. But still, using SHA-1 in 2005 was a lazy choice, and it would have been nice to have seen a move to SHA-2 sometime in the following decade.

(*) I know people are saying that the SHA-1 checksum is not a security device, but that's a bit naive: It's a central part of a protocol for exchanging data over the internet. Whatever it was intended to be, it is in reality a central part of git security.

Comment Re:Whew! (Score 1) 516

Income inequality is an indirect, at best, and irrelevant at worst, measurement.

One cares about the average health, wealth, and longevity of a population.

Those are correlated. Equality is correlated with better health. Remarkably, that applies not only to average health, but to everyone's health: Even the rich are healthier where there's less inequality, despite being relatively poorer.

Slashdot Top Deals

"You need tender loving care once a week - so that I can slap you into shape." - Ellyn Mustard