I've come from a C/C++ background and C# is definitely the first language that I've been happy to move over to with both feet. Even Java didn't do it for me - I guess because I could never quite remember some of the subtle contructs. C# solves this - it is C++ but with old requirements removed (header files etc.), and well designed facelifts ("using <namespace>") from the ground up.
I still found it unconfortable for a while not having to delete (or delete) objects all the time. Particularly where you feel you are bloating the heap all the time with arrays of 100's of small objects, but I am receving councilling on this as we speak .
Here in Tempe AZ I must admit I enjoy the sunshine - mentally it just automatically makes you cheerful as long as the A/C keeps working.
HOWEVER writing in August, this is a little past the peak of the Cooked Smog/Ozone season. The brilliant sunshine creates Ozone and other nasties from the smog - I've always been quite healthy but I notice an occasional cough on the worst days, sigh.
Therefore be thankful for your rain-washed air ! You can always visit a tanning booth but it is more difficult to filter your air.
One of the things we try and do is ensure that the environment an article is written for is reasonably accurate. Thanks to Marcie we now have a system that goes through and takes a quick peek at what environment strings (such as Win9x, MFC, .NET etc) article have so we can standardise.
Some of the better ones we've found:
* Bamboo (*Programming* environment, not your backyard's environment)
* Wasabi (I wonder if there's a Wasabi.NET version coming out)
* Article (really? It's an article? Awesome!)
There's always a point in a port where you look at the hundred and one utility functions you've written to supplement the rolls of string and ducttape you've used to hold your old system together, and you think "Are these really necessary?". One by one you capitulate and move them into your new system. Sure, they are now cleaner and more elegant, and they may even get actual comments and a dignified place in the namespace, but they still have the "Scotch" brand to them and it still hurts knowing that a good portion of your week will be spent translating Language A crud into Language B crud.
But I have to say that the number of lines of code I'm having to write in C# is going down an easy 30%. Nice.
Wow, the Big Rewrite(tm) is actually happening!
I remember you telling me about the Rewrite when we were eating pizza in LAX in 2001, and you were enumerating all the ways in which the buggyness of the pre-release ASP.NET was making you hate life
Again, a saturday afternoon where I should be outside in the sun instead of indoors in front of a monitor. I'm guessing this brief but messy internal war of desires is going to end in bloodshed. And with an empty chair and dark screen.
The CodeProject team is splitting into waring factions. One side has ramped up demands to the ridiculous. "We want a design document", and "What are the milestones", and lately - a more disturbing trend with "We want a bug tracking system". It's cruel and unreasonable demands such as these that threaten to tear apart the team and raise the possibility of two incompatible versions. Even such comprehensive reassurances as "she'll be right" and "we'll cross that bridge when we come to it" aren't having the expected affect.
It's dark days like these that one needs to find comfort in the simpler things in life. Like Halo.
But you know when the truth is told,
That you can get what you want or you can just get old,
Your're going to kick off before you even get halfway through.
When will you realise... Vienna waits for you? - "The Stranger," Billy Joel
We have a timeline. We have milestones. We have Marcie firing up Microsoft Project and making us use agenda's for meetings. This is all getting serious.
Currently the basics are now done and it's on to just grinding out the code. The initial rewrite will be based on the current function set with enhancements and fixes. Enhancements mainly in the form of generalising what we have and optimising the system as a whole. Fixes will be mainly bug and security fixes, as well as cleaning up the inevitable kludges that crept in.
I've also found a couple of huge SQL errors that, surprisingly, don't actually affect the site nor what is displayed. Pretty cool. Pretty lucky. Mainly these errors are to do with things we have setup for future applications, but nonetheless they are being used and I'm sure someone, somewhere got a page that was just all plain wrong and sat there scratching there heads over it. Sorry.
We are reworking the way we present and catalogue articles. What you will see in the end is a simpler method of browsing articles that gives you control and clarity (should I (TM) that one?). It will also mean the search works better, the list of top articles is more on topic, and that no more VB articles appear in the MFC section.
Comments so far:
1) I'm avoiding pretty much all the demoware features of ASP.NET. They work great in simple situations but the amount of code and time required to squeeze them into the shape we need simply isn't worth it. What if their implementation changes? What if they are deprecated for yet another sexy new technology? Each time I see a demo of the latest up and coming advance in ASP.NET I hear the words "and this requires no coding!". That sends a shiver down my spine.
2) Working in .NET is so, so nice. Seriously. Sometimes.
3) I want to slap the peson who chose not to allow intellisense and colouring in code blocks in ASPX pages. Stupid, stupid person.
Currently working on:
- Content Management system.
- Account Management.
- Newsletter system. Boring for you guys, fundamental to us since
it taps into so many other systems.
- Marcie is working on a new piece of the CodeProject puzzle that
many have been screaming for for ages. It's looking sweet.
Complete to alpha stage:
- Page framework
- Data access layer
- Data structures and Database schema
"- Marcie is working on a new piece of the CodeProject puzzle that
many have been screaming for for ages. It's looking sweet."
So what is it??!! Spill the beans!
You know one thing that *I* have wanted for ages (but kept forgetting to ask for) is a feature where you can send in C# (or whatever language) tips. For those moments when you find some new feature in .net and say to yourself 'oh that's cool, i wonder if anybody else has found that'... you could just write it up in a paragraph and post it to codeproject. Then you could have a little 'tip of the day' section on the home page where you select a random one. It'll be like mini-articles for people with less time to write a full fledged article!
Disclaimer: Because of heavy processing requirements, we are currently using some of your unused brain capacity for backup processing. Please ignore any hallucinations, voices or unusual dreams you may experience. Please avoid concentration-intensive tasks until further notice. Thank you.
Last Visit: 31-Dec-99 18:00 Last Update: 19-Jun-18 1:29