Building simplicidade.org: notes, projects, and ocasional rants

Notes

last update:

Bonjour to you too

Check this out: Amazing the list of people here… 450 persons from all over… Just starting.

Just left the conference of Dina Mehta – Social Tools for Research and Collaboration. It the best one so far. She talked about the blog/wiki/network collaboration that grew out of an collaborative effort when the December 2004 Tsunami hit. They had a chaotic environment and operation but from that, order slowly become apparent. The most interesting point for me is that the reason she thinks it worked was that people were helping out in the fields of expertise they had.

Let's try this again

Nuno, let’s try this again: both two posts I wrote about this minor issue (the one you quoted in your initial article and my response to that article) are not against x86. Please re-read them. It’s about Intel. Not x86, but Intel. That’s what I’m skeptical about (and thanks for the explanation about British and American spellings). It’s not that I don’t like x86, I use them every day of my life, in all the servers I buy, or the servers I recommend buying.

Sharing the pain

The new PowerBook saga continues. What will I do next? Well, I really don’t know. For now, I’m sharing the pain with others. Questions to be answered: how long after Mactel shows up will Apple support PowerPC hardware? Will see.

It's not about x86, Nuno

Nuno didn’t read my posts closely enough, it seems: Some people (lots of them in fact) seem to be sceptical of this and wonder why the heck would Apple switch from a so far successful hardware architecture. I’m not skeptical (ant not sceptical, according to Mac OS X spelling check) about x86 choice by Apple. I’m skeptical about the choice of vender of x86 architecture. My feeling is that Intel is not innovation in the last years and they don’t seem to have a strategy to x84-64 (compare Itanium sales to Opteron).

Questions needing answers

Going forward, I’ll see lot’s of talk about Apple and Intel. As Rui as told you, as long gcc runs, I’m ok. I use my Mac mostly in UNIX-mode, so I’m not in too worried. Now, the only thing that is still unanswered in my mind, is why Intel. Why not AMD. Also the 32bit question. So I decided to keep a log of my questions (and hopefully answers): Why did Apple decide to go with Intel and not AMD?

Well, at least will get softcore porn out of this deal… I will post pictures of me naked on top of my car in broad daylight if Apple moves to x86 chips. Seriously. :)

Why Intel?

Let’s say that I buy into all this stuff about Apple switching to x86 chips. I don’t, but let’s assume I do. Why Intel? Why? Why not Opteron? It’s a superior architecture, and the PowerMacs already use HyperTransport… Well, will soon find out what this is all about. The only sure thing I know, is that Jobs does not announce the switch to x86 chips next week, CNet and other will have a lot of explaining to do to it’s readers :).

Ruby on Rails, and Catalyst

So, after having learned a bit about Ruby, the next logical step for me was to try Ruby-On-Rails. A bit of background: before going to work at Sapo in the XMPP Messenger product, I was a lead-developer at Novis. My main task there, was to build websites and provisioning systems, and the glue that ties billing systems with technical databases. We used a framework that was developed internally since ‘99, and in it’s latest generation was called Apache::WAF.

Ruby and Perl

I’ve been learning Ruby for the last couple of weeks. I bought the book some time ago, and I’ve been reading and rereading it several sections. Ruby is a very very good language. Blocks are one of the most productive features I ever used in a programming language. Yet, I use Perl everyday. I’m a Perl user since 4.something patch level 35 or 36, and I really like perl5. Also, at work, I need Perl and POE to build XMPP components.