If you're a C.S. person, it's likely that you are a digital person, and you will most frequently use the oscilloscope to troubleshoot digital busses. Don't skimp on the channel count, go for 4! For things like serial busses (RS-232, SPI, I2C, etc.) you will want to watch clock, tx, and rx simultaneously. For a parallel bus, you can get your clock, chip select, and a couple addy or data lines. For most problems on your board, you can get by with the scope instead of an expensive logic analyzer if the scope has enough channels. The scope is better than the logic analyzer in many ways as you can watch for issues with noise, bus contention, etc.

Every engineer has their bias, I say go for Tek! LabVIEW and DAQ are cool for repetetive measurements under automation, but there's just no substitute for a physical front panel interface with knobs and buttons when you just want to spend a couple minutes looking at a few levels.

Try to find something with Ethernet or USB. Many of the used scopes on ebay have the old 3.5" floppy, and that becomes annoying when noone in the office remembers floppy disks and you need to get a plot off the scope to send to an FAE! :)

Maybe this is in the works. Just read that they are getting the ARM core.
http://www.eetimes.com/electronics-news/4204863/Microsoft-takes-ARM-license

Obtaining the leading processor core for mobile phones positions them well to create a mobile phone, don't ya think? :)

Most electronics companies where I've worked or consulted use LabVIEW for automated product testing.

You can download an eval copy from http://www.ni.com/labview/optin/trylabview

LabVIEW is graphical programming. I'm still loyal to C/C++, but all those text languages are so 20th century! ;) Until we achieve natural language programming, LabVIEW is as good as it gets for 21st century.

Putting humor aside, LabVIEW apps are very simple to write and deploy. The Application Builder allows you to create an EXE from your app and bundle it with the runtime in a nice Windows installer that you can send to your customers.

I've seen some suggestions on here for PowerShell. One limitation of DOS batch files is the inability to interact directly with .NET. Anyone on modern Windows should learn .NET since it is the preferred framework now for that OS. PowerShell can give you the .NET access, but LabVIEW will have a much quicker learning curve if you ever have the urge to delve into .NET.

The LabVIEW forums are very active, and the community gurus provide quick turnaround on support questions. For long-term maintenance of your test app, you're likely to find more engineers in the Test&Measurement arena that use LabVIEW versus DOS.

Good luck in your choices!