Skip to main content

Lost Promise

What happened to the blogosphere? Why is the USENET dead? How did Yahoo and Google groups (listserv-like services) wither so quickly? Why is podcasting struggling?

The answers to some of the above questions are simple:

  • USENET was killed because ISPs feared being sued for the amount of illegal files being distributed via the newsgroups.
  • Groups and listservs died thanks to a mix of spam and inconvenient delivery methods. Who doesn't stuggle to manage a flood of email as it is, without mailing lists?
  • Forums require frequent visits, and the "loudest," most annoying members drive the curious and open-minded away. Forums are now for true believers… arguing about ideological purity.
  • Podcasts and music downloads have lost ground to streaming audio and audio-on-demand services. It's still "podcasting" in a form, but through larger services like iHeartRadio and TuneIn.

Blogging and forums are the saddest loss, to me, though I miss the USENET programming newsgroups, a lot.

I've been watching Medium and other blog sites struggle, despite seeming like good ideas. I dislike Facebook and the click-bait in my stream, but I dislike the Google+ layouts even more. Nobody I know uses Google+ and the Groups/Communities there and on Yahoo have fizzled.

Slashdot, my favorite website, has said traffic dropped precipitously over the last year. Tom's Hardware dropped, too, not even bothering to fix a broken iOS reader app.

Every Slashdot discussion on operating systems or programming descends into useless screaming. That was always a problem, but you could filter the idiots. It is now so bad you can't find the good technical arguments. Looking for information on Swift programming, Apple's new C#-like language, what I find instead of useful information is diatribes. The USENET groups on coding would have featured discussions of the compiler choices, why LLVM works well (or not), and what the implications are of optimistic parsing.

The coding blogs? Dead. The coding listservs? Spammed to death. The IRC forums? More bots…

Remember when the Internet was supposed to create and expand "community" or something? Instead, it has reinforced tribalism (ugh, lousy word) and cliques of like-minded ideologues, while the generalists and moderates walked away.

The good news is that for information I'm back to attending real, physical meetings with other programmers to learn about tech. We don't even bother to update the group websites anymore, though.

The fading value of online communities might lead to… real communities.

Of course, things could change in an instant. Facebook could revive discussion threads. A new alternative could emerge. Google+ could finally be made useful.

Whatever happens, I doubt we can predict how we will communicate and convert information into knowledge five years from now.

Comments

Popular posts from this blog

MarsEdit and Blogging

MarsEdit (Photo credit: Wikipedia ) Mailing posts to blogs, a practice I adopted in 2005, allows a blogger like me to store copies of draft posts within email. If Blogger , WordPress, or the blogging platform of the moment crashes or for some other reason eats my posts, at least I have the original drafts of most entries. I find having such a nicely organized archive convenient — much easier than remembering to archive posts from Blogger or WordPress to my computer. With this post, I am testing MarsEdit from Red Sweater Software based on recent reviews, including an overview on 9to5Mac . Composing posts an email offers a fast way to prepare draft blogs, but the email does not always work well if you want to include basic formatting, images, and links to online resources. Submitting to Blogger via Apple Mail often produced complex HTML with unnecessary font and paragraph formatting styles. Problems with rich text led me to convert blog entries to plaintext in Apple Mail

Learning to Program

Late last night I installed the update to Apple's OS X programming tool suite, Xcode 4. This summer, in my "free" time I intend to work my way through my old copy of Teach Yourself C and the several Objective-C books I own. While I do play with various languages and tools, from AppleScript to PHP, I've never managed to master Objective-C — which is something I want to do. As I've written several times, knowing simple coding techniques is a practical skill and one that helps learn problem solving strategies. Even my use of AppleScript and Visual Basic for Applications (VBA) on a regular basis helps remind me to tackle problems in distinct steps, with clear objectives from step to step. There are many free programming tools that students should be encouraged to try. On OS X, the first two tools I suggest to non-technical students are Automator and AppleScript. These tools allow you to automate tasks on OS X, similar to the batch files of DOS or the macros of Wor

Learning to Code: Comments Count

I like comments in computer programming source code. I've never been the programmer to claim, "My code doesn't need comments." Maybe it is because I've always worked on so many projects that I need comments  to remind me what I was thinking when I entered the source code into the text editor. Most programmers end up in a similar situation. They look at a function and wonder, "Why did I do it this way?" Tangent : I also like comments in my "human" writing projects. One of the sad consequences of moving to digital media is that we might lose all the little marginalia authors and editors leave on manuscript drafts. That thought, the desire to preserve my notes, is worthy of its own blog post — so watch for a post on writing software and notes. Here are my rules for comments: Source code files should begin with identifying comments and an update log. Functions, subroutines, and blocks of code should have at least one descriptive comment.