intertwingly

It was with a sense of foreboding that I read the posts that swam past on Planet Intertwingly today. First came Mozilla’s Brendan Eich’s chastisement of Microsoft’s Chris Wilson , followed in a short while by commentary by Sam Ruby , where he...

--- “I want what is good for end-users”, I, John Nobody, said once. And I explicitely showed why and how.
— “I want to be relevant”, said some google cretin, who thought he was “smart” compensating mediocrity by allying with the powers that be.
— “I still get my pay check”, did not explicitely said certain W3C honcho, whose idea of two serializations is not even the pseudo-solution he thinks it is.

So...the death of sanity.
Not just XHTML, mind you, but also XML, eventually. And more importantly, the general drive to sanity, however imperfect.
The death of any resemblance of authority by W3C, too (which granted, was a mirage).

Given capitalism, corporations “win”, everybody loses. No surprises.

Just as in the “real world”.

Crashes DO happen, however.
So do revolutions.

While visible, that’s a maze of twisty passages, all alike.

The page itself is an ad, which leads to [link].

That page lists three options.  Go to the page that I can’t read.  Send myself an SMS message (result: URL of the same page), or select my device from a list (which doesn’t list my device).

Try [link]

That should bypass the dropdown cruft.

I have yet to figure out how to install Opera Mini, or even verify that Opera Mini is supported at all on the device that I have.

Again, what I see if I go to the Opera Mini page is that the Products... Support... Company... and Business #nav dropdown menus are all (simultaneously) dropped down — just the backgrounds though (rectangles with horizontal lines, no text), with the net effect being that the page itself is obscured.

Try media queries again.  Your phone’s built-in browser doesn’t support them, but Opera Mini does.

I went to operamini.com, but the browser on the phone did such a poor job of rendering the page (the dropdown menus on the top are permanently dropped down, and obscure the content of the page) that the page was useless to me.

As to OpenID: I do try to get the “sreg” nickname and fullname info and have tested it with my setup, but for some reason it didn’t get your info.

As an update: the problem appears to be related to the “footer” that I relocate to be a dropdown menu.  It doesn’t relocate with this web browser (which is fine with me), but does cause the screen width to change (which is what I want to avoid).

anonymous. Heh. I figured it would take the name via OpenID somehow...

That page does not appear to be always up to date. E.g. my Sony Ericsson C905 is not listed either but Opera Mini works fine. Maybe go to operamini.com on your phone and see what it says?

I truly am new to this, and honestly don’t know.  I don’t see my device listed on this page.

I guess it is not an option to install Opera on that phone?

But Safari’s track records are pretty good, right? It’s not bad for the simple reason that it had to be good. It had no chance of becoming a major player in the market if it’d done any less than Firefox and Opera (and really, it’s only with

It would be hilarious to see the first part of AWDR become a sort of “Choose your own adventure” in which you can choose to write unit tests by skipping to page XX and you can choose to avoid scaffolding using another choice. Although all choices should work in the sense of not having error messages being thrown from a given version of Rails, it would be really funny to also have a “Fail” adventure in which the developer chose to write the depot app in the worst way and the code is now unmaintainable.

Really enjoyed the book. I’d like to see running with JRuby and integrating legacy Java code covered, but that is probably a separate book and something that I’m going to have to discover for myself.

A little while ago, Carl and I starting digging into Rails’ initializer. We already made a number of improvements, such as adding the ability to add a new initializer at any step in the process, and to make it possible to have multiple initializers...

A little while ago, Carl and I starting digging into Rails’ initializer. We already made a number of improvements, such as adding the ability to add a new initializer at any step in the process, and to make it possible to have multiple initializers...

If only runcoderun.com supported XMPP notifications :)

Aunque el HTML5 está lejos, la gente ya está empezando a desarrollar cosillas usando sus nuevas capacidades. Y es que cada vez más los navegadores lo están adoptando, aunque aún es muy pronto para poder usarlo libremente sin preocuparnos de...

Since December, Rails has undergone a fairly significant internal refactoring in quite a number of areas. While it was quite tricky at first, we’ve started to hone a process for diving into a new area of the codebase and emerging some time later...

Testing AWDwR examples with different versions of rails...