HTML5 Brief: in one paragraph
alexkessinger.net
alexkessinger.net
The paragraph's construction makes it hard for the reader to know what the main point is. At the beginning of the paragraph, I was lead to believe that the topic of the paragraph was the lineage and evolution of HTML5 and its emergence from a previous failure. Halfway through, the topic shifts ("Implicitly,") to discuss the implications of the technology. In the third half, it seeks to get to a "bottom line," which seems to be "you should care about HTML5."
The lack of hyperlinks and references has several knock-on effects. The first is that claims made ("Some dismiss") smell like straw man arguments or like hyperbolic statements ("there will be no more versions of html"). Another effect is that the reader is left with no way to learn more, making this a pretty shocking example of the failure to use hypertext (ironically, to discuss hypertext markup technology).
Some recommendations: (1) Print out the paragraph, take a pen, and start crossing things out. Seek to reduce the number of words. (2) Read your work out loud, as you would read a book to a child. Not as you would talk to a buddy over a beer. (3) Review some books on clear writing.
Some people might wonder if I actually tried to edit, I did; this isn't me being lazy. So, feedback like this is helpful. Well, not linking to source material that is lazy.
I went to college, 4 years, in a program that had a fair amount of writing. I never thought I was a good writer, but I never got a good take down like this. Even from my teachers, I wonder if they just saw it as a lost cause.
Anyways, thanks.
I try to self-edit and, I can offer a suggestion from my own experience. I strongly suggest using a pen on a paper copy. This takes you out of the context in which you originally wrote the work-- your computer and keyboard. You can step away from your desk and go somewhere with a different context. A library, coffee shop, or outside under a tree are good places to rethink and rewrite.
And finally, I hope we'll see a revised version of your HTML5 paragraph-- you've clearly hit on an idea appealing to HN readers...
Alot of successful writing is in clear thinking (not being overly emotional at the moment helps immensely), then paring down of thoughts, _then_ writing, and then finally (and most importantly) editing. I always find saving a draft and sleeping on it before reading it back to yourself prior to sending/saving/publishing often helps.
Original: But who decides where the paragraph breaks go?
Edit:
okay well the above comentor obviously wins, but my point was that their is no compiler for english that can point out my syntax errors, and that we each develop a sense of english, and rules are fluid, and can be broken.
But your "paragraph" is even harder to define as there isn't any real fluidity to it, it seems more like thoughts here and there in short sentences with little to zero continuation.
I don't want to turn you off from writing and you should just keep on going in order to improve (no matter what people say), however learning from authors and books can also help along the way.
That being said, I think this is a good attempt to encapsulate HTML5 into a short statement (which should, as others have pointed out, really be broken up into multiple paragraphs). I'm not so sure it is a good encapsulation; but certainly a good attempt.
(In the same spirit: The semicolon in your final sentence should be a comma. But it doesn't affect my judgment of you one way or the other. ;) )
Thank you though, this is going to go in my list of question to ask my self while editing; does this feel like it could be in a middle school book report?
1. Keep it simple 2. Avoid howlers
Give 'Politics and the English Language' another read and scan the style guide of your favourite major newspaper or periodical. Check spelling. Check basic style (look up 'run on sentence' in a style guide and see what it says about what you wrote in your comment). Check if you're making sense (ask yourself, what sort of games do dodos play? does text 'feel' or 'read' or 'sound'? etc). If you want a use a metaphor, simile, idiom or common expression, triple check, look it up, verify it means what you think it means and consider 1. again. And that's it - simple, makes sense and has no howlers takes you into the stratosphere of online writing. You can decide whether you're interested in getting to orbit from there.
Billion dollar companies are making HTML5 a second class citizen to their own app platforms.
HTML5 can do nice things that hackers can currently post on their blogs in the hope that, if they are first and loud, eventually someone big will come calling and their developer dreams will come true. HTML5 is a nice thing to research for the mid-to-long term because in the real world the percentage of users that hit the site my job relies on that use IE6+7+8 is over 85% and that will not change any time soon. HTML5 demos do look pretty though so kudos on those but don't get carried away.
Why does HTML5 make "Objective-C folk" sad?
Obviously, Objective-C means Apple, and Apple's total control of their platforms might be thwarted by the kind of functionality enabled by HTML5. However, that does not seem to have anything to do with Objective-C per se.
Does it?
HTML5 is a buzzword like AJAX and Web2.0 that encapsulates the most exciting improvements to the web platform in the past and next few years.
AJAX originally meant (as its name implies) the use of XMLHttpRequest to asynchronously load xml data from a server. However, it quickly became a buzz word that meant increased interactively on a web page outside of the page reload. HTML5 has similarly evolved from describing a limited set of new standards to describe a new way of building highly interactive, desktop-like web applications and encompasses a whole host of W3C standards, recommendations and working drafts.
For some evidence that this expanded definition has become the norm, take a look at the HTML5 Test [2], which has been linked here several times. While not anything official, only a handful of the features tested are actually part of the HTML 5 spec.
[1] http://www.w3.org/TR/2010/WD-html5-20100624/ [2] http://html5test.com/
As Chris Wilson insightfully put it:
> HTML5 is now a brand, more than it is a specification. There are a variety of reasons for that, and a variety of persons “responsible” for that confusion, but the ship has sailed.
See also:
http://www.zeldman.com/2010/08/01/html5-test/
http://jeffcroft.com/blog/2010/aug/02/term-html5/
http://blog.codinginparadise.org/2010/06/why-im-going-to-kee...
We had that discussion with AJAX in the past. The one on the side of strict interpretation of the acronym failed. They'll fail again if they try to fight this one.