{"id":41,"date":"2007-05-14T05:25:33","date_gmt":"2007-05-14T12:25:33","guid":{"rendered":"http:\/\/blog.mozilla.org\/axel\/2007\/05\/14\/re-platform\/"},"modified":"2007-05-17T13:22:33","modified_gmt":"2007-05-17T20:22:33","slug":"re-platform","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/axel\/2007\/05\/14\/re-platform\/","title":{"rendered":"Re: platform"},"content":{"rendered":"

Firstly, architectures with one platform give you grass on rails, not rubies. Opting for still-imagery here, take a look at the Amerika Bahnhof<\/a>. I pondered taking half a day off and take some pictures from Berlin’s Lehrter Bahnhof<\/a> (or, Hauptbahnhof). Anybody who’s been there knows that it’s a maze of platforms, aiming at different needs, operated by different parties (there are at least 3 different operators for local public transportation in Berlin). That doesn’t count all those independent parties running shops and restaurants.<\/p>\n

Mozilla is a train station, and it comes with a plethora of platforms. Platforms as in horizontal stuff to take off from<\/em>. NSPR, NSS, Gecko (undefined in all levels of –with[-out]-technology), libxul, xulrunner, toolkit applications. Those are platforms for programming. I’d call Firefox rather a platform for web experience, not strictly one for programming, I see non-programming values in Firefox that form a distinct kind of platform, like privacy, security, good defaults, user choice. Then there’s spreadfirefox, which is a platform to launch marketing projects. Not everything that is essential to a train station ecosystem is a platform, btw, and there are plenty of those in Mozilla, too.<\/p>\n

Despite the fact that it took me me only a few minutes to write down some punch words for some of our platforms, Mozilla doesn’t do a good job about defining which stuff we consider to be a platform or not. That doesn’t mean that platforms need to be done, or that MoCo has to commit to get them done. They may actually be as much of a Baustelle<\/a> as anything. Yet, defining them and giving them names makes them easier to find, and to fix, even. I consider the non-programming platforms vital for the train station ecosystem, too.<\/p>\n","protected":false},"excerpt":{"rendered":"

Firstly, architectures with one platform give you grass on rails, not rubies. Opting for still-imagery here, take a look at the Amerika Bahnhof. I pondered taking half a day off and take some pictures from Berlin’s Lehrter Bahnhof (or, Hauptbahnhof). Anybody who’s been there knows that it’s a maze of platforms, aiming at different needs, […]<\/p>\n","protected":false},"author":17,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/posts\/41"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/comments?post=41"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/posts\/41\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/media?parent=41"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/categories?post=41"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/axel\/wp-json\/wp\/v2\/tags?post=41"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}