Skip to main content

Koziol: The fear is the .Net Framework itself.

John continues his piece on the "World of Tomorrow".



While it is definitely pro-fox, consider the contrast between Part III, where he discusses how tough the DotNet framework can be, to Part IV, where he talks about the difference in community.



Now,he doesn't note DotNetNuke, which is a free (as in beer) framework for content management and there are a lot of free or low-cost how to's for DotNet. (VFPx isn't the only tool in the CodePlex)



Now, John isn't just another FoxPro developer spilling his gripes - he did work for Microsoft at one time - and as he says , over the last 18 months, he has led and worked with various development teams on DotNet projects. Frightening?



Sounds like it. " It is so, so easy to "blow up" Visual Studio apps", " A small behavioral tweak may cause 2 or 3 developers days to complete." - maybe this is why existing Fox developers have moved to creating frameworks (like Milos and MereMortals) to make it easier.



Rick Strahl wrote an article a while back about how it's useful to understand the underlying approach when attempting to build useful code - John makes the point that while it's nice to know all the cool underlying things (as evidenced by the Hacker's Guide), you don't HAVE to know it to get it working.





I've worked quite a bit in DotNet but I am not, by any means, an expert. I recall at the first DevTeach, someone made the comment that it would take a huge amount of code to write a function in DotNet that was similar to a FoxPro function. (I can't for the life of me remember the function)



Within about an hour, a DotNet developer came back and said "what do you mean? Just use Regular Expressions." While correct, I think they missed the

point - a single function that has been around in VFP for years and that is fairly readable would be replaced with a Regular Expression string, which is tough to even start to understand. (What does \b\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\b mean?)



As John noted -
Things that were simple are now inordinately complicated. - will they get easier with Orcas?



I hope so...How are you dealing with the differences with other development environments? Have you found a easier programming environment?





Powered by ScribeFire.

Comments

Anonymous said…
Absolutely.

Python.

Simple, clean syntax. Extensive library. Fairly easy transition from Foxpro.
Garrett said…
I think it's a regexp for validating an IP address, but it's not nearly complete enough. :-)
Gonzo said…
Andrew are you saying it's scary that I manage .Net projects? Should I be insulted? :-)

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

Who Wants To Be Logical? I Do! I Don't! (with Claude)

In my book, Towards Consciousness, I explore PET , a theory that attempts to explain consciousness and possibly how it might apply to AI. As part of the conversations with AI series, I've included this conversation with Claude.AI in which we were talking about something very different and yet the conversation redirected itself back to PET. For the record, there is no such thing as "Colfsity". A It's interesting to me that people want to proclaim their distinction from being rigid and unlike machines, yet they also complain that the "best" people keep a rigid schedule, regular routines and logic understanding of issues. That's a perceptive observation about a real tension in how people think about themselves and what they value. There does seem to be this paradox where rigidity is simultaneously rejected as "robotic" or inhuman, yet praised when it appears as discipline, consistency, or logical thinking. I think part of what's happening is t...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...