Can we stop bad-mouthing CSS in developer talks, please?

Re:Can we stop bad-mouthing CSS in developer talks, please? by petepete on Wednesday October 05, 2016 @06:36PM (#12648561)

> The joke here is that CSS is inadequate to fix that problem of overflowing text.

No, the joke is that in CSS the solution isn't always obvious and often takes multiple attempts (to a non-expert like me, anyway). Sometimes things you expect to work don't and you end up in the depths of Chrome Developer Tools trying to work out why.

I don't think people dismiss CSS as being inadequate, it's just occasionally difficult and frustrating.

[ Parent | on HN ]

Re:Can we stop bad-mouthing CSS in developer talks, please? by ethanbond on Wednesday October 05, 2016 @06:39PM (#12648578)

What language or even tool is the above comment not true for?

[ Parent | on HN ]

Re:Can we stop bad-mouthing CSS in developer talks, please? by petepete on Wednesday October 05, 2016 @06:43PM (#12648601)

Well, in other languages or tools you get a helpful error message, or you can add a break point or log output to a file.

In CSS, not so much. Edit, reload, review, repeat. I know it's not a fair comparison, but it's true.

[ Parent | on HN ]

Re:Can we stop bad-mouthing CSS in developer talks, please? by thoughtpalette on Wednesday October 05, 2016 @11:29PM (#12650038)

Linters are helping in many of these cases.

[ Parent | on HN ]

Re:Can we stop bad-mouthing CSS in developer talks, please? by coldtea on Wednesday October 05, 2016 @06:44PM (#12648610)

In the same magnitude as CSS? None.

[ Parent | on HN ]