Friday, April 30, 2004 - Posts
I wrote about this some times ago but today the posts of Greg Robinson and Robert Chartier points me to the same argument: the comunity is too much Longhorn (or Whidbey) focused.
I agree that the future is interesting and fascinating, that we must be prepared for the future of .NET programing etc., but in these month if you buy a programming journal like MSDN what you can see? Whidbey articles, Longhorn articles, Avalon etc.
But the present?? Why not writing about the actual development platform? We've to work with this NOW! Personally I agree with Greg... I'm tired to see articles with contents like writing a windows form application on Whidbey and see that the "Hello World" is better for eyes than with VS2003...
I think that a real interesting technical article must talk about the present technology, not only about the future... 
UPDATE: I've forgot to say that just this morning I've wrote on my Italian .NET User Group a post about the next TechTalk 2004 here in Italy... 640€ for conferences that for 80% talks about introduction to Longhorn, introduction to Indigo, introduction to Avalon etc. Maybe too much??
Do you think that pressing CTRL+ALT+CANC for rebooting your machine is not so easy?
Try this method... this could be a future business for someone!! :D
One of my favourite site that I check every day is The Hacker's Choice (THC), the site of a group of international experts involved in network and system security.
Today on the first page there's an announce: Johnny CyberPunk, a famous hacker of this community, says that "This is an anouncement that I'll personally not publish any further exploits to the public. Too many flames from guys who are too lame to use the exploits or to fix offsets for other targets. Too many risks that kiddies around the world use it for bad purposes. I saw, that the original intention, to publish exploits, for pentesting or patch verifing purposes didn't work. Remember, that I speak just for me, not for the rest of the group".
I agree with this choice. His last free creation was the IIS 5 Exploits code, freely available (source written in C) on the site. This code could be dangerous if someone use it only to "play as an hacker". Publish code to take advantages from exploits is not the right direction for an hacker with intelligence.
Good decision Johnny! 
On MSDN in the ASP.NET Community there's an interesting question:
Visual Studio .NET creates Web applications using the Code-Behind model, while Web Matrix creates them until the Code-Inside model. Visual Studio 2005 will add yet a third model (Code-beside). Which should you use?
The opinions of 4 experts are given.
I'd like to know what other people thinks about it.
Personally I like the separation of ASPX and source code. A Web Designer can work on the graphic part of the site (HTML) and a developer can work on the source code... there's a good level separation and I like this "layered" vision.
However, Dino explanation is good. The future VS.NET Whidbey will introduce the code-beside model, which seems to be an excellent combination of the original idea of code-behind with VS.NET IntelliSense-related needs. Advantages? Maybe a lot...