Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:semantic flush (Score 1) 307

i and b were deprecated in HTML4 in favor of em and strong, respectively.

HTML5's sections did nothing to cure div-itis. Now we're going to be afflicted with article-itis and section-itis as well.

HTML5 won out over XHTML2 because of better overall backwards compatibility, however HTML5 is full of incompatible details such as the dilution of h1.

CSS has nothing to do with this. Every element is supposed to impart a well-defined context to its content, regardless of presentation. That's what I meant by semantics. An h1 styled with 8pt text is still more important than a p styled with 72pt text. The "semantic web" was rooted in putting XML in everything, and died as hatred of XML rose.

As for the car analogy, I'm complaining about the badly designed new parts, reuse of obsolete parts, and generally poor build quality. The HTML5 spec doesn't express as firm a grasp of its content and concepts as previous versions. Never mind that it's been nine years in the making.

Comment Re:semantic flush (Score 1) 307

First, i and b will only ever be used as presentational elements, no matter how they get redefined... those zombies should still be in their graves. There's still no grouping element for dt and dd. Sectioning as defined in HTML5 is a mine field of malformed logic and self contradiction. They should have just made a h element that inherits its level based on context (similar to how li's inherit their bullet style from list depth), rather than "strongly suggesting" that h1 be used for every headline, which is not a backwards-compatible change to that element. Allowing unquoted attributes and arbitrarily deciding that some elements don't need to be closed is just fucking asinine.

Within an hour Hixie will appear to ask for bug reports be filed (which by now is just passive agression), or lay out some convoluted, ill-founded, self-referential logic (which won't hold a drop of water) to counter these points.

Comment Unlearn anything from Gawker (Score 1) 1191

I briefly looked at the beta home page. Briefly, because it felt very much like the Gawker redesign from a couple years ago that made those sites (I only really read Jalopnik) a jumbled, discordant, unnavigable mess. FWIW, Jalopnik is the only bookmark I've ever deleted from my bookmarks bar... that's how incensed I was about it.

Two main things:

  • Don't try to mash the newest three stories into a single picture collage. Every item on the homepage needs to have the blurb, period. Pictures are usually noise for most /. stories, and most of this audience will not tolerate it: you are not aimed at the average user.
  • If a story is going to have a picture masthead, put it between the headline and the blurb. Above the headline, the pictures lose most if not all context.

If Nick Denton had anything to do with this redesign, even casually or tangentially, please let us know so we can riot. That idiot has no idea what he's doing.

Comment Re:Welcome to how SSDs fail. (Score 2) 552

This describes several of the reasons why I will not buy an SSD any time in the near future. Sketchy reliability, indeterminate longevity, inexplicable data loss. Mirroring a turd just means you have multiple turds. I have a few 10+ year old DeskStar drives that I still use and have never given me problems.

Comment Re:$20B the value of Steve Ballmer leaving (Score 1) 357

What did Outlook ever do to you, anyway?

Nothing to me, as I've managed to completely avoid using it. That is, until I began implementing parts of the iCalendar and vCard RFCs. Outlook's support for these standards is per capita worse than HTML support in any version of IE. In a month I had managed to implement better recurrence rule support than Outlook ever had.

Slashdot Top Deals

"There is such a fine line between genius and stupidity." - David St. Hubbins, "Spinal Tap"

Working...