The Blogging DeadBlagofaire from xkcdReliable sources have finally confirmed that the blog is dead 1. According to Jason Kottke, . People seemed to be giving up on blogging and moving on to bigger and better things. Twittering (is that right?), Facebooking, Instagramming (one ‘m’ or two?), and Google+ing seem to be the hip-thing to do in 2014.So let’s look back and pay our last respects to the memory of Blogging.So what is blogging?I don’t know. I honestly don’t know.Blogging seems to mean different things to different people. Wikipedia, the modern sum of all human knowledge (no?), has an entry on Blog which nicely represents the state of affairs. The introduction describes a blog as a website with basically every feature or adjective under the sun.Blogs can be written by individuals, small teams, large corporations and think tanks. They can be about a single subject, a diverse range of topics, personal events and thoughts, brand advertising, or feature updates about a service or product. They can contain text, photographs, video, animations and illustrations. They can have comments and discussion by readers, or not. Blogging is not restricted by the kind of authors or type of content.So what is blogging?Jason seems to distinguish the ‘blog format’, the reverse-chronological stream of posts that blogs traditionally have. Even though most blogs use the stream format to present a list of posts, this is a UI decision. It works nicely for some kinds of content—periodic photography posts (Street Photography by Sagi Kortler, Streets of Athens by StamatisGR), personal diary, product/service updates (Gridset Blog, Building Feedly). I don’t think the stream works for sites with a lot of eclectic topics; I don’t really like the stream nature of the archives of this site, but I don’t have any better ideas yet (suggestions welcome!). Blogging is certainly not restricted to the time-stream format 2.So what is blogging?Is blogging just writing?For a long time blogging was a derogative for writing on Web. If you wrote on the Web, you were a blogger, not a ‘real’ writer; it was a blog post, not a ‘real’ article; it was blogging, not ‘real’ journalism 3. Blogging was, simply put, bad writing.I hope that in 2013, it is clear that this was an asinine point of view. This type of blind bigotry against content just because it lives in a different medium is still rampant (comics vs. real literature, anyone?); but it seems we have finally accepted content on the Web as a legitimate form of writing.A book is no longer considered bad just because it is digital or on the Web 4. Comics on the Web have received wide acceptance. The success of House of Cards has finally shattered the perception that good drama can exist only on film and television 5. Lot of mainstream magazines and newspapers are now online. Many scientists write blogs about their research 6.Good content is good content, regardless of the medium. The Web is a global, open, accessible, flexible medium for writing content; and writing on the Web is not bad writing. Blogging is not a dirty word anymore.So what is blogging?Blogging is, simply put, writing on the Web. Blogging is not some special exotic activity that suddenly everyone gave upon (planking?), it is just writing on the Web. People have been writing on the Web long before 1997 (the birth year that Jason put on the Blog’s epitaph).1997 was around when web-publishing tools became accessible to the not-so-technical crowd. Everyone and their mother started writing on the Web, and called it a ‘blog’; a portmanteau of web and log. Later as people realised that blogging was not just about choosing a peppy website name, a snazzy visual theme and cool widgets; and that you actually had to write good, interesting content, most people gave up. The blogging fad died, slowly and painfully, exactly because people realised that blogging was about writing—and that it demanded hard work, lots of thought, sometimes multiple edits, just like ‘real’ writing. Most people who had jumped on the blog bandwagon were simply not prepared to do this work. It is much easier to follow on Twitter, ‘like’ on Facebook, reshare on Google+, than it is to create and write interesting content yourself. We have become passive followers rather than active creators.The people who stayed with active writing either, enjoyed the process (like me) or had been writing on the Web before ‘blogging’ became the it-thing. In fact, a lot of these folks no longer refer to their writing as blogs. Mark Boulton, Craig Mod, Jeremy Keith have journals, while Randall Munroe has a xkcd blag. Jeffrey Zeldman prefers to just call it a website!Of silos and walled gardensJason also seems to use the word blogging to distinguish writing on your own website from writing on silos (Facebook, Tumblr, Medium, Google+… ).The tightly-integrated walled garden that these silos provide is very, very tempting compared to the wild, anything-goes, shoot-from-the-hip nature of the open Web. If you write on these silos you are given easy access to a large audience along with plenty of easy-to-use tools for sharing. But, you also miss out on the people who don’t live in your particular walled-garden. Should you post multiple copies of your content on every silo? Should you update all of them and keep them current?The most problematic aspect of this is that there are only copies, no original! If in the future someone wants to read your content, in which silo should they look for the best representation?Another issue I have is conformity. Every tweet, post on Facebook looks and feels exactly the same. Medium, for instance, seems to exert a lot of control on how its articles look. While it helps to exert some quality control, this makes the platform very restrictive 7.What happens when one of these silos shuts down? Imagine if every time a popular book publisher closed down, every copy of all the books they ever published just disappeared. What a disaster! That is the situation with writing on silos. Sure, they might give you a backup copy of all your posts, but then you’d republish them on another silo and the cycle begins anew. It is much better to publish on your own site as the canonical version and syndicate copies elsewhere aka POSSE.In this sense, the blog isn’t dead. It is just sleeping or the blog might be dying, but the web’s about to fight back.ReawakeningBlogging is not a form, not a style, not a UI format, not a medium. It is a made-up buzzword like Web2.0 or web-app 8. Blogging, the buzzword might very well have lived from 1997-2013. As for writing on the Web, it has existed as long as the Web has, and will continue to do so.As of today, people are increasingly turning to walled-garden silos to host their content. If the death of blogging means the end of a fad, of a buzzword, of bad writing then I am all for it. If, on the other hand it means the end of original writing on the Web, or writing solely on silos, I really hope ‘blogging’ rises back from the dead to haunt us.In any case, let’s not ‘blog’, let’s just write—on our own personal place on the Web.Notes & ReferencesMore on ‘Blogs being dead’: The blog is dead, long live the blog and R.I.P. The Blog, 1997-2013 by Jason Kottke.The Death of the Blog, Again, Again by John Scalzi.The blog isn’t dead. It is just sleeping. by Colin Devroe.The blog might be dying, but the web’s about to fight back by Ben Werdmuller.This is a website by Jeffrey Zeldman.Blogging and UI: Weblog Weirdness by Eric Meyer.Blog Interface Design 2.0 by Luke Wroblewski.Blogging and journalism: Is Blogging journalism? by Paul Andrews.Blogging vs. Journalism: The Ongoing Debate by Jacob Friedman.the transition to digital journalism by Paul Grabowicz.Books on the Web: The Feynman Lectures on PhysicsButterick’s Practical TypographyThe James MacTaggart Memorial Lecture 2013—Kevin Spacey about the paradigm-shifting success of House of Cards.Blogs by scientists: What’s new by Terry Tao.Not Even Wrong by Peter Woit.One Universe at a Time by Brian Koberlein.Musings by Jacques Distler.Azimuth by John Baez.This restrictive post format is one of the main reasons I moved to own site. I would not be able to post a lot of things I have here, on Medium or Facebook or Google+.Webapp or not: By any other name and Defining the damn thang by Jeremy Keith.Poll Results: “Sites” vs “Apps” by Chris Coyier.
By any other name
I’m not a fan of false dichotomies. Chief among them on the web is the dichotomy between documents and applications, or more broadly, “websites vs. web apps”:
Remember when we were all publishing documents on the web, but then there was that all-changing event and then we all started making web apps instead? No? Me neither. In fact, I have yet to hear a definition of what exactly constitutes a web app.
I’ve heard plenty of descriptions of web apps; there are many, many facets that could be used to describe a web app …but no hard’n’fast definitions.
One pithy observation is that “a website has an RSS feed; a web app has an API.” I like that. It’s cute. But it’s also entirely inaccurate. And it doesn’t actually help nail down what a web app actually is.
Like obscenity and brunch, web apps can be described but not defined.
I think that Jake gets close by describing sites as either “get stuff” (look stuff up) or “do stuff”. But even that distinction isn’t clear. Many sites morph from one into the other. Is Wikipedia a website up until the point that I start editing an article? Are Twitter and Pinterest websites while I’m browsing through them but then flip into being web apps the moment that I post something?
I think there’s a much more fundamental question here than simply “what’s the difference between a website and a web app?” That more fundamental question is…
Why do you want to make that distinction? What benefit do you gain by arbitrarily dividing the entire web into two classes?
In the case of “web app”, I’m genuinely curious to find out why so many designers, developers, and product owners are so keen to use the label. Perhaps it’s simply fashion. Perhaps “website” just sounds old-fashioned, and “web app” lends your product a more up-to-date, zingy feeling on par with the native apps available from the carefully-curated walled gardens of app stores.
That’s a good point. A lot of tools, frameworks, and libraries pitch themselves as being intended for web apps even though they might be equally useful for good ol’-fashioned websites.
In my experience, there’s an all-too-common reason why designers, developers, and product owners are eager to self-identify as the builders of web apps. It gives them a “get out of jail free” card. All the best practices that they’d apply to websites get thrown by the wayside. Progressive enhancement? Accessibility? Semantic markup? “Oh, we’d love to that, but this is a web app, you see… that just doesn’t apply to us.”
I’m getting pretty fed up with it. I find myself grinding my teeth when I hear the term “web app” used without qualification.
We need a more inclusive term that covers both sites and apps on the web. I propose we use the word “thang.”
“Check out this web thang I’m working on.”
“Have you seen this great web thang?”
“What’s that?” “It’s a web thang.”
@adactio A near universal understanding that’s hard to define. Much like using the words “brunch” and “obscenity.” ;-)
@halfnibble But why?
@ScottKellum bit like saying “they’re all just fruit, so bananas and apples seem like needless differentiation.”
@adactio My frustration with “just use progressive enhancement” is that it is currently a lot more complex. There is no prior art …
@eoinkelly I don’t recall saying “just”.