News for hackers. Stuff that matters.
Re:Continuous Design and the NoPSD Movement by specialist on Tuesday July 02, 2013 @10:56PM (#5982176)
This is old, old territory. HTML's least offense is its syntax. XorNot just doesn't have the vocabulary (or desire) to rehash a settled debate.

Just to save some time, HTML+CSS+JS fuses, poorly:

1) page description / layout

2) appearance

3) interaction / animation

4) forms

5) content

6) metadata / markup

7) typography

8) vector art and raster images

You could probably throw in HTTP stuff, cookies, how much the DOM sucks, and multimedia too.

Sadly, bad as HTML is, there hasn't been anything better.

Re:Continuous Design and the NoPSD Movement by talmand on Wednesday July 03, 2013 @10:27AM (#5984708)
But you are clearly covering topics that XorNot did not mention. He specifically stated disliking the syntax and having to type it.

I would agree with you that over the years people have pushed features into HTML beyond what it was originally intended for, but that's not what's being discussed.

Re:Continuous Design and the NoPSD Movement by XorNot on Thursday July 04, 2013 @07:11AM (#5990090)
Simply put: <p>some text</p> involves more awkward use of the right-side of my keyboard then there's any need for it to.

Contrast to Jade where I would just go: p some text

and let the indentation sort out the DOM structure. It's simple, readable, and doesn't overuse a set of keys placed more or less to be used infrequently (the <> brackets). All this translates to more productivity.

CSS is different problems, but it still stems from being overly verbose (too many vendor tags to worry about) and lacking useful functions, interators etc. Basically CSS sans a preprocessor is just slow and clumsy to work in.