Early Thoughts on Developing for Windows

I didn't completely escape the clutches of Microsoft when I found my new job. This new place does some development for windows CE, it turns out. I've been struggling through some build issues with some code for the last couple days, and my early impression of developing for windows are not good. I'll admit possibly a little bias, but I'm really trying to keep an open mind. Really.

First of all, the command-line tools are severely lacking in Windows. My mentor here is showing me all kinds of command-line tricks to get stuff done, which I really appreciate, but cmd.exe is awful, copy-n-paste is weird, you can't resize the window by dragging the edge. Useful commands like which, grep, find, just don't exist. Agony. I know about cygwin, but I've never been able to integrate that well with the rest of windoze, and especially not with Visual Studio.

My second complaint is online help. MSDN appears to be quite voluminous, and somewhat helpful actually, but if you run into something that's not in there, all you can find are forum threads where developers make uninformed suggestions to each other and sometimes they happen to find something that works. It's not their fault, the source code for all their tools is secret, so it's really hard to know exactly why the build tools do what they do or the compiler says what it says. The open source folks theoretically can find out exactly why a tool is behaving weird, and with enough people on the internet you can usually find someone who has the correct explanation for the exact wonky behavior you are seeing. Not always a fix, but at least an intelligent explanation that is much more convincing than, "I don't know, have you tried service pack 2?"

OK, back to having a good attitude and plowing ahead.

Comments

Anonymous said…
Still using Command Prompt? Use PowerShell.

http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx
May 18, 2009 at 2:49 PM
Timothy Molinari said…
http://gnuwin32.sourceforge.net/packages.html

All the GNU-tools you need, without messing with cygwin.
May 19, 2009 at 12:26 AM
Bryan said…
OK, PowerShell is neat-o, I'm sure, but I just don't have the will to learn a whole 'nother set of shell syntax. All reports seem to indicate that for interactive use (my complaint here) it's not much better than cmd.exe.

Now gnuwin32 is cool. It's really nice to have some familiar commands back. Doesn't fix copy-n-paste or window resizing either though. Thanks, Timothy!
May 21, 2009 at 2:35 PM
ustunozgur said…
Maybe this will help:

http://sourceforge.net/projects/console
May 26, 2009 at 1:13 AM
Bryan said…
I finally took a second to try console out. It's easily resized, you can easily copy-n-paste, the fonts are easy to change, and it even does transparency. Very nice. I've realized that the big thing that I'm missing is readline functionality. In other words, I need my emacs shortcuts for navigating command history and editing commands.
June 3, 2009 at 10:15 AM
Sam said…
Developing on Windows is bad enough, but what is even worse is developing for CE. Some solutions exist to the problems you have been having (several of which have been posted on comments above), but often times these solutions are not available for CE. Which leads to the wonderful world of writing software the reinvents the wheel over and over again.

Not sure if I or the other dude is the mentor you are referencing.
September 11, 2009 at 8:56 AM
Bryan said…
You are the wince mentor I was talking about, Sam, don't worry.
September 13, 2009 at 7:23 PM
Post a Comment

Popular posts from this blog

SystemVerilog Fork Disable "Gotchas"

This is a long post with a lot of SystemVerilog code. The purpose of this entry is to hopefully save you from beating your head against the wall trying to figure out some of the subtleties of SystemVerilog processes (basically, threads). Subtleties like these are commonly referred to in the industry as "Gotchas" which makes them sound so playful and fun, but they really aren't either. I encourage you to run these examples with your simulator (if you have access to one) so that a) you can see the results first hand and better internalize what's going on, and b) you can tell me in the comments if this code works fine for you and I'll know I should go complain to my simulator vendor. OK, I'll start with a warm-up that everyone who writes any Verilog or SystemVerilog at all should be aware of, tasks are static by default. If you do this: module top; task do_stuff ( int wait_time); #wait_time $display ( "waited %0d, then did stuff" , wa
Read more

'git revert' Is Not Equivalent To 'svn revert'

I just learned that if you have some changes in your working tree that you want to get rid of, you don't type 'git revert' like you might guess. No, that's what cvs, subversion, mercurial, and bazaar (to name a few) use revert to mean, but not git. With git, revert is used to undo actual commits. Thankfully, you can undo your revert with another 'git revert', I just learned. So let me repeat to be clear, if you have changes to your working files that you want to abandon, DO NOT do this: git revert HEAD That will undo your last commit. Do this instead: git reset --hard HEAD I'm glad I have that straightened out now. I'm wondering if /etc was really a good place for me to start out playing with git. UPDATE: Nearly two years later and I'm still getting comments on this. I'm glad I've been able to help people out this way. The discussion in the comments is good, and one thing I'd like to point out is that I now always use
Read more

Put /etc Under Revision Control (with git)

UPDATE : There is a much easier way now : sudo aptitude install etckeeper There, now etc is under revision control and changes are automatically committed with a helpful message after you install new packages. Thanks for the tip, Marcelo! Read on for the original blog entry. --- I put my /etc directory under revision control. I used git. It's awesome. Not that I think I'm going to wholesale copy my /etc from one machine to another, nor because I'm going to branch my /etc directory and spend weeks developing some cool new feature (whatever that would look like...) and then merge it back into the main branch. No, it's mostly because I like the idea of having the big "undo" option that having things under revision control provides. Having to commit changes and write check-in comments when I make changes helps me stay more organized too. It's never good when I go in willy-nilly to make a "quick change" to some configuration file. I r
Read more