Is this thing on?

Subscribe to RSS feed

Posts tagged with "past"

CSS 2.1 Solid Soon?

, ,

XKCD recently published the future and found through a good number of Google searches that finishing up HTML5 would herald the demise of newspapers and the Third Coming of Christ.

Coincidentally the W3C declared that finally CSS 2.1 had reached Proposed Recommendation status, and surely, surely!, the end, in the form of CSS 2.1 as Recommendation, should be nigh. I recapped the story in an almost four year earlier entry, Cruelly Slow Slog, a slog that cruelly continued for four more years. 11 years of labour is not bad for what was intended as a quick fix.

Heaping on the irony, a new working draft of CSS3 Speech Module was published. While CSS 2.1 was bound to reach PR some day, the CSS3 Speech Module had been missing in action for seven years, if this module had been a person he would have been recorded as dead long time ago and his belongings spread among his inheritors.

Maybe it is time for me to revive the Audio module? While the Speech module is an aural equivalent to the Text module, how to style spoken text (generated by text to speech), there would be a use, arguably a greater one, for handling audio files. Audio is to speech as image is to rendered text. Properties of an audio module would be the likes of volume, balance, delay, speed, how to present the media in a given context.

In the intervening years HTML5 has happened, with dedicated audio and video elements. As is otherwise the case having more well-defined markup makes the case for styles easier, with the ability of everyone involved to adapt content to user circumstances, for audio as well as images.

Of course, given present form, Jesus Christ would have become a frequent flyer by the time such a module would reach Proposed Recommendation.

Veien til fremtiden

, , , ...

Into the bog

, , , ...

This entry was actually made, well conceptualised, back in early July when I wrote several entries on HTML5 and XHTML2. If I made it then it could be considered prophetic, though it would only show a Nostradamus-style prophetic ability ("there will become a war, and in that war some people will suffer badly"). I lost that opportunity, but if something is worth doing, it is worth doing very, very slowly. And trust me, there will become a war, and in that war some people will suffer badly.

Read more...

Bending or breaking the tree: Extensibility in HTML

, , , ...

A link to the past

HTML is the Hypertext Markup Language. Hyperlinks is what made HTML special. When I came to the HTML Working Group, shortly after the browser war was over, the feud of the day was with XLink 1.0, which quickly had become a Recommendation through a flawed process. The HTML group wasn't happy about it, as they didn't think the specification fulfilled its design goals.

XLink had a complex history, originally it was meant to be an Extensible Linking Language to complement the Extensible Markup Language (XML). The specification ended up creating a number of attributes in the XLink namespace, 'link:type', 'xlink:href', 'xlink:role', 'xlink:arcrole', 'xlink:title', 'xlink:show', 'xlink:actuate', 'xlink:label', 'xlink:from', 'xlink:to'. The idea was that any XML language needing hypermedia functionality would mix in the appropriate XLink attributes.

When I left the HTML Working Group a few years later XLink was forgotten, but the HTML working group had made a very similar collection of floating attributes for XHTML2, 'xhtml:href', 'xhtml:role', 'xhtml:src', 'xhtml:about' and so on. The idea now was that any XML language needing hypermedia functionality would mix in the appropriate XHTML2 attributes.

Read more...

HTML5 — XML's Stealth Weapon

, , , ...

Even after the death-of-XHTML2, syntax debate still dominates the day. Here is my contribution.

The XML story

In the beginning was SGML. There is a lot to be said about SGML so I won't. HTML was specified to be an application of SGML, but that never happened in practice. Among browsers Opera kept the pretence of supporting SGML for the longest time, causing us a lot of trouble because Opera behaved differently from every other browser. DocBook is another known SGML application, but in general SGML was no success.

About a decade ago a small group of people started a reformulation of the old SGML standard, First they did it outside of the W3C and later, when the success became apparent, within the W3C. The story of this simplified SGML, now known as XML, may be best told via the annotated XML, by Tim Bray, one of the principal authors. Essentially XML is angle brackets and a number of production rules on top of Unicode (for a fuller description see Comparison of SGML and XML).

Read more...

An XHTML 2 far

, , , ...

Before the weekend W3C announced that the XHTML2 Working Group would be discontinued. That hardly came as any surprise, and mixed with that feeling of relief and melancholy the death of a terminally ill patient may elicit. To me XHTML2 was the next HTML3, another ill-fated W3C spec discontinued at an early stage and superceded by a browser-supported spec, HTML 3.2. The difference was that I had an inside view of XHTML2.

Read more...

A little knowledge is a dangerous thing

, , ,

This was a comment on a New Scientist piece, Linking genes to geography could revive race myth.


The concept of human races that most of us have grown up with has been shown to be at best simplified or misleading and at worst completely false. That hasn't and won't make racism go away. Furthermore this racial theory we have inherited is founded on Victorian science, and an enlightened project to classify and make sense of the world as they knew it then. The racial theory we know is far better founded than the theories at their time, but that wasn't good enough.

Combined with the obvious question at the time, "Why are Europeans so apparently superior to other human beings?", this cause profound misery in the late 19th and the first half of the 20th century. The scientists did their best based on what they knew moved on based on new data. But the societies didn't as there will always be a generation gap between the two.

I think history might repeat itself. Phrenology and talking about the Mongoloid race is (mostly) a thing of our past, slowly so may the Victorian idea of race do as well. The question of today seems to be "Why are the East Asians so much better at making money than other human beings?" Based on the past we can expect racist attacks and theories both against and by ethnically East Asians.

Science has moved on, we don't talk of race any longer, we talk of populations. But when it comes to genetics we are no better informed than the Victorians were about anthropology. We are making our conclusions on very scant material. There will be something in it for everyone, and many of these will have an axe to grind. By carefully selecting data you can get material to support every wild idea you can find on the Internet.

Nothwithstanding "It is important to emphasise that there are no genetic variations exclusive to any racial group. Some are more common in certain populations, but their distribution does not align with social categories of race." the idea of race is too ingrained and too useful to go away.

And it isn't just about race. Say you have data that 30% in a population, such as a classroom or an office, are predisposed to obesity. How are the 30% or the 70% to react to this information? If you know you are predisposed, would you eat less, or will you eat more because you can't help it anyway? What if you are predisposed to being bad in math? Or to violent crime? What if it is the neighbour and the neighbour's kids?

And what if 15 years later scientist discover that you or your neighbour weren't predisposed for obesity or being bad in math or violent crime after all? How would your life have changed from living 15 years under false assumptions?

The 20th century just died after prolonged illness

, , , ...

Decadance

, ,

Some nights ago, at a pub in Žižkov that used to be called U smrku (The Pine), I was chatting with a friend while not listening seriously to the songs being played. I asked her what would be the ten most decadent songs in history, without really coming up with suggestions of my own.

I tentatively put up "Crazy frog" (Axel F) in position #8, but I am really not good with lists, particularly not with music lists. Maybe you can come up with some suggestions?

Leaving Opera

, , , ...

That should more properly be "having left Opera", as I am no longer an Opera employee, but that doesn't work as well as a title. There is nothing dramatic about the decision, and I think Opera is an excellent employer, but I had been at Opera for seven and a half years and that was long enough.

Much of my work at Opera has been with standards, and standards don't matter. Having standards does, but as long as they are reasonably sane it doesn't matter what they are. The latest standards debacle in Norway wasn't related to browsers but with office products, word processors and the like, with the competing standards called ODF and OOXML.

ODF is not a good standard. You can read through the entire spec and will find nothing clever there. Anything ODF can do HTML5 can do better. Add cursor position to HTML5 and it could have been called ODF 2.0. What it has going for it is the absence of bad. Microsoft makes good standards, much of the time. OOXML is not one of those times, what it is lacking is the absence of bad. Could it be fixed? Probably, but to me it isn't worth it.

As for Web standards I think it should be an optional for Opera. Opera should encourage the presence of standards, and follow them unless they are bad, but it shouldn't necessarily form them. Opera should do what makes its users happy.

Opera Mini makes me happy. It lets me do things I couldn't do before. This entry was intended to be typed in on Opera Mini while I was on the move, but in the end it was typed in on a PC. It wasn't written in Opera Mini because Opera Mini isn't data loss safe, without copy&paste or save I can easily lose what I write, and data loss does not make me happy.

Being unemployed makes me happy as well, for now anyway. It's been a long while since the last time, as the last few times I changed jobs I went directly from one to the next. It is almost the same elated feeling as being homeless. I haven't actually been homeless in the sense that I own one flat and rent another, but I have adapted to a mobile lifestyle and from time to time I've not known where I will spend the next night and that is a strong feeling of freedom (until nightfall) — I can go whereever I want. I have used to claim that the bag in my one hand is my office, containing my laptop and other work stuff, and the bag in my other hand is my home, containing clothes and other private stuff. For now I can move with one bag less.

The evolution of language

, , , ...

There have been many language threads and digressions; I should know, I have participated in most of them. Maybe it's time to start talking about talking: What is language, where did it come from and for what reason? How do languages compete, cooperate, coopt each other? Where are they going? Is one language better than another? What about dialects, sociolects, idiolects, jargon?

Follow the discussion here

The Year in Browsing: The Little Engine That Could

, ,

By the end of last year one long-standing competitor to Opera ceased to develop its browsing engine. No, I am not thinking of Netscape, that browser was dead when it was bought by AOL, but an old Opera favourite, iCab. From now on iCab will use WebKit as the engine, in effect turning it into a WebKit skin, like OmniWeb before it. This is more sad and nostalgic, OmniWeb was always about the UI anyway, while iCab showed that two skilled and dedicated programmers could compete in making a browser that (some) people actually wanted to use.

This is not to say that it wasn't a sensible, rational, and reasonable business decision. iCab can prosper more easily now that as tiny team can focus on the one thing closest to their users, and leave site compatibility to the much larger group of WebKit developers and evangelists. My next beer will be on them. However, this leaves the choice on the Mac platform to three, WebKit (Safari, OmniWeb, and now iCab), Gecko (primarily Firefox, but also Camino and others), and Presto (Opera). In general the trend on any operating system is less choice, not more, and this trend is likely to continue. There is unlikely to be a radical new browsing engine in 2008 or in 2009, the choice is instead going to be among the existing ones.

Entering a dark age of innovation

,

I came across this report on a study by Jonathan Huebner showing that the rate of technological innovation is slowing down, and that by this rate we will be down to the Dark Ages level by 2024 (a curiously precise prediction, but presumably by comparing the technological advances of the millennium 500-1500 with the current trend).

There is no doubt this study is seriously flawed, the data picked can be seen as arbitrary and even misleading, but it is no more flawed than the other hypotheses and studies around. Self-styled futurists tend to be highly myoptic. It is a natural phenomena, you are highly aware of the changes happening to you, but less to to your parents and their parents' parents. In particular I admit a strong scorn of the singularitons claiming our world will enter a technological apocalypse in the near, but conveniently distant, future. My claim is that revolutionary, paradigm shattering, Oedipal changes are getting rarer as we live a longer productive life. Of course that is far from the whole story, but over time extrapolations always fail.

In a particular area the field may be stable or stagnant for a long time, experience rapid technological growth, and then fade into the background. This can be seen in the ages, we have had the non-starters of the Atomic Age followed by the Space Age, with the more successful Information Age which too will fade. The myoptic bias is to count the changes that are important to us now, and discount the changes that were important to us then, or will be in the future. We will have no greater problems living in our future than our predecessors have living in our present, as long as we can adjust to that change in focus. All that changes fast now will change slowly in the future.

Omnes viae...

, ,

I got a well-appreciated birthday gift from myself a few days ago, the Rome series 1 DVDs. The second, and probably last season, will air in a few days. The time slice covered by this TV series will thus (assumedly) be from the fall of Gaul to the preeminence of the first Roman Emperor. A small gripe is why does it always have to be Caesar and Augustus, and not for instance the republic a couple centuries earlier.

While the backdrop story is one often told and retold, the historical characters are not the stars in the series, but the city of Rome itself. This fictional account of the end of the Republic, and history is always fictional, is the best one I've seen so far. Given the high cost and usually moderate income from historical soaps, dramas, and documentaries, it is likely to remain so for some time to come. The creators have said that current Calcutta, err Kolkata, has been an inspiration for the recreation of the Rome as was, and the city is as believable as the story is enjoyable.

The next fifty years: it is all in the mind

, , , ...

My magazine of choice, (The) New Scientist, released its first issue 50 years ago, and more recently followed up with a hefty anniversary issue.

Reading news (or watching or browsing them for that matter) is a waste of time if you want to be informed or enlightened. I have argued before that instead of following flickering interpretations of what just happened it is better to use sources like New Scientist get an insight into what is going to happen.

Self-conscious at 50, New Scientist looked backwards for its New Zeitgeist in news articles past, as well as forward in inviting predictions for the following 50 years. While both are good reads, true to form it is the present, in the "Big Questions", that this issue shines. One present but unasked question is the role of science itself.

A test to determine the kind of action a scientific branch has is to look at the reaction. Since the time Galileo run afoul of his pope astronomy has annoyed nobody (well, dark astronomy annoyed me, which shows promise). The last public uproar based on physics were the anti-nuclear demonstrations in the 80's. There may be sufficient smokestacks left to give chemistry a bad name, but this is not where the battles lie. Meanwhile information has been the most recent inclusion into the physical system, and with the widest impact the last few decades. That notwithstanding all the theory was fairly established by the time the first issue of New Scientist was published, and thereafter nothing much has happened, and not that much is going to happen either.

Advances in physical science and computer science is now in the realm of usability studies and market research. It is no longer iconoclastic in nature, fundamental world views are no longer turned over by breakthroughs in physics. We will probably never return to the rapid and fundamental advances in the golden era of the late 19th century and the early 20th century. The physical sciences are a part of the establishment. Einstein is an icon, and we use quantum physics when we try to understand the world. If you observe two connected butterflies causing a storm a cat will die while staying alive, therefore if something is sufficiently garbled it is scientifically proven.

Biology on the other hand is upsetting. Christians largely in USA and Muslims largely outside of USA are rallying against Darwin, in a truly impressive display of rear-guard action. What other scientific theory of that venerable age can still muster the troops this way? But it isn't just the implicit threat to creation myths that gets us going. Genetic engineering, cloning, stem cell research... You name it, we protest against it.

Back to the big questions and the long forecasts. With some exceptions we were relieved of the hyperbole. Fifty years is not a long time, half a lifetime or thereabout. The world in the 1950s was very different in flavour to ours, but it wasn't truly alien. The world in 2050 won't be either. The forecasts in physics were largely completist in nature, reminiscent of card collectors, "if we just got these two missing cards we're complete". Based on past experience we will learn more if this completition project fails, but in any case an uninspiring outlook for us non-collectors.

I am much more enthralled that we are well on our way to discovering our past. Thanks to the invention of writing we have known tales from the past for quite many generations now, but what about the unwritten stories? Fossils may be among the oldest things around, but they have been new to us. As Andrew Knoll noted, most of the the artifacts of life and civilization remain in the ground undiscovered, but fifty years from now most will have been found. Non-intrusive survey methods will cover all the land mass as well as the seas. Digging for artifacts and fossils will not be the only way of inquiry. From the human genome project of the last decade, the neandertal genome project is well on its way. We are set to discover not only who we are but how we got to be, much of it from archelogical evidence in living genes in addition to communing with the recent dead.

Applied biology is provocative enough. But when it really goes home to ourselves it will be hard to ignore. Several of the articles touched the fleeting worry that when science has disposed of free will the way it did to phlogiston or the aether, what would prevent us from doing harm as it isn't our fault anyway?

This is reminiscent of when 18th and 19th century science gutted God good, the raised concern was how a society could survive and prosper without the fear of God to scare people into subordination. As you know we still turned out pretty allright. Demystifying our own behaviour will not make us into irresponsible people even though in a deeper sense we aren't responsible for ourselves. Put the other way around proving the illusory existence of self would not turn previously selfish people any more selfless. I may not exist but I still want that car.

Revolutions past

, , , ...



17 years ago, in a Friday November 17 far far away, the seminal event for the soon-to-become Velvet Revolution happened. The event itself, a sanctioned student demonstration ostensibly celebrating a martyr against the Nazi invasion 50 years earlier, mattered less than its aftermath: a fairly brutal police repression, augmented by a staged death by a secret police agent.

To my then jaded eyes, the depth of moral outrage among Czechoslovak citizen about this seeming police murder was endearing. This was shortly after Tiananmen Square (making everyone aware what was at stake), and even in Western Europe death by demonstration was not unheard of, or indeed 20 years earlier they had the self-immolation of Jan Palach and the 70-some killed in the 1968 Soviet invasion.

For me November 17 is connected with a fairly subdued plaque at the spot where the demonstration was stopped by the police. I don't remember when it was made, I think it was some time in 1990, probably at the anniversary. I do remember that in 1990 everyone would go out of their way to show you that spot, even if you had passed by a dozen times before. In the beginning were the revolutionary posters I mostly couldn't read at the time, then the candles, and finally the official plaque which was more or less the end.

The revolution itself officially lasted 11 days, including a theatre strike and a demonstration with an estimated half a million participants, which for a city of 1.2 million and a country of 15 million was an unmistakable signal the gig was up. The post-revolutionary euphoria lasted less than a year, it was commemorated a year or two more, and then the collective amnesia set in. Thereafter it was as it never had happened, it was never talked about. If I reminded anyone about it they were invariably embarrassed, a youthful and Un-Czech (the country had split by then) indiscretion they were aware of but rather would not remember.

As time went by a generation came to be that genuinely didn't remember it, because they never had experienced it (possibly apart from some weird and fragmented childhood memory), or the preceeding communist regime. That too embarrassed and secretly annoyed the slightly older generation. Until just recently when it became a subject again. Some of it was political, the high rating of the barely reformed communist party, as about the only protest party against the less than inspiring crowd of Czech politicians, did frighten the establishment and the anti-establishment alike. And youthful indiscretions are less embarrassing when you're not as youthful anymore. So nowadays it is a school subject, and if a revival is too strong a word (no expected theatre strikes) it is a reminder.

So today I decided to visit that old plaque. It is on one of the main streets, so it isn't as if I haven't passed by it countless times already, but I too haven't visited it for 15 years or so. It was much as expected, some strangely inappropriate posters and candles in massive appearance, to be taken pictures of by everyone in the audience with our camera phones. Having done that we all moved along.

How the Internet has changed

, , , ...

A Debates & Discussions forum thread:

How has the Internet changed (or changed your life)? How will it change in you lifetime?


I can recall as a kid in the seventh grade, in Montreal Quebec, in our computer science class we had access to a time-sharing computer based somewhere else in the country. The method of data input/output was an enormous Telex teletype machine that sounded like a jackhammer when printing. [...] My vision of the future for Internet is not all rosy. [...] What I'm sure of is that the Internet will continue to become part of our lifestyle and those who are Internet illiterate will slowly be left behind as progress marches steadily on. [...] I invite any and all to send their ideas.

En svensk tiger

, , , ...

Opera 9.0 Beta is now available for download. For those of you who have regularly tested the 9.0 previews and weeklies the difference from those isn't that great (except in stability), but from 8.5 it is huge. There are new features and advances in standards. One that has truly progressed since 8.5 is SVG. While we don't have complete SVG Basic support yet, with full styling and scripting, we are close. Getting here has been a long journey. The first version of SVG, SVG 1.0, became a W3C Recommendation in September 2001. We had an interest in SVG even earlier, but the sheer size of the specification made us decide against it, it was hard to justify putting so much effort into a format that was going to need years to get a foothold in the market. We had done it with PNG before, but that was easy. The arrival of the Adobe plug-in decided the matter, why should we spend our remaining resources on SVG when there was a viable alternative? We weren't looking for a Flash competitor, which seemed to be Adobe's main drive until they bought Flash several years later. It definitely wasn't to make a Purity of Essence markup language not sullied by the real world like the HTML harlot – many working group members at that time were deeply hostile to the Web. The mobile companies were the next to turn on to SVG, and while there are clear benefits with SVG on phones, the gains can be even larger on a larger screen. We saw a vector graphics markup language as an adjunct to HTML, together they would become more than they were separately. Each language could provide what the other one could not. HTML augmented with CSS could do both text, layout, hypertext, semantics and more. But it couldn't do the simplest illustrations (except through brutal hacks), or graphs, or fancy boxes or headlines. As HTML was a W3C language and SVG was a W3C language you would have expected that these two were well integrated, that you could easily use one to enhance the other. That certainly isn't the case and this is a tremendous unfulfilled promise. It isn't all bad, the two languages do integrate with each other after a fashion. They can be looked at as feuding siblings, having them in the same room will cause torment, but they are family. Hopefully some years from now they will both grow up. How did it get to this state? One reason was attitude, another was timing, a third the participants. The way W3C works may also have had an influence. Many at the time believed that the Web was fundamentally broken, that it was better to have a fresh start. If the Web was broken, what was the point in integrating with it? Whenever SVG integrated with other specs, it was always to other new and still largely unused specifications. SVG wasn't to enhance the Web, it was to replace it. This was less ridiculous than it might seem now. The Web was war-torn and not in a very presentable state. To this day our Open the Web team is working on, or rather against, the Web of 1999. The timing was unlucky too. HTML 4 was done when SVG started, and in the following years that group was preoccupied on reengineering HTML to be on top of XML instead of (ostensibly) on SGML. In any case the climate for HTML, W3C's greatest hit, was chilly. There also seemed to be an implicit W3C assumption that XML made document integration automatic, and then that XML Namespaces would do so. For one reason or another the browser makers were not involved. Microsoft, that had an SVG precursor in the VML format, has just won the Browser Wars and could go back to sleep for another half decade. Netscape was busy changing its skin to Mozilla. We were turning our CSS browser into a DOM and CSS browser and, more hidden from view, a browser that could thrive in the most cramped devices. The actual SVG implementors didn't have any great interest in Web integration, for them this was just extra complexity with no direct benefit. We might have been one of those implementors. In the summer of 2002, mere months after SVG 1.0 was published, our lead SVG developer held an internal demo of a prototype SVG implementation that included the iconic SVG image of the time, the SVG tiger, looking the same way then as it does now. A bare-bones SVG feature set, much smaller than the extended SVG 1.1 Tiny we released in Opera 8, could have been a part of Opera 7. It would have been scalable vector graphics later to be animated, styleable, and scriptable, but not much more. But the great migration towards Presto had started, SVG had to wait. Further on there was a repeat of the Adobe plug-in story, as Ikivo made a great SVG Tiny implementation that covered our phone needs if not our cross-platform needs. Had it made any difference if we had given higher priority to SVG? For the standards, probably not. The odds were against it at the time, and we had little time to spare for W3C work. It might have increased the browser attention to SVG, but none would likely have come up with an actual implementation faster anyway. Web developers might have caught on to SVG a little earlier, but they would have been even more frustrated with SVG than they were with HTML+CSS. Today Opera 8 (but not Opera 9) suffers from what I see as a mistake in the specification: If there is anything in SVG a browser doesn't recognize, it is not allowed to show anything at all. For a hardcore graphics SVG implementation, like the one we were contemplating, that would in practice mean that unless the SVG was specifically made for Opera, we would not have been able to show it. Another and much larger problem is that even with this rule, which was made with the intent to make different implementations interoperable, the existing SVG products today aren't really compatible. We will eventually get this right, but it will take years of slog (déjà vu for any CSS enthusiast). When the SVG world and the Web world eventually did collide, that meeting was often acrimonious. It probably was unavoidable. While there was ideology on both sides to be dealt with, SVG as a standard needed some years on its own to find its standing. HTML, CSS, and DOM is today a fairly harmonious trinity, but that was not the case at the beginning. Early on Netscape had annexed HTML, CSS came from W3C and got its first real implementation in Opera, and while Netscape came up with JavaScript, Microsoft trumped it with a superior and more popular DOM. Neutral ground W3C DOM (which is more similar to the MS DOM), while formally the standard DOM created by Microsoft and Netscape together, wasn't really supported by either browser. Mozilla was the first browser to support W3C DOM, followed a few years later by Opera, Konqueror, and most recently iCab. Standards are the first casualty in browser wars, and it took a decade to mend them. But during all this hammering something else happened, the three specs began to fit. Fitting HTML and SVG the same way should hopefully mean less banging, and the signs are that they are slowly melding, and people from both camps are seing the mutual benefits (and, as many of us are commercial, the business cases). What is more intimidating is that this is going to be the easy part. Uniting HTML and SVG is a bit like uniting magnetism and electicity, there are other forces less mallable to the theory of the Grand Unified W3C.

Death in the Family

, ,

Co-founder of Opera Software, Geir Ivarsøy, died of cancer last Thursday.

The first time I met Geir Ivarsøy was in 1998 installing Opera 3.5, when Opera got CSS support. What I didn't know then was that this very first good CSS implementation had been Geir's work in few months, but it made CSS geeks worldwide pay attention to the Opera browser. A couple years later many of us ended up as Opera employees.

When I started in Opera I was charmed by that people worked regular hours, the atmosphere was as far removed from the life of a microserf as could be. Geir, our lead developer, went to the office in the morning and home to his family in the afternoon. But what happened in between was pure gold. Dozens of newly employed Opera programmers lined up at his door whenever they had a problem they couldn't fix. Geir would pinpoint the problem and the solution within minutes.

While this complete command of the Opera source code was impressive, it wouldn't fit the organisation we were to become. It must have been around 2002 when he told me with some satisfaction that he didn't personally know the code anymore. And the rookie programmers were rookies no more. It is their work you see in Opera today.

When we needed to jump ship, both continuing on what was to become Opera 6 and developing the next generation engine, Geir and Karl Anders were the architects of Presto, based on experience from the past as well as the requirements from the future. Presto is a large collaboratory effort but it was also probably the most sensitive engineering project we have ever undertaken. We had dozens of projects hanging in the balance, we could not afford to fail and we didn't.

As Opera Software has grown from a handful people to a quarter thousand I still recognize most of the same company culture as when I started. The Asterix-like attitude, never to be fazed by incredible odds (part of what makes it fun to work for this company), the drive to make something that is actually good, and never cease to improve what's there.

Some of this Opera culture can be pinned on individuals such as Jon's endearing conviction that nothing we ever do is second-rate. Less obvious but just as present is Geir's influence, both on those who met him, and those who did not. I would not call him shy, but he was intensely attention adverse, you would never see him first in line when Opera won prizes. He didn't brag even though he had better reasons than most everyone. He focused on doing the task right and doing it well, and the proof was in the code. To this day you won't hear an Opera programmer brag, even when they have good reasons to, and they often do.

Geir's understated sense of humour complemented those of us who enjoy being rather overt in our merry glibness, like elsewhere Geir was subtle but clear. He was immensely nice, likeable, unassuming, but not easily impressed. As the saying goes the good Geirs die young, but in this case his renown will last for a long time.

Fig leaves

, , ,

Going from the usefully useless spacer to the false start of HTML 3.0. HTML 3.0 never made it to a final specification, but it contained many interesting if half-baked ideas. One of these was the fig element. Like spacer the element had many attributes now obsoleted by CSS.

Also like spacer or the logo and photo types in vCard, but unlike img, object, or canvas elements fig tells what kind of image is shown, here a figure. In addition the figure had associated content, the caption and credit elements, as well as content fallback like for object in HTML4. caption reappears in XHTML2, while credit has yet to reappear.

Two other properties were unique for this version of HTML, the overlay, an image positioned on top of the figure, handy for sprite animations, but here ostensibly to save bandwidth. The images could have a checksum so that when leeching an image the owner of the site would not be able to swap the image with an inappropriate one without the browser detecting that the image had been tampered with.