Visual Studio is such a hog

I’m feeling a little frustrated right now. Visual Studio 2005 requires such high specs that my old 1.8Ghz Pentium 4 is having problems just clicking along between the various panes. It’s click, wait for the focus, click, click, wait for focus, etc, etc.
I don’t know why I’m complaining now – I’ve done quite a bit of work on my personal project already, but it’s frustrating because the slowness is finally getting to me.
I’m used to fast fast fast. When I code I type fast, I think fast, and when I compile, I expect instantaneous feedback.
Not sure if it is due to the .NET framework (I installed 3.0 sometime back). I intentionally upgraded my memory sometime back to, are you ready for this, 1.25GB of memory, specifically to support my development work! Wow! 1.25GB! And still VS is unsatisfied!
Oh, alright, the memory isn’t as high as I would have liked, but hey, it was 512MB before.
Hark back to the old days when I made do with GCC.
Now with Visual Studio 2008 on the horizon, with full support for the .NET 3.0 technologies, I’m convinced my machine as it stands right now is more likely to make my morning coffee than to be able to even load VS2008.
I’m sorely tempted to just sink in 2K bucks and build myself a screamer of a PC, so I can code in relatively stress-free environment. But no. I will make my next project pay for itself, and pay for the new machine that I’m most definitely going to buy.
But that 19″ LG widescreen monitor is looking very appealing right now. The luscious screen is showing a disembodied finger making a come-hither motion, beckoning me forward, beckoning me to flash my wallet, and I have a feeling I may not be able to withstand the lure for very long…

Developer Personality Test

I just did this test, which is quite funny (not quite hilarious, not quite dull).
Your programmer personality type is:
You’re a Doer.
You are very quick at getting tasks done. You believe the outcome is the most important part of a task and the faster you can reach that outcome the better. After all, time is money.
You like coding at a Low level.
You’re from the old school of programming and believe that you should have an intimate relationship with the computer. You don’t mind juggling registers around and spending hours getting a 5% performance increase in an algorithm.
You work best in a Solo situation.
The best way to program is by yourself. There’s no communication problems, you know every part of the code allowing you to write the best programs possible.
You are a liBeral programmer.
Programming is a complex task and you should use white space and comments as freely as possible to help simplify the task. We’re not writing on paper anymore so we can take up as much room as we need.
You can try it yourself here.

VB in Linux via Mono – good thing?

I was about to hit the sack when I came across this article: Mono brings Visual Basic programs to Linux. Although it doesn’t explicitly say which version of VB, it does seem to cover only the .NET version of VB (considering what Mono does, this is very logical).
I mean, when you say VB, there are after all two ‘versions’ , if you will, of VB, and that’s VB6 and VB.NET. Both of these languages, despite their similarities in name, are so different from each other that only the colossally stubborn would insist that they resemble anything like each other. The article could do better in being more explicit.
Anyway, [stiffles yawn], so now I can write VB.NET applications running on Mono. Is it a good idea? It simply means if I’ve existing skills in VB.NET, I could leverage that on a platform I don’t understand. However, since you’re coding in VB, it’s a high probability that you’re going to go through a learning curve getting around in the Linux environment anyway. If you’re going to learn, why not learn a new language and code for Linux the ‘proper’ way? At the very least take this opportunity to use Mono to learn up C#, if you haven’t already in the Windows world!

Damn it SQL CE!!!!

I’m oh so pissed.
I waited damn long for the SQL Server Compact Edition to come out of beta so that I can use it in my application. We’re talking bated breath here, the daily website status check.
I just found that it cannot support byte datatype length beyond 510 bytes! This sucks, of course, as I can’t use it to store the images the application that I’m currently writing depends on!
And I spent hours today porting the database from Access to SQLCE, only to hit this problem.
I’m more than a little angry – time is money, and as it is time is already a premium. This is counterproductive, and I wished this sort of crap wouldn’t always happen when I’m in crunch mode.
I’m not unfamiliar with this sort of tech curve balls, but it’d be nice once in a while to just work with new technology that ‘just works’.
If this was for work, I’d be less angry, but this is for my personal project, which is already behind schedule as it is (and getting later as I write this rant).

Technorati Spiders? Arrrrgh!

I don’t know why I put this under Programming, but hey, I’m adding a link to Technorati in a vain attempt to improve my visibility. I’m trying to tell everyone:
Of course, those who really make the trek here will find that not only am I not really *that* opinionated. But at least I sound authoritative while trying to be opinionated.
Okay, here goes: Technorati Profile.
Let the spiders cometh.

ADO.NET makes developing for different databases harder

Hmm… I suddenly realized that my focus these days is development. Interesting.
I’m wondering if there is an easier way for a .NET application to natively support different databases in the same code base. For instance, when I do SQL Server, the .NET Data Provider I would use is SqlConnection. If it is OLEDB, then it’s the OleDbConnection namespace.
Now each of these namespaces have their own DataReader object, which is the primary data object I use. How can I write the application such that I can automatically choose which one to use (based on a parameter), without coding different sections for each data provider?
MSDN, here I come!