Recently in Viewpoints Category

Vindictapart.

| No TrackBacks

Yesterday I made a post to my business weblog with some rough thoughts on the TypePad outage. I had some additional observations that didn't make it into that post I'm going to write up here. These are rhetorical questions that I find fascinating to look at.

Why does the blogosphere think Six Apart sucks so much? We all suck. I suck. You suck. Software sucks. For some reason though it seems Six Apart is at a different level when it comes to ridicule. Why is that? Even people that have never used their tools take pot shots at them. Granted they've made their fair share of mistakes. Take last week's outage for example. Om Malik reported that a number of other hosted applications suffered outages last week. WordPress.com was down for some time as was del.icio.us, gone for most of the weekend. All of these outages are unfortunate, if not annoying, yet you'd be hard pressed to find these others receiving a fraction of the rants that are aimed at Six Apart. The difference in intensity is pretty startling.

Why is the WordPress community so vocal, bordering on vindictive, when it comes to Six Apart? This might be related to my first question, but I've noticed that the WordPress community is pretty aggressive in kicking Six Apart when they're down. Take the comments in this post (the suggestions to use WordPress.com is a bit amusing given they had their own meltdown last week) and this post for example. Why is this? If you are a MT or TypePad user of any stature, make a post griping about your tool and see how many WordPress users show up in the comments. See how many other blog tool users show up. The difference is also pretty startling.

What's even more fascinating to me then all of this is that despite years of "MT|TypePad|Six Apart sucks" rhetoric the company still continues to grow and thrive in leading the market.

So what's the lesson to be learned here?

Nick Bradbury writes:

Bottom line: the imprecise RSS specification resulted in a lot of guess work, which complicated things for developers, end users and feed producers. The solution? We clarified the RSS spec.

The solution? We clarified the RSS spec. While problems with entity-encoded HTML haven't disappeared completely, in my experience they're far less common than they used to be (and when they do occur, we now have examples to point to).

And that's all that's needed here, too. Clarify the OPML spec, and we can skip another prolonged format battle.

Clearly RSS feeds have gotten much better, but I think the Feed Validator had a much greater impact on that clean-up then the clarification Nick sites. Don't forget RSS 1.0 and 0.9x feeds were equally as busted as the 2.0 version he points to.

Having had my fair share of frustration with both RSS and OPML and OPML's "spec" is far more ridiculous then RSS ever was and that is saying something. I have to wonder -- is it worth saving OPML? I'm not so sure. By default OPML is used as an import/export format by aggregators -- there was nothing else proposed and it just spread as the market for tools exploded. This isn't too dissimilar to how RSS grew. The difference here though is that OPML's use is quite limited in comparison to its intended scope. OPML was specified to be a general purpose outline format however it is only really used for representing blog rolls and it does that poorly. Without a real specification of the values, attributes or even the attributes case there are many variants of the OPML blogroll format in the wild. So is it "really" fixable if it were specified? Not without a lot of breakage really and you'd still need to be ready for all the crazy variants from the void left by the lack of a good specification.

I guess what I'm saying is it doesn't really matter whether it gets better specified or not. Best of luck who are taking it on. My view is that the toothpaste is out of the tube and OPML as a blog roll format will only be a bit player a best.

I'm much more interested and intriuged by XHTML outlines -- the microformat better known as XOXO. I've used it before in a few instances and its worked very well. (X)HTML's system of providing outlines has been around longer, is better specified and more widely supported in the grand scheme of Internet software that I have to wonder what does OPML provide that makes it better? What does specifying and developing another format buy us? I can't think of anything. The current universal support of import/export by aggregators is nothing to sneer at, but how hard would it be to convert current blog rolls to XOXO? Trivial. OPML blog rolls don't contain any more information per entry then the XHTML link tag. Which require more effort: fixing the spec and then all the OPML blog rolls or just converting to XOXO? I think its a tie. Which would provides the better footing going forward? I think clearly XHTML because you can do more now and its already here, well specified and well supported.

It's understandable why OPML is supported in aggregators and that that should continue to be exploited, however I just don't see furthering OPML for blog rolls. Let sleeping dogs lie. It's served it purpose. Lets not get trapped in past foibles and move on to new and better things.

UPDATE: Sam Ruby who I believe is the most patient and persistent person you'll ever find in technology has entered into the OPML conversation. The Feed Validator that he was instrumental in driving has OPML validation with a call for more tests. This I believe supports my assertion that his validator was more instrumental in cleaning up bad RSS then clarify the specification as Nick Bradbury wrote. So perhaps there is a bit more hope of a clean up then I had before.

OSCON Wrap-Up.

| No TrackBacks

It's been a week since OSCON ended and I'm just beginning to recover. Very interesting things abound.

The theme/tagline of this year's event was The Future is Open. Rumor is the runner-ups with The David Hennemeier Hanson Show and With Ruby on Rails! More on that in a bit though.

Ben Hammersley and I had quite a good turn out and response to our 45 Syndication Hacks in 45 minutes presentation. While we were in one of the smaller presentation room its was filled to capacity throughout. You dread presenting on the last day, last session because attendance is significantly diminished as everyone is burnt-out or running off to catch their flight. Ironically I seem to draw this dubious honor each time I present. Perhaps there is a secret password I'm forgetting to say. Nevertheless for those who are interested in our flying-by-the-seat-of-our-pants slides they are here.

I attended Brad Fitzpatrick's scalable Perl presentation. Quite an impressive setup they have developed. Some of the tools they've develop and released as open source – memcache and perlbal – look quite intriguing stuff I hope to take a look at soon. The mention of a forthcoming distribution, Data::ObjectDriver, caught my eye. As I suspected it sounds like an open source version of MT's data persistence layer with various high-end scalability functions built in. Six Apart founder Ben Trott discusses the module here. Looking forward to that modules release.

My sleeper pick was Yahoo's Michael Radwin's presentation on HTTP caching and cache busting. Highly useful information to anyone dealing with efficient distribution of content on the Web. Presentation hasn't been posted. My rough notes at the end of this post.

So Ruby on Rails and its creator David Hennemeier Hanson seemed to be everywhere at the conference. The good Mr. Hanson had 1 tutorial, 2 presentations and 1 keynote this year. Several other Ruby presentations were also on the bill and the discussion of many conversations heard through out the conference. There was even a Ruby on Rael sighting. The always insightful and humorous Danny O'Brien put it best when he noted that Ruby moved from being ignored to winning (thereby bypassing being laughed at and fighting) in about three weeks. I always worry when any thing gets hyped up into such a rich foamy lather because misuse and backlash is inevitable. Ruby on Rails does have a lot of nice things worth praise.

The thing I like most about Rails is the thinking and philosophy behind the framework. The idea of joy and aesthetics is a novel one that gets lost or forgotten. I once felt that type of joy from MT and know it really can make a difference.

The following are my rough notes I took from Extracting Rails from Basecamp and Secrets Behind Ruby on Rails.

Less people, more power
Less money, more value
Less resources, better use
Less time, better time

Prove that an application is worth building the big thing (scaling up) for it.

We built half a product instead of a half-ass product.

Develop less software.

Too much enterprise. Too much focus on 99.999% uptime. Too much 100 man shops.

Liberate the good ideas. Change the language. Change the context. Retain the core insights.

Call me shallow. I love beautiful code. Aesthetics. Joy.

On APIs: I'll know when I see it. You have to feel an API to make it fit. Guessing the future is for fortune tellers.

Why Open Source? For entirely selfish reasons. Make others do the work. Bask in the glow of being a giver. What's there to loose?

Fear obscurity. You need a network to reap the effects.

Passion is infectious. The baseline of excitement. A conversation of success.

Scaling a culture. Early influx can bend you out of shape. Release not so early, then often. Set a viral example of kindness.

Getting rid of XML situps. Use conventions.

 class Post < ActiveRecord::Base
    belongs_to  :weblog
    has_many    :comments
    has_one     :author, :class => Person
 end

No compilation. No deployment. No server restarts. No code generation.

Ruby: Introspection, Open classes, Execute code in class definitions.

Complete, integrated, and familiar stack. One language all the time.

The bucks stops here. We handle it all.

Responsible for the whole experience. Taking care of all the little things.

Flexibility is overrated. Its a bad notion. Trade flexibility for constraints are liberating.

Of all the Rails knock-offs being discussed, this last point, that flexibility (in frameworks) is overrated, seems to be the most crucial and most overlooked attribute. (Are you listening Catalyst team? This is what I meant.) Phil Windley rocks out flexibility being overrated here. I didn't get to attend the Rails tutorial, but Phil did.

Notes on Michael Radwin's HTTP Caching presentation:

 Cache Publishing and Busting.

 (Dynamic Content)

 Frequently 
     HTML

 Occasionally
     CSS
     JavaScript

 Rarely/Never
     Images
     Flash
     PDF

 (Static Content)

 Top 5 Techniques.

 Use Cache-Control: private for personal content
     For use with dynamic content. 
     HTTP 1.1 Caching anything by default
     In practice, most caches avoid anything with:
         Cache-Control/Pragma header
         Cookie/Set-Cokkie header
         WWW-authenticate/Authorization
         POST/PUT
         302/307
         SSL content

     Cache-Control: private

     Shared caches bad for shared content
     Private caches perfectly OK
     Avoid personalization leakage.

 Images Never Expire
     Dictate that images once published never change
         Set Expires header 10 years in the future
     Use news names for new versions
     Tradeoffs
         More difficult for designers
         Faster user experience, bandwidth savings

     mod_expires
     ExpiresActive on
     ExpiresByType image/gif A315360000 # 10 years
     ExpiresByType image/jpg A315360000

     mod_headers provides a HTTP 1.1 solution

     mod_images_never_expire - Never even hits the file system 
     when an if-Modified header is sent.

 Cookie-free TLD for static content
     A seperate domain name for your static content (like images) 
       cuts down on the size of the requests coming from a cookie 
       header being inserted in every request.
     Many proxies are more likely to not cache a file to avoid 
       personalized data leaks.

 Use Apache defaults for occasionally changing static content

 Use randon tags in URL for accurate hit metering or 
   very sensitive content.
     Convert public shared proxy caches into private caches
     Without breaking real private (browser) caches
     (Missed last point)

     (Missed more here.)
     Return 302 to highly cacheable images file
     Counts 302s as hits

     Does not require modifying HTTP headers
         No need for Pragma: no-cache or Expires
         Doesn't break the back button
     Browser history & visited-link highlighting
         Javascript timestamps/random numbers
             Easy to implement
             Breaks visited link highlighting
         Session or Persistent ID preserves history
             A little harder to implement

     User expectation: Back button works instantly
         Private caches normally enable this behavior
     Aggressive cache-busting breaks back button
         Server sends Pragma: no-cache or Expires in past
         Browser must re-visit server to re-fetch page
         Hitting network much slower than hitting disk
    (one more)

 Pro-Caching Techniques
 Cache-Control: max-age=<bignum>
 Expires: <10 years into future>
 Generate static content headers
     Content-Length
     Last-modified, ETag
 Avoid cgi-bin, cgi, "? in URLs
     Some proxies (e.g.Squid) won't cache
     Workaround: use PATH_INFO instead.

 Cache-busting Techniques
 Use POST instead of GET
 Use random strings and ? char in URL
 Omit Content-Length and Last-Modified
 Send explicit headers on Response
     Breaks back button
     Only as a last resort
         Cache-Control: max-age=0,no-cache,no-store
         Expires: PAST DATE
         Pragma: no-cache

 Books Web Caching and Replication (Addision Wesley)
 Web Caching (O'Reilly)

Limits can be fun and too many resources can be harmful.

Constraints drive innovation and forces focus. They are to be embraced, not removed. says David Heinemeier Hansson on the 37Signals weblog. To explain this he uses the decline of Star Wars movies as an example and quotes a comment from Slashdot:

No the problem is money. Lucas has way too much of it. Especially for the first film [New Hope] there was a severe budget crunch. They were limited in both money and time. I think this forces a film team to make decisions that in the long run are good for the film. If you have no boundaries, you are more likely to throw in little bits that really have no business being in the movie. If you are limited, you are forced to trim the fat and leave the good bits. With the prequels, Lucas had no limits. He effectively had infinite money and time in which to make these films. As a result he wasn’t forced to REALLY think about which parts worked to help the film and which didn’t.

Yeah, that about says it.

Tim Bray writes:

As noted previously Drupal had a little trouble, and the community rallied around: individuals to the tune of over $10,000 and my employer with a server. So, I note that to build out their infrastructure, Drupal is going to use the community donations to buy Dell boxes. Um, let’s see here; IBM and Sun invest in Open Source, big-time. HP’s there too. Dell... uh, Dell? Ecosystem? Community? There’s something wrong with this picture.

I suppose when you're Dell and your hardware is the epitome of low-cost commodity technology you can't afford to be generous. I have to say that Drupal's actions seems like an utter slap in the face that, after the generous donation Sun made, they did not give them any business and went with Dell. Seems rather tactless and unappreciative no matter what the price difference actually.

Nat Nails Rails.

| No TrackBacks

The sagely Nat Torkington gets to the crux of why Ruby on Rails is so hot.

Whether or not you think Rails is the bee's knees and the wasp's nipples, you have to admit that the 37 Signals crew are master marketers. In many ways, more amazing than the technology of Rails is the way these guys have created buzz and build a community by lowering barriers to entry.

I've been fascinated and inquisitive of this surge of buzz in the past few months surrounding Rails, the Ruby code framework the 37 signals team derived from their web applications. In fact, I just finished watching the movie Nat's post links to. It's quite impressive what they can do there and while Rails certain makes development more rapid and less repetitive, even more a bit more accessible, it still has some rather rough spots and geekery to it. I'm one to talk being a Perl guy. The Perl developer community as a whole has a lot to learn from Rails. (Sorry Catalyst team, it's pretty clear you're missing the point on Rails and have a long way to go.)

So while Rails biggest achievement may be its marketing, there is a lot of technology lessons to be learned and it should be seen as starting point rather than a convergence and a beginning rather than an end.

In his O'Reilly weblog post Safari Sucks Memory, Roger Weeks writes:

The killer problem that I just noticed today is that Safari positively EATS memory. I was working in Cacti, and noticed that my system had really slowed to a crawl. The browser window took forever to update, and I had a lot of disk activity. I fired up top and WHOA! I only have 2M of free RAM and the system is swapping like mad.

Safari was taking up 216M of RSIZE memory in top. That's half of my system total! Again, this is a single web site. I have a single window open, at this time displaying a list of 25 graphs which I was editing one at a time.

216M of RAM! What on earth are you doing to me, Apple?

Tell me about it. I had a similar experience and called Apple support before I noticed the memory sucking power of Safari. My Powerbook was burning up and absolutely crawling. This behavior was exactly how my last Powerbook before it died on me one New Years Eve.

I know I just need to switch to FireFox, but old habits die hard. I'm also a slut for esthetics which Safari still does better then FireFox.

Hopefully Safari 2 will do better when I finally get around to installing my Tiger upgrade that's been collecting dust.

Over the weekend I got to read and contemplate Jason Kottke's post A whole new internet? that got my special attention because it solicited a response post from Mena Trott taking the bait.

Jason touches a couple of areas I'm quite passionate about and have been investing a lot of thought lately. So much so, that I'm dividing these thoughts into two parts. This is the second post and address a few specific points as a long-time members of the MT community.

In my first post I focused on how a successful application's evolution changes innovation and its community dynamic particularly as business entity with investors and employees. Here I drill down on some particualr points as they related to Six Apart and the community I call myself a part of.

Kottke writes [those who] were [once] pushing the edges of web design are now focused on making software that generates revenue and aren't saying a whole lot about it. That's great for them, for Six Apart, their customers, and their partners, but it kinda sucks for the community as a whole.

Mena points out that perhaps one of the reasons why Six Apart seems so quiet to the core audience of bloggers these days is because Six Apart wants to reach an audience outside our own inner circle of webloggers (the early adopters).

Noting a recent presentation to non-profit organization she continues, Maybe this isn't the most exciting stuff if you've been following blogs for three or four or five years. And perhaps it isn't anything new for people who read Mena's Corner. However, for this audience, I was explaining a new world – one which I hope resulted in the creation of more weblogs from the non-profit realm.

I think this is an important and often overlooked point that I wanted to highlight as I've been guilty at times of the same sort of think Jason expressed.

Being a long time user of Movable Type and friend of Mena, Kottke pulls Six Apart in front and center as an example of his observations.

Consider Six Apart as an example of what I'm talking about. 6A is like a black hole for creative people. Folks who, a year or two ago, were among the leading voices in the discussion of how weblogs were changing our culture, were coding all sorts of useful plug-ins for Movable Type, or were pushing the edges of web design are now focused on making software that generates revenue and aren't saying a whole lot about it. (Sort of ironic that working for 6A kills the weblogs of their employees, isn't it?) That's great for them, for Six Apart, their customers, and their partners, but it kinda sucks for the community as a whole.

Mena replies....

I don't buy the idea that most companies are creatively stifling their employees. While it may be true for some companies, I think it's far more likely that, as you say, people with jobs are really, really busy. Frankly, I know that when my heaviest periods of blogging came when I was unemployed or not feeling fulfilled at work.

I agree. The major of my posts came whilst unemployed and looking for employment. My habit sank dramatically once I took matters into my own hands and started my consultancy. I can commiserate with Mena's views.

I think Kottke referring to Six Apart as a black hole for creative people is not entirely accurate. I don't see Six Apart sucking the creativity and skill out of its employees. I think there is a great deal of creativity going on everyday inside the company. What I do think is that it rarely escapes the company's inner walls and, when it does, not enough is really made about it. This is were the black hole analogy may hold up in their case.

For companies like Six Apart, I think its too their benefit for the creativity to be as outward facing as possible to the point that they should actively seek ways to promote and foster it.

People often misconstrue my motivations for not posting as frequently as I should. During the course of the day I'll get into a conversation about some hot topic and decide that I'll want to devote a Mena's Corner post to the matter. But, the fact is, I'll get pulled into a meeting about an upcoming business trip, will have to catch up on the email that builds up in my inbox, will need to participate in a meeting about future versions of our various products or will be called to handle the sort of situations that arise when you're an executive of a growing company and you're intent on fighting the good fight.

I can understand were Mena is coming from here and know it too well having been a manager in an Internet upstart myself. Still as a blogging tools company with a very active and vocal customer base that looks to them for leadership, this should be a requirement of some individual's jobs. (This is not just aimed at Mena) If they don't blog something they aren't doing their job regardless of what else is going on. If they never have the time or energy, then their workload or perhaps even the company culture needs to be re-examined and adjusted.

As I company half the size Six Apart ever was its advice I practice myself. (Now being such a time.) It is a struggled, but its one I hold dear to what I do for a living. Its rather worrisome that Six Apart seemingly doesn't.

Transparency is wonderful and we're constantly struggling about how much information we want to reveal. Today, in fact, we had a follow-up meeting about the release of Movable Type 3.16 and Shelley (one of our technical support wizards) raised the important point of finding the right balance of revealing future features to our customers and explaining to them when a certain bug will be fixed.

Like I said, it's a constant struggle. And, when you're competing with big guys like Microsoft, Yahoo and Google, I think we'd err on the side of opacity if keeping our product plan for 2005 closely guarded meant giving us an edge of these giants.

I'm not sure it is giving 6A an edge. I'd argue its holding them back and not captializing on what they've built.

For a blogging tools company this seems rather backwards and one I wish they'd reconsider and err on the side of disclosing too much. I see it as being crucial to their existing community and continued success against the big guys.

As a relatively small and nimble company that is focus on one space as opposed to the big guys, I would expect Six Apart to be able to move more quickly and innovate faster. If they can't, then they have bigger problems then a competitor potentially stealing an idea.

Mena asks, So then the question is: What do people want us to reveal?

Just let us know you are listening, thinking about it or have a plan to roughly were you are going with it. A wonderful case in point is the very post from Mena I am commenting on now.

Seems WordPress is reliving some of what it was like to be Six Apart around May of last year. Funny since many of its community where the chief antagonists then. Quite frankly I think they are getting off easy considering their offense is far more unethical and dishonorable then anything Six Apart ever did.

Andy Baio reports:

Wordpress is a very popular open-source blogging software package, with a great official website maintained by Matt Mullenweg, its founding developer. I discovered last week that since early February, he's been quietly hosting at least 120,000 168,000 articles on their website. These articles are designed specifically to game the Google Adwords program, written by a third-party about high-cost advertising keywords like asbestos, mesothelioma, insurance, debt consolidation, diabetes, and mortgages.

Essentially, as I read the explanations to these actions in the ensuing comments, WordPress is hard up for cash to fund the project and was quietly taking money from a company trying to Internet trash into cash. Baio caught their hands in the cookie jar.

Many are calling it spam and others a scam. I'll just say its quite shady and a damn shame that this will mar the reputation of a project. Developers deserve to eat, but there are many many more ethical and honorable means.

I find it highly ironic that it was some of the WordPress community's most prominent and active members that were so blatantly opportunistic and criticized SixApart for trying to charge for their work (which is far more ethical and straight-forward then what happened in the WordPress camp) in the name of open source and freedom.

Not that Six Apart's execution was perfect. It had a lot to be desired and I said plenty on that. I'm not saying open source is bad and commercial software rules either. What I am saying is that I think there needs to be more consideration, understanding and balance to the economics of software development and how a highly successful project may not become victims of its own success.

I find it rather odd that the court of public opinion (and we know how large and vocal that court is in the blogosphere) has been seemingly less concerned about this infraction. What is the community saying? That open source by any means supersedes ethics and class?

Matt Mullenweg is unluckily (or is that luckily?) on holiday in Italy. However Jonas Luster, the first employee of the Wordpress Foundation, posted a response to the news and particularly notes Jason Kottke chiming in on the post. This quote was quite a kicker:

WordPress development is expensive. Start with a server and hosting, add Ping-O-Matic’s needs (PoM is the default for most WordPress and Drupal installs, today, and a large number of MovableType blogs) go on to figure that some of the developers have dedicated a seizable amount of their time to this effort, and you see where money might be needed.

It might not occur to Kottke, but maybe Matt felt that without some financial assistance, WordPress could not be sustained as a free project (in every meaning of the word), and realized that donations won’t cut it.

There is some news! Does this mean Six Apart is not the second coming of Microsoft after all? That they kind of knew what they were doing and were only being realistic?

Live by the sword. Die by the sword. I can only think that Matt can only have a new found appreciation for what Six Apart was trying to do in May 2004.

I received an email message from Bob Parsons President and Founder of Go Daddy that was sent to all of its customers today. It begins:

Today I have the unfortunate responsibility of informing you that there has been a decision made by bureaucrats of a Federal agency that takes away your right to privacy as guaranteed by the United States Constitution.

Well this only confirms what I suspected from their recent trashy Super Bowl ad campaign – they aren't exactly the brightest company around. If my memory from my American History classes serves me correctly, there is NO guarantee to privacy in the constitution. A quick search of its text confirms that the word privacy isn't mentioned let alone guaranteed. Whether the framers of the Constitution never could have imagined the issue could become what it is today or it's a Fox Mulder-esque conspiracy doesn't matter.

Its not like I'm for invasion of privacy – I'm quite opposed to it and think it needs to be taken more seriously by our leaders. Its just that I like having my facts straight in an attempt to sounding credible and intelligent. Perhaps some Go Daddy staffer can show the good Mr Parsons how to use Google before he gets in a snit like this one and lashes out without thinking.

About this Archive

This page is a archive of recent entries in the Viewpoints category.

Syndication is the previous category.

Web Developments is the next category.

Find recent content on the main index or look in the archives to find all content.

Powered by Movable Type 4.21-en