To cut to the chase, Spiderman 3 was... part great, part awful. On the one hand, amazing cinematography and special effects, on the other hand a soulless script, misguided patriotism on the part of the director (this scene in particular reminded me of Raymond Chen's classic saying, "I bet somebody got a really nice bonus for that feature").
There is so much going for this movie that I couldn't help but attribute most of its shortcomings to a surprisingly shallow screenplay; my theory is that Sam Raimi's background as a B-Movie director ("in the trenches" is the term I'd use), while affording him impressive technical innovation and brilliant tongue-in-cheek humour, does not lend as well to his screenwriting abilities. The first two Spiderman movies were written by professional writers, and with Raimi's superb(not to mention distinctive) style of visual gloss the combination is very effective. For some reason the Raimi brothers took it upon themselves to write the script for the third movie, and it suffers accordingly.
Overt patriotism (which was much more subtle and agreeable in the first two movies) is very awkward for a superhero that is, in many ways, the antithesis of his contemporary who swears to uphold "truce, justice and the American way;" this reflects in the acting, and outlines how artificial those scenes were. The same goes for most love- or romance-related scenes which also felt forced and superficial. Tobey Maguire, who seemed in the first movie so appropriately docile and nerdy, on the second suitably vulnerable, now seems a little out of his element; in his defense, the over-the-top dialogue and violent mood-swings called for in the script would probably make any actor falter. A lot of the script just doesn't work.
Sandman is, and please remember that I have not actually read the comics, an utterly uninteresting character. It seems like a subplot, and one that doesn't make sense at that (it was never obvious to me why he fights against Spiderman); Thomas Haden Church plays, in this case, a very lethargic character that has - whether due to bad scripting or bad acting - very little depth. This would be a good opportunity to oppose a conundrum (minor spoiler ahead): at least once during the movie a fake news broadcast is shown, in which the anchorman provides commentary on the proceedings in real time. The anchorman provides the audience at home with the particular details of the combatants, and names them accordingly (Spiderman, Sandman, Venom). As my friend Yoav puts it, "who gets to decide these names anyhow?" (link in Hebrew)
On the plus side, James Franco actually seemed to learn to act, or maybe lack of any significant screen time in the first two movies never let his talent show. His dialogue is, ironically, quite sensible, and he carries it off very well indeed. A cameo appearance by the legendary chin is utterly hilarious, the music is great and the cinematography - as I previously alluded to - is simply fantastic. I'm not in the business, but I wouldn't at all be surprised to find out that Raimi has invented any number of new camera techniques in the course of filming Spiderman 3 alone. The special effects are brilliant and there is non-stop action - most of which is really good.
In conclusion, to reiterate the first sentence in this article: Spiderman 3 is not a bad movie, nor is it great (that title is reserved to the first movie in that particular series). I just wish Sam Raimi would stick to what he's (very) good at and leave the screenplay in the hands of people better suited to the task.
Lastly, it's worth noting that I saw this movie in Pathé Tuschinski in Amsterdam, which is undoubtedly the single most impressive cinema I've ever been to; it is a very large building, reportedly built in 1921 in the Art Deco style, and much more impressive on the inside than on the outside. Theater 1 is huge, spacious and comfortable, with an astounding number of chairs and two (!) levels of balconies. Audio and video quality was excellent - possibly the best I've ever experienced, and the lobby alone is worth the price of admission which, excluding discounts or sales, is €9-10 - quite pricey.
Long time no update. Reason? A vacation in Europe - mostly centered around the Netherlands (which I like very much). In the meantime I'll just post some random musings:
- Radiohead rock. I have this thing where, when I hear music that I immediately dislike or "don't get," I feel obliged to give it another go every year or so. It took my years to learn to like Pink Floyd, and even more time to learn to like Radiohead, but after a serious listening session I have to concede that my friend (who we shall term "the rhesus") was right to call OK Computer "one of the 20th century's sublime records."
- At Outline 2007 (on which I will expand in a seperate post) I got acquainted with a Dutch tracker who styles himself Cosmiq. Take a listen to his second album, which I actually really liked (particularly track 3, "A Shine Too Much").
- You'll notice that I added a button for the FSF's latest campaign, Play OGG, under "advocacy" on the right. I'll take OGG over MP3 any day (on account of better sound quality for size, and no licensing fees for anyone); I don't expect the campaign to be wildly successful, but you never know. Maybe I'll actually be able to enjoy my next iPod or car audio set on my own terms.
- Had a bit of time to spare, so I watched The Karate Kid again. The movie certainly looks different after 10 or so years -- it actually looks better (if you discount the obligatory '80s movie influences). Pat Morita is extremely funny, and I've seen much worse actors than Ralph Macchio (who looks much younger than his 23 years at the time). It also happens to be a really quotable movie, mock Eastern wisdom notwithstanding: "to make honey, young bee need young flower, not old prune."
Next on the agenda: Spiderman 3.
All I can say is: YES! Breakpoint 2007 was amazing. I went with Mickey (my brother) and we had an absolute blast! On the first day of the event we happened to spot an open bag one of the tables that had a newly-bought cellphone package sticking out of it, and were astonished to see that it had a sticker in Hebrew on it. We left a note saying "contact us!" and the anonymous Israeli guy turned out to be no other than Bacter!
Left to right: Mickey, Itzik (a.k.a Bacter) and myself
The entire 3-day event was an absolute blast. I got to hang out with really great guys like Havoc (one of the Outline organizers), who was cool enough to give Mickey and me a ride to the Netherlands after the party; Jeenio who also hosted the party prize-giving ceremony; Andy Voss (a.k.a Phoenix/Hornet and MindCandy fame) and a whole bunch of others. I also went to a couple of intereting seminars (one on new optimization strategies for realtime raytracing and one on moving from demos to the gaming industry, both of which you can find here), spoke to quite a few demoscene legens (including Chaos and KB of Farbrausch) and had a really awesome time.
People dancing to a live cover of Bubble Bobble? You bet!
Press Play on Tape gave a really good concert in the main hall, and you have to see it to believe it - people were literally dancing to live covers of C64 classics (Bubble Bobble and Commando, to name but a few). They also re-did their classic console-controlled Cannon Fodder, which was even cooler in real life...
One of the Scene.org Awards Amiga demo nominees on the big screen
For the first time I also got to watch the annual Scene.org Awards ceremony play out, and it was really impressive - the level of crowd involvement was utterly fantastic, and the whole hour-long event was amazingly well-received.
Some of the compos were really quite funny - a "speech coding" compo was held, in which someone had a piece of original code and had to transliterate it using the built-in Windows Vista voice recognition. That feature, apparently, sucks eggs, but the wide range of mistakes it made gave the audience a very good laugh for nearly an hour.
The video compo had a wicked-cool entry by Jakob Bienenhalm called LOL, Internet - see it, spread it, it got a standing goddamn ovation!
fr-041: debris by farbrausch, the winner of the Breakpoint 2007 demo compo
By far the highlight of the party was the PC demo-compo. In this somewhat daunting, several-hour event, no less than 23 demos were shown, and there were some really astounding entries: Andromeda (the oldskool Amiga group) made a huge comeback with Noumenon (2nd place), which was not only cool fanservice but also a really impressive demo; Synesthetics won a very well-deserved 3rd place with the excellent STS-01: Lucy in the Sky with Deities; and Traction and Brainstorm collaborated on a very impressive demo called Fairytale. Of the lesser-appreciated entries I particularly favored Kikumoto by Vovoid.
Farbrausch really rocked the house with fr-041: debris though - this demo had at least three standing ovations while it was still playing, and as much as I loved the other demos... you just have to see this. As a regular demo it's impressive. On the big screen it's bigger than life. And when you take into account that it's only 177KB... it easily becomes the new Second Reality. Only one other time in my life have I felt this exhilirated to be a part of an audience.
Whew. There are more pictures and anecdotes I may share on occasion, but for now I'm spent
I've mentioned System Shock 2 before; to make a long story short, it's one of the finest computer games ever made.
The random Gnome's random Lair published an article on how to run System Shock 2 on modern PCs, plus links to the various (extremely mature) mods that improve the sound, texture and mesh quality in-game; one of these mods also subtly balances the game, making certain items more powerful while normalizing others.
I've been playing System Shock 2 once a year or so since 2003 (four years after it came out!) and I can tell you that it's an experience not easily topped. Go, play!
With my project finally nearing completion, it's nigh time for Microsoft to release yet another update to the .NET Compact Framework 2.0. Service Pack 2 ought to bring it to about "beta 2" level.
Check out these gems:
- NETCF deadlocks on exit if native callback delegate has been called on native thread (this is one of the few bugs in the CF I haven't encountered. Ironic, considering we make heavy use of native code in our project.)
- Access violation marshaling a class with a string field (there is a dent in the nearby wall on account of this one.)
- TypeLoadException using generics with NETCF 2.0 (TypeLoadExceptions in general are a lot of fun in the CF.)
- Installing multiple locales of same MSI results in multiple instances of NetCF showing up in Add Remove Programs (we've had some complaints regarding this from our client. They'll be mighty pleased to hear this, I'm sure.)
Now don't get me wrong - I think the CF is an impressive platform, or at the very least could've been. I would venture to say that the people on the CF implementation team are probably skilled professionals just doing the best job they can. But I can't forgive Microsoft - as a company - for shipping a half-baked, half-assed product that even at version 2.0 and after two service packs is still riddled with bugs! It boggles the mind that for any but the most hard-core developers, a third-party extension to the .NET CF is practically a necessity because the class library itself is simply inadequate.
As an aside, I seriously doubt we'll chance regression bugs this close to the launch date, so we'll probably stick with SP1 (we've worked around the issues we've encountered anyway.)
By far one of the most annoying aspects of the .NET Compact Framework is how heavily it relies on P/Invoke to fill in the gaps. The framework itself is missing huge pieces of functionality, and with the lack of C++/CLI for the Compact Framework a developer is often time left with no choice but to hack around the missing functionality with P/Invoke (or COM interop, if you have the patience to muck about with ATL).
The problem is that, on occasion, a P/Invoke call would result in a MissingMethodException (in fact, if you're really unlucky, the type loader will throw the same exception on loading the method actually making the P/Invoke call). Although a lot of the scenarios have been thoroughly ironed out by now and can be resolved through a Google search or some hacking on the developer's part, there is one scario that is esoteric enough that I couldn't find any references to it on the internet: you can get a MissingMethodException when you are out of memory.
We're working on an extremely large (in mobile proportions) and complex project, involving massive amounts of .NET logic combined with a very large, performance-concious and memory-hungry native codebase. We've had to hack around a lot of missing capabilities in the .NET Compact Framework (as well as some bugs and/or shortcomings in other parts of the OS), and one of our native calls would inconsistently throw a MisingMethodException; having reearched the problem for a day or two I was convinced that the problem was an incorrect function prototype for the exported function and added explicit calling convention declarations. This seemed to have resolved and I was content for a couple of days, until the problem resurfaced.
The exception content itself is next-to-useless, and since the same P/Invoke call would work intermittently I was hoping that enabling the loader log might supply some further information. Alas, all the log would provide was the following line:
Failed to find/load [SomeDll.dll] (even in [\Program Files\Somewhere\])
Not good. I then dug up another article on the subject and proceeded to enable the interop log, which provided some additional information:
JIT ERROR FOR PINVOKE METHOD (Managed -> Native):
int Workarounds::GetSinkWrapper(out IImageSink , IImageEncoder );
int (I4_VAL) GetSinkWrapper(IImageSink& ** (INTF_REF) , IImageEncoder *(INTF_VAL) );
I was originally interested in the bizarre native signature generation (specifically the IImageSink& ** parameter - where'd the reference come from?), but upon reading some valid log files for working methods I was convinced that it's a dead duck. I then set my attention to the JIT message: what has the JIT to do with a native function? I theorized that the JIT is responsible for the native signature generation for native functions and kept working under that assumption. That narrowed the question down to, "what went wrong with the JIT compiler?"
Eventually it occured to me that this might be yet another manifestation of the memory limitation issue (processes under Windows CE 5.0 are limited to a 32MB address space). The P/Invoke call is made fairly late into the application; I added a dummy function to the library which I called on application initialization. This forced the JIT to take care of the native library before anything was sucking up memory, and the issue was resolved.
The moral of the story? If you get MissingMethodExceptions on your P/Invoke calls, fisrt make sure your DLL is actually deployed; then check the DllImport signature (you can find a lot of useful resources on this FAQ). Finally, make sure you're not out of memory.
I was screwing around with XmlSerializer and manual recompilations (you can enable raw code output from the XmlSerializer) and somehow this happened:
.NET Framework reinstall time, I guess...
Also had some personal issues to take care of, and my family are all out of the country, which means I have a dog to take care of, which means less free time. All of this results in a lower posting frequency, which I intend to remedy in the coming weeks.
In the pipeline (in case you're wondering, this is also a placeholder so I know what's left):
- More posts about .NET Compact Framework (memory and string handling, nonmodal dialog boxes, bizarre method overloads in the BCL, issues with CAB generation)
- Issues with Windows Media Player Mobile
- Some articles I want to link to and discuss
- A couple additional articles on using wikis in the workplace (with additional insight on real-world scalability and usability)
I use Trillian for my IM needs, and a few days ago ICQ abruptly stopped working with an "invalid password" error. Attempting to log in using Icq2Go resulted in the same error; logging in on ICQ's site also indicated that the password is wrong. Oddly enough, the security question remained the same but the system would accept none of my answers; furthermore it wouldn't accept any of my e-mails (current or previous) for resetting my password.
I searched the help system. ICQ's answer?
Please note: If you are unable to get a new password using the password assistance system, then you will have to register a new ICQ number.
So basically, my ICQ number since 1999 or so is useless. I'll update my contact information and try to get in touch with my older ICQ contacts, but if you're looking to contact me please don't use ICQ anymore (I'm not going to register a new number, not much of a point with everyone having an MSN account anyway). I'll be changing passwords on all my accounts in the meantime.
Update (1 July 2007): The newer versions no longer exhibit this problem (tested on beta 12.0.1183.516). Just make sure you chose "None" for the image borders.
Looking back at my post on Windows Live Writer dating back to August, it seems that I either missed a very significant fact about the product or perhaps something has changed in one of the betas. The short story is that Windows Live Writer sucks at handling images; whenever I embed an image it goes on to severely reduce the image quality:
You be the judge: on the left, the original. On the right, the "improved" version
Not only does WLW upscale my image for some unknown reason, it also does this via an extremely low quality scaler. In the case of simple images such as the one above, this will also result in larger file sizes (this example demonstrates a 400% increase in file size - from under 21KB to a little over 104KB).
This reminds me of the old image pasting problem with Microsoft Outlook, and what kills me is that I can't think of any conceivable reason why anyone would develop this "feature". To add insult to injury, the only feedback link I could find (via this post in the Windows Live Writer blog) is an MSN Groups page that requires registration. The registration process itself asks you about a hundred completely personal questions that Microsoft has absolutely no business asking.
I'll try and get in contact with the WLW team since I do want to keep using the tool, but this particular issue is starting to cost me a lot of time and effort.