F1 Belgian GP: Petition against FIA decision
The Belgian F1 grand prix ended with a spectacle. Slight rain turned the race into a gliding party and a historic fight for 1st place started. Hamilton (McLaren) passed Räikkönnen (Ferrari) who later crashed into the wall and Hamilton won the race... until FIA came into action.
Just before overtaking Räikkönen in La Source, Hamilton had little choice but to cut the last corner of the Bus Stop chicane. By doing that he got in front of Räikkönnen so he let him pass again. The traction of the Ferrari on the wet surface was awful, but when they both passed the start/finish line, Hamilton was driving nearly 7 kph slower than Räikkönnen. Hamilton got behind him again and passed him in the next corner where the Ferrari was again very slow.
Two hours after the race, FIA stewards decided Hamilton had gained an advantage by cutting the corner and gave him a drive-through penalty. That's a bit silly after a race so it was converted into a 25 second penalty, putting Hamilton third in the race's rankings.
I have read the Formula One Sporting Regulations and the FIA International Sporting Code with special attention for the two rules quoted in the official press release, but those rules say nothing more than "you must use the track". The so called "gaining an advantage" is never explained or declared and the rules are absolutely void of any regulations about what should be done to normalise the situation again.
The decision has once again fueled the discussion about FIA being biased in favour of Ferrari and several important people in the F1 have now said what a big part of the public has been thinking for years. In any case, such decisions are the exact opposite of what the sport needs. An online petition has been started to try to convince the FIA to revert the decision. Will it help? Probably not, but not trying won't help at all.
Do you want to sign the petition? Just click here. I already did!
The quest for a PHP editor
I've had a hate-and-love relationship with a few editors over the past few years, but I've never found one that I truly love. Some look promising in the beginning but after some time I really get tired of their limitations.
I thought I had settled with Eclipse (with PDT) because it's the best I've used, but the software update messes up so often it's not funny anymore. That and those pesky "builders" that keep flagging stuff as errors in places where they're absolutely useless. So with Eclipse rapidly losing credit I started a new search... without any results so far.
Perhaps my requirements are too steep, but Visual Studio [1] manages to combine them so I don't think they're too far-fetched. What I want in a PHP editor (or rather IDE):
- Projects instead of loose files (think of: Visual Studio solutions or Eclipse projects).
- Smart intellisense (not just autocomplete, it should be able to parse the project and recognize custom classes - Visual Studio is the reference here).
- Handle whitespace properly (tabs to spaces, clear trailing whitespace per line, clear empty lines).
- Formatting (with bonus points if I can configure my own set of rules).
- A non-cluttered modern interface.
Extra bonus points are awarded to IDEs that can perform small "design-time" checks (e.g. unreachable code, non-returning branch, unused variables, ...) and have a couple of refactoring functions/shortcuts (to name two: rename variable/method and implement interface).
So if there's anyone who knows about a little gem for PHP development, please let me know. Oh, and don't make me beg
[1]: No, there's nothing wrong with your eyes. Visual Studio is actually a Microsoft product that I like. It's simply the best IDE in my very humble opinion.
MOSS 2007: laugh or cry?
When Microsoft released Microsoft Office Sharepoint Server (MOSS) 2007, it was touted as The Next Big Thing™ for enterprises. And that's where the good news ends...
This piece of software has so many issues I don't even know where to start. My first encounter with it was when I had to evaluate the web content management features of the product. That evaluation period lasted about a week, but was stretched to a month just for the sake of it. When coming from something like eZ Publish, it felt like I had done some time travelling all the way back to the Stone Age [1].
A remarkable feat that Microsoft managed to pull was to release an anti-developer product. My career is still pretty short, but it was the first time that I encountered a piece of software that was set on making a developer's life as hard as possible.
After the dust had settled and a couple of holidays had joined other historical facts, it was time for the second encounter. The idea was to give the collaboration features of MOSS 2007 a test run. So my colleagues and I clicked around when we suddenly noticed the "My site" link. A harmless link [2] to a personal site... until we (= 3 persons at that time) managed to click at the same time: one arrived at the personal site, one got an error but managed to proceed and the other one got an error and another one when trying to proceed. Guess which one was me... I was told it was caused by the speed of the network connection. Makes sense? Not to me.
The security settings regularly start leading their own life causing all sites to go down, file uploads went wrong and blocked all edit actions on document lists, etc. These are just a couple of things, but I could go on for quite a while. It's at a point where I don't know whether to laugh when it goes wrong or to cry with the fact Microsoft managed to produce such a nightmare.
[1]: I know there were no computers back then, but let's forget that little detail so I can make my point
[2]: Or so it seemed...
Recommend me a 24 inch monitor
I'm looking for a 24" monitor, but I just can't find the one. I've been reading tons of reviews during the past few days and that has made things even more complicated.
On one side there are the TN panels. While I've been very happy with my current monitor (Iiyama AS4314UT) I can't get rid of the impression that recent TN panels have a lower quality. The monitors at work seem to confirm that suspicion. The 24" TN panels currently do not have response time correction (RTC) as can be seen from the specified 5ms response time. The result is that the 5ms as specified by the manufacturer is the most optimistic scenario (black-white-black). Gray-to-gray response times are pathetic.
On the other hand there are the *VA panels. While they should be superior to TNs in terms of image quality, they also have disadvantages. They do have hardware RTC but that hardware can also produce errors (read: it guessed wrong and a pixel gets the wrong colour). Depending on how severe the miss is, you will either see it or not. I haven't found any monitor yet where you won't see some errors. The biggest downside of these monitors is the price: they are effing expensive.
There are also S-IPS panels, but their price jumps off the scale.
I'm starting to think it's still too early for a 24" screen and that the market is still in the starting blocks. On the other hand I'd like to be proven wrong because I love the space on 1920x1200 screens. So if you have any idea, please leave it in the comments.
PS: Keep in mind that I'm in Belgium so we don't have the abundance that e.g. Germany has. Example: I've heard of Iolair monitors, but I still have to come across a shop that actually sells them.
Exciting times ahead for PC gaming
So it's been a little over 4 months since the last post, but this place isn't dead yet... and the same can be said about PC gaming.
We've heard all kinds of doom stories concerning gaming on the PC, but I'm sure that good content will sell and the second half of this year is literally filled with exciting titles. I'm currently tracking 28 games and only 4 of those are currently scheduled for a 2009 release. That leaves 24 games that are scheduled for release between the end of August and the end of the year.
For those that don't know what's coming, here's an excerpt from the list of games I'm tracking:
- Brothers in Arms: Hell's Highway
- Call of Duty: World at War
- Command & Conquer: Red Alert 3
- Command & Conquer: Tiberium
- Crysis Warhead
- Empire: Total War
- Far Cry 2
- Mafia II
- Pure
- Quantum of Solace
- Red Faction: Guerrilla
- Tom Clancy's HAWX
- Tomb Raider: Underworld
Exciting times are ahead, but my wallet doesn't agree...
Vanden Borre: 10 weeks to deliver a battery and counting
The story starts on December 26, 2007. That's the day I ordered my new digital camera at Vanden Borre. I got a deal on the camera that included a mini-tripod, a carrying case, a 2 GB memory card and an extra battery. I was quite surprised to get a phone call the next day. My camera had arrived in the shop and I went to pick it up. All the extras were in stock too, except the battery, type Nikon EN-EL5, which was ordered immediately. Mark the date: December 27, 2007.
After two weeks, I went to the shop to inform about the battery. There was no news and I would have to wait. When I asked how long, they couldn't tell me. In fact, it could still be the same 10 weeks later as far as the staff was concerned.
I contacted their customer support department after five weeks. There was no news coming from the store and the online tracking wasn't really useful either. They replied they couldn't do much about it, but they'd query the manufacturer. I received a follow-up message from customer support basically telling me the same thing: no news, keep waiting.
Today is March 11, 2008 and we're well past the 10 week mark. Guess what? Still no battery! I have bugged customer support once again asking how long this is going to continue. I do know that I'm running out of patience.
10 bloody weeks... I think someone can walk from China to Belgium in that time frame. I'll definitely think twice before purchasing something else there...
And just in case someone from Nikon reads this, they're blaming you as manufacturer claiming there are no deliveries. For 10 f***ing weeks?
IE8 defaults to IE8 now
One of my previous posts mentioned that IE8 would default to IE7 standards mode unless web developers would specifically request the new IE8 mode. Well, there's some good news coming from Redmond.
The IE team announced that they changed the behaviour. IE8 will now use its most standard compliant rendering mode for pages that meet the criteria for standards mode. If you, as web developer, want pages to be rendered using IE7's standards mode you will have to use the META tag or the corresponding HTTP header. So they did the right thing and made this feature an opt-in feature: you only have to act if you want to use this feature.
I'm glad Microsoft listened to the web developer community and did the right thing. This puts the burden on the developers who don't want to fix their pages and it might persuade them to update their code if it's broken in a new IE version.
In other IE8 news, Beta 1 of Microsoft's newest browser is now available. This is only intended for web developers and designers. If you are a regular user, you should skip this release.
IE8 defaults to IE7
This is surreal... I just posted about Microsoft's latest trick with IE8 and a meta tag and I already have an update that warrants a new post. Through some reading and clicking, I arrived at a blog post by Jeremy Keith on this subject. Without going into the pros and cons of the meta tag, his post shows me three things.
The first thing is the format of the tag. It appears it will take the following form:
<meta http-equiv="X-UA-Compatible" content="IE=8" />
A second point is IE's default behaviour. In this case, default means without any changes to existing pages. Apparently, Microsoft decided that, without meta tag, a page will be rendered in IE7 mode. I'm going to borrow Jeremy's words because they are perfect:
Unless you explicitly declare that you want IE8 to behave as IE8, it will behave as IE7.
That's just plain ridiculous! What's the point of creating a new version if the default behaviour is to use the old version? I guess this is Microsoft logic.
The third point is closely related to the second one. The right default behaviour would be to use the current browser version. There is a way to activate that option by using IE=edge as... you guess it, value for the content attribute of the meta tag. Using that trick is strongly discouraged though.
So essentially this means the meta tag is not an optional step, but rather a mandatory part of creating a web page. To use the mode associated with a browser version beyond 7, you have to specify it. To disable the checks, you also have to specify it.
This is so surreal and such mess..















