Skip to main content

Version 1.0 - WinForms Blues

I was wondering how long it might take for these types of comments to start rolling in, if at all.

DotNet is still a very young product, despite all of the experience MS may have gleaned from its other Dev products. One comment on Rick's blog was "pain=opportunity" but this is where developers really have to start getting tougher.

While we're all waiting for the next generation interface, a lot of us still have to build Windows-based applications. If the latest and greatest tools don't make it easier, then the existing tools that have served us well in the past (read VFP for me) will continue to be the tools of choice.

Are they the most current? Maybe not but the ongoing development on these products by MS shows that there is some intelligent reasoning as to why VFP wasn't thrown into the whole DotNet package and why DotNet may not be the only solution to every problem.

Do they still run that "who can build an app the fastest" contest at the conferences? Who has won recently?

Interesting way to look at it but : Latest + Greatest != Fastest+Best

I'm sure they'll get it right (or the third party market will) but it certainly doesn't make for an appetizing reason to make the switch for all existing apps. Best rule is still : find the best tool for the job that will get it done right the first time and allow for changes the next time.

Rick Strahl's WebLog

Comments

Post a Comment

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com
1 comment
Read more

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...
Post a Comment
Read more

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...
12 comments
Read more