Foo - Couple questions for Programmers

1. What are you programming in mainly these days?
2. What platform primarily?
3. Which IDE?
3. Any web programming and on what web server?
4. Your favourite compiler?

1) These days, mainly Matlab and Python, but I am yearning for some C++
2) Unix
3) Nothing I do requires an IDE, so it's a text editor plus a compiler.
4) Nope
5) G++, works, does what I need

1)High level Assembler for z/OS
2)z/OS (version 1.9)
3) ?
3b) Websphere, and generated java
4) Compiler for Rexx on Z series

1)High level Assembler for z/OS
2)z/OS (version 1.9)
3) ?
3b) Websphere, and generated java
4) Compiler for Rexx on Z series

What's that... your own-developed web box?

actually should be generated HTML. . .
all this new fangled stuff is confusing

1. What are you programming in mainly these days?
2. What platform primarily?
3. Which IDE?
4. Any web programming and on what web server?
5. Your favourite compiler?

1. Java - web apps and legacy app integration.
2. It's Java so the platform doesn't matter.
3. IBM RAD7 - not my choice.
4. Yes, WebSphere.
5. Favorite compiler? That's way too geeky to even care about.

1. COBoL & ALC
2. MVS
3. ?
4. No
5. I know someone with a really nice PC that he games on a lot.

5. Compiler? d'oh. I have no choice in the matter. Whatever is on the box is what we all use.

1. COBoL & ALC


I didn't know you were a Cobol programmer... that was my primary language when I started out, and it still would be if the rest of the industry wasn't so turned off by anything that was around more than 10 years ago.

My first major project was written in Micro-Focus Cobol to run on XT compatible systems... and I have written several MVS programs as well.

I still yearn for the days of Cobol with the nice well defined data environment... ;)

It seems so long ago, but I would love to be coding Cobol again.

1. What are you programming in mainly these days?
C#

2. What platform primarily?
Windows Server

3. Which IDE?
Visual Studio 2005 Team Edition

3. Any web programming and on what web server?
Almost exclusively. The code I write is used in ASP.NET web applications. IIS 6 and 7

4. Your favourite compiler?
I can't claim to have a favorite, but I use the Microsoft one because it's basically the only option for the work I do.

Edit: In the past, I'd have answered this with the appropriate answers for developing php applications for LAMP using Dreamweaver

1. C#
2. .NET Runtime 3.5
3. Visual Studio 2008
3. IIS
4. GCC 3.2

1. .NET (C#)
2. Web
3. VS2008
3. Yes, IIS front, plus app servers in the middle and big honkin SQLServer dbs with webservices and stuff all intermixed
4. compiling by hand is sooo university. We do use CruiseControl.NET and msbuild files though....

I didn't know you were a Cobol programmer... that was my primary language when I started out, and it still would be if the rest of the industry wasn't so turned off by anything that was around more than 10 years ago.

My first major project was written in Micro-Focus Cobol to run on XT compatible systems... and I have written several MVS programs as well.

I still yearn for the days of Cobol with the nice well defined data environment... ;)

It seems so long ago, but I would love to be coding Cobol again.

There are some applications that will still be around for the foreseeable future. I recall the cartoon I about 9 years ago, where some people in the year 9999 had brought some guy out of cryogenesis, and they said to him... "excuse us, but we saw here that you know CoBOL".

Nice to see some mainframers. I am a z/OS assembler programmer. These days, I am doing development on USS and using the makefile process. Not bad.

My development is in assembler but I do code Cobol, C, and PL/I test programs.

I'm not coding anything these days but back in my prime...

1) C++ for main apps. Perl for minor stuff and PHP for the web interfaces.
2) UNIX.
3) None, good ol' pico.
Please note you wrote #3 twice...
3) Apache, but only for web interfaces to the main app, when required. I hate web programming.
4) G++.

I've used the MS Visual thingies for Basic, C and C++. They are nice once you learn to use the darn ultracomplicated interface. Windows programming and UNIX programming are very different worlds.

Pretty much Linux / Windows with MySQL backend, PHP for server code.

I do most of my development work with VBA in Access.....make access do all sorts of things its not originally designed to do. Moving into being a SQL developer supporting an Oracle Financials application. Have done VB, Foxpro, Visual Foxpro, and Clipper. All Database applications with either native mdb files or MS SQL Server.

0. C/C++
1. Unix
2. IDE is for wussy. I use vim/gdb/ctags/make.
3. nope. When I need a web page I hand code it in vim.
4. gcc/g++.

1. COBoL & ALC
2. MVS
3 . . .

I knew there was a reason I liked you

1. C, Java, Python
2. Any host platform but usually SSHed into Unix
3. vim, although I wrote my own text editor using ncurses I sometimes use.
4. None, I only enjoy lower-level programming.
5. gcc with -Wall -ansi -pedantic

1. What are you programming in mainly these days?
2. What platform primarily?
3. Which IDE?
3. Any web programming and on what web server?
4. Your favourite compiler?

1. C++, Java or some scripting language.
2. Windows.
3. Bloodshed Dev-C++ or Visual Studio Express C++ (C++), Eclipse (Java) or Notepad (anything else)
4. Back in my last job, I did some basic HTML/CSS programming on a standard UNIX server.
5. GCC

I am an etl programmer. This thread is almost not applicable to me.

1. Datastage at the moment. Though it is more of a visual etl tool.
2. Windoze
3. Notepad at most.
4. I have used html in the past for a website I had. Booooorrrriiiiiinnnnngggg
5. Datastage :p

Anyhow, I am now looking at learning either more on database design or another etl software package.

1. Perl, C
2. RHEL, FreeBSD
3. vim
4. very little, custom fork of apache
5. N/A

1. C, C++ and Cocoa/obj-c recreationally; perl at work.
2. NDS homebrew, OS X, Unix
3. Unix is an IDE :P XCode/IB for Cocoa stuff
3. As little as possible/apache/whatever language suits the project
4. Is there even a choice these days? gcc

1. What are you programming in mainly these days?
2. What platform primarily?
3. Which IDE?
3. Any web programming and on what web server?
4. Your favourite compiler?

1: C#
2: Windows.
3: VS 2008
4: No real web programming, just basic stuff going to a box running IIS 7.
5: Favorite current compiler, depends. Favorite historic compiler, Symantec's C++ compiler.

I am an etl programmer. This thread is almost not applicable to me.

1. Datastage at the moment. Though it is more of a visual etl tool.
2. Windoze
3. Notepad at most.
4. I have used html in the past for a website I had. Booooorrrriiiiiinnnnngggg
5. Datastage :p

Anyhow, I am now looking at learning either more on database design or another etl software package.

Come on DJ, no one writes it that way any more. But since you have such a nice avatar, I wont take this any further. :thumb:

C# guys, how are you finding it.. Like it / loathe it? Have you always been programming Windows?

C# guys, how are you finding it.. Like it / loathe it? Have you always been programming Windows?

Its decent. I don't program for a living, but I do write a utility or two, and VB .NET/C# both do the job well, and are not any slower than other languages, although a good assembly programmer hand tuning all routines could squeeze out a 1-5% speed boost.

It also gives a dirty feeling, mainly because .NET applications are not really portable off the Windows architecture like Java is. So, if I go to write a Mac version of my utility, I'll have to pretty much rewrite the thing completely.

Its decent. I don't program for a living, but I do write a utility or two, and VB .NET/C# both do the job well, and are not any slower than other languages, although a good assembly programmer hand tuning all routines could squeeze out a 1-5% speed boost.

It also gives a dirty feeling, mainly because .NET applications are not really portable off the Windows architecture like Java is. So, if I go to write a Mac version of my utility, I'll have to pretty much rewrite the thing completely.

Just a comment - unless someone is incredibly good with assembly (not good, but an expert who codes only assembly), you are not going to beat by much the libraries. In the past, sure, but not after 20+ years of library building. This is an antiquated idea - it once was true.

The biggest achievement is if you can prevent the libraries from bringing in the kitchen sink - i.e. bloatware. Take a look at "Hello World" - and the size of the program. Back in the Jurrasic period, I could have written that in assembly as a com with perhaps less than 100 bytes.

But of course, we have so much memory and so much power, it really doesn't matter. I know used an interpreted language because it is plenty fast enough, and compiled over interpreted just isn't that important honestly, and an interpreted language lets you do things that are much more interesting, with less work.

You tend to tweak with assembler in routines that you are going to use a lot - or when working in environments where speed is critical. I used to work in digital signal processing where the total life of the program was measured in less than 20 milliseconds. In that environment, it is critical that everything is efficient. Generally speaking though, if your routine interacts with a disk or network, you don't bother since accessing these medias are so slow that whatever else you do appears to be instantaneous compared to this.

But I would generally not waste my time tweaking a C##, if I wanted it super fast and cared about 1 to 5 %, I wouldn't use that language.

C# guys, how are you finding it.. Like it / loathe it? Have you always been programming Windows?

Before I got this C#/.NET/Windows gig, I was doing performance-critical development on Solaris and Linux using C. Despite that (or perhaps because of it), I really do enjoy the C# language, as well as the .NET runtime. It's still has the familiar C-style syntax and structure, but high-level enough that you don't get bogged down in details. C#.NET also has a very nice set of standard libraries.

As far as I'm concerned, the main downside to C#/.NET is it's platform-specific nature. I suppose there is the Mono project, but it lags behind Microsoft's efforts by at least a generation.


You tend to tweak with assembler in routines that you are going to use a lot - or when working in environments where speed is critical. I used to work in digital signal processing where the total life of the program was measured in less than 20 milliseconds. In that environment, it is critical that everything is efficient. Generally speaking though, if your routine interacts with a disk or network, you don't bother since accessing these medias are so slow that whatever else you do appears to be instantaneous compared to this.

But I would generally not waste my time tweaking a C##, if I wanted it super fast and cared about 1 to 5 %, I wouldn't use that language.

Exactly. There are very few places in the industry where the sort of cycle-counting I did back in the day is important enough to warrant substantial developer time. The rapid development and program stability that's easily attained when working in C# (and other languages at a similarly high-level, such as Java or Python) are far more important.

Before this thread dies I thought I would just add, Java rules. ;)

1. C++
2. Windows 7
3a. None
3b. No
4. Whatever happens to be in our standard build environment (currently "Microsoft (R) C/C++ Optimizing Compiler Version 15.00.30729.165 for x64")