I often think the existence of CSS can be seen as the strongest criticism of XML: when designing a language to store styling attributes for HTML, they used their own heirarchical format instead of another SGML-derivative.
Re:18F: CSS coding style guide
by felixgallo on Friday January 29, 2016 @08:03PM
(#10999913)
I think you overestimate the amount of considered, thoughtful reflection that went into creating HTML, CSS and JavaScript.
Re:18F: CSS coding style guide
by YngwieMalware on Friday January 29, 2016 @09:43PM
(#11000236)
And yet they have become useful far beyond their original intended design.
Re:18F: CSS coding style guide
by felixgallo on Saturday January 30, 2016 @12:21AM
(#11000650)
No. They have prevented aeons of progress. They are an unmitigated computing tire fire that future generations are going to curse us for.
Yeah, if just full-screen Java Applets had prevailed instead of web pages we would be much better off! Seriously, the html/css/js stack has its share of haphazard design, but it has shown to be much more robust and adaptable than any of the proposed "better-designed" alternatives.
Re:18F: CSS coding style guide
by YngwieMalware on Saturday January 30, 2016 @10:48AM
(#11002242)
Yeah I do wish I could see a bunch of unstyled, barely functional UX "designed" by engineers who have no understanding of interfaces or design.
Future generations? Current generations curse them right now :-).
Your hyperbole is truly as excellent as your dangling prepositions. I do so love the smartness with which you declare the end of society.
Re:18F: CSS coding style guide
by YngwieMalware on Saturday January 30, 2016 @10:27AM
(#11002138)
I and many other have careers because of them.
If it is such a problem for you, I would suggest coming up with actual solutions instead of the Grandpa Doom visionary "prediction" you've offered which is of no value.
Well, they've been used far beyond their original intended design, at least.
Re:18F: CSS coding style guide
by YngwieMalware on Saturday January 30, 2016 @10:29AM
(#11002149)
What exactly is not useful about using HTML and CSS to create web pages? The entire medium of the web to create applications is already far beyond the original intended design of the browser, etc. So what makes it so bad besides that some people, who seem to think they're pretty smart, have a lot of difficulty with it?
Re:18F: CSS coding style guide
by Mikhail_Edoshin on Sunday January 31, 2016 @01:47PM
(#11007419)
All of it? :)
It's neither a good rendering medium, nor a good language to describe the structure of the data.
Surely you must be joking about JS at least. The language was created in 10 days.
Re:18F: CSS coding style guide
by currysausage on Friday January 29, 2016 @09:01PM
(#11000133)
He writes "overestimate," not "underestimate" :)
Well CSS is older than XML. SGML was considered a (meta-)markup-language, i.e. a format for adding semantic info to human-readable text. It was never considered an universal data format. As an example DSSSL, the style sheet language of SGML, was not itself a SGML language, so it is clear the SGML community never considered SGML appropriate for all kinds of data. For that matter, DTD's are not in SGML language either.
XML was initially thought of as a simpler SGML, but when it took off it started to be used for all kinds of data including data which are not based on human-readable text at all. XML is fine for markup, but needlessly verbose and complex for non-markup languages.
Re:18F: CSS coding style guide
by Mikhail_Edoshin on Sunday January 31, 2016 @02:16PM
(#11007549)
I think you're mistaken about DTD, they were used in SGML. (As in XML they were optional.)
I was unclear. I meant DTD's are not an SGML language.
Re:18F: CSS coding style guide
by paulddraper on Saturday January 30, 2016 @09:49AM
(#11001953)
I think CSS is the strongest criticism of CSS.
Slightly off topic, I'm slightly bothered by the amount of trash talk CSS receives since it's pretty much the best language we've ever had to define interface styles, and it's only getting better. Maybe some of the rules about behavior are arguable, but by and large I've never met a design I couldn't get to work with some well-defined CSS.
And if you can't read nested CSS I can't imagine how you'd feel in the face of some heavy XML.