To stem the tide of terrorism, key terrorist origin and destination countries need to pass legislations that severely penalize families of terrorists. This will force parents of potential terrorists to take more interest in knowing what their children are up to and curb them away from their destructive path. Also this will raise the ante for suicide bombers so they'll have to put more than just their worthless lives on line.
Also, we need to put up fake Al-Qaeda recruiting websites. While the same can be done by closely monitoring the real ones, this approach offers more options. Trapped and turned, they can help us infiltrate the real ones.
These are, no doubt, extreme measures but I fear terrorism will spread like cancer if steps like these are not taken. Even now, pro Al-Queda communities are spreading. Even in Korea, an Al-Queda fan club was recently formed. It was promptly shutdown upon discovery but, by that time, its membership was 100+. While most of them were probably joking when they were carelessly posting about blowing things up, I am pretty sure a handful of them were not. Left alone, there are no limits to what misguided youths can do.
More popular you are as a blogger, more wary you should be of your power to destroy because your readership is, in essence, a potential lynchmob, ready to be loosed on the target of your choice with a single mouse click. If you are an A-List blogger, be very wary.
If you can't trust yourself not to abuse your powers, then try to cultivate a balanced readership. This is hard to do if you spend a lot of time shouting your readers down, call them names, and telling them to leave if they disagree with you. Keeping doing that and you will end up only with readers whose opinions align with yours.
I tend to focus often on the downsides of the socio-technological advances to do my part in adding to the balance. Evolution tends to leave a lot of dead bodies behind, you see.
Boo is a lanugage that looks like Python (differences) but is statically typed like Java/C# and runs on for CLI (read .NET and Mono). It's most interesting feature (I thought) is how it supports duck typing: with a type named 'duck'.
static1 as int
dynamic1 as duck
Hillarious. Boo still has many issues to resolve before it can be used in production but it's already quacking. To a whitespace freak like me, Boo looks reasonably elegant at first glance. I hope it stays that way.
This is an old popular topic but I thought I should state my opinion. I don't think bloggers are journalists. Journalists who maintain blogs are journalists. Bloggers who act like journalists are not journalists. Bloggers who gets journalists jobs are journalists. Clear enough?
Now that is done, let me state that I don't think any extra 'rights' journalists enjoy above and beyond what us non-journalists have should not exist in the eyes of the law. However, I think they should be allowed to keep what they, as an organized group, can and have forced others to give. We, the bloggers, just need to pull together and do the same.
In other words, we don't deserve anything we can't defend. Journalists have managed, overtime, to define and defend their territory. We can and will do the same over time. Meanwhile, claiming that bloggers are journalists will just cause confusions. We are something else despite the overlap in effects.
Consistently good looking bezier curves are difficult to draw, let alone doing it fast, but Maxim Shemanarev shows how in Adaptive Subdivision of Bezier Curves. At first glance, I don't see much difficulty in applying the same technique for bezier surfaces.
Don't be scared by all the math. After all, following a trail is easier than making one. And afterward, you can appreciate curves a whole lot more.
Jonathan Krim writes about DSG in his Washington Post column. Looks like he did his research, revealing new information like the fact that DSG had to quit school. Unlike most of the million bloggers who read my post (shocking number, really), he also didn't miss what I thought was the right level of social punishment. Good job, Jonathan!
Ironically, I didn't find Jonathan's article through Technorati or Feedster. Instead I came by it after reading a syndicated Korean news article that mentioned his DSG article (Korean translation was excellent, BTW). So the DSG post blasted off like a rocket, up and out of the blogosphere, and then back down to earth on the other side of the Pacific Ocean. Welcome home, DSG.
Bjarke Viksoe, who specializes in Win32/ATL/WTL, is writing a windowless control framework that also has some limited DirectX-based animation support. He has a fine collection of nifty Win32 works which hardcore Win32 developers should take note of. I hope he will flesh out the framework fully soon.
London was hit. I can hear the cries but, sitting in my trench staring straight ahead, the sound turns into fog and dissipates without reaching me. I feel nothing, not even ange, except a sense of relief that it was not me who got hit. Idle days before 9/11 are fading memories, replaced with stains on my uniform.
As I have written before, we are all soldiers on the frontline of battle against terrorism, a line made up of billions of people. There is no similar line on the other side, just an expanse of impenetratable darkness. The darkness is born out of pride and despair, a mix that turns lives into explosives. It is almost comical that they have to throw their lives away to make them meaningful, but that's the lure of darkness.
Hundreds on the line got hit today. Much more will die before the dawn comes. I am sorry but today is just another day at the frontline for me. I'll cry for the dead when the dawn comes, but not before.
My Social Fabric (via Wired) is a very interesting social software thesis that could unfortunately, if applied naively, turn friendship into work. The UI is very cool though.
I wonder if this is the PeopleAggregator Marc was attempting to describe? If not, I still don't get it.
.NET Framework architects continue to disappoint me.
VS.NET2005's WinForms designer, while glamorous, tends to create an increasingly complex web of EventHandler/Delegate dependencies between the top container and the components it contains as well as among components themselves.
Typically, this sort of problem is solved by applying the Command design pattern but .NET 2.0 doesn't have a built-in support. I have no idea why a feature GUI programmers considered essential since the MacApp days is not in .NET.
So I began writing one this morning that used .NET's existing event and delegate support. It took me little time to run into the strong delegate reference problem which just created more work for me. And it looks like .NET 2.0 won't have built-in support for weak delegates although enough people both inside and outside Microsoft have noted the problem.
After more experiments, I've concluded that independent implementation of weak delegate makes little sense because .NET's event and delegate implementation is too deep a level and sealed too tightly. Instead, I am going to abandon using delegates, rigging an interface-based command microframework instead.
A last bit of rant while I am at it. I've found .NET code like below bewildering. First, 'EventHandler' receives an instance of the calling class mysteriously. Second, keyword 'event' turns 'Testing' into a weird collection-like object. And what's with having to instantiate EventHandler to remove an EventHandler?
public event EventHandler Testing;
Testing -= new EventHandler(Testing_Called);