• Welcome to the new COTI server. We've moved the Citizens to a new server. Please let us know in the COTI Website issue forum if you find any problems.

What Programming Languages do you use?

What Programming Languages do you currently code in?


  • Total voters
    96
After a few months of trying to do what I'm not really made to do, I had to face the fact that I don't have the brain cells to learn two languages at once. Since work needs Perl, and I was hired on to learn Perl, then Perl it is. Go still has a lot going for it, but I'll have to wait.
 
After a few months of trying to do what I'm not really made to do, I had to face the fact that I don't have the brain cells to learn two languages at once. Since work needs Perl, and I was hired on to learn Perl, then Perl it is. Go still has a lot going for it, but I'll have to wait.

It helps to understand one language first, then you can approach the other language as a "how do I write X in Y". Like "How to do write Perl in Python".

Obviously there is going to be an impedance mismatch, but it's closer than not.

Mind, I segregate "learning the language" from "learning the libraries", though many conflate it. But to a new learner, they should be distinct.

Language is syntax and runtime. Libraries are just the utilities built on that syntax and runtime "How do I read a file" is a library problem (though technically not true as this was a first class concept in older languages like Fortran, BASIC, and Pascal).

While productive, Perl is a crummy language to learn first. It has no rigor. "There's more than one way to do it" can go too far, especially for a beginner.
 
It helps to understand one language first, then you can approach the other language as a "how do I write X in Y". Like "How to do write Perl in Python".

Obviously there is going to be an impedance mismatch, but it's closer than not.

Mind, I segregate "learning the language" from "learning the libraries", though many conflate it. But to a new learner, they should be distinct.

Language is syntax and runtime. Libraries are just the utilities built on that syntax and runtime "How do I read a file" is a library problem (though technically not true as this was a first class concept in older languages like Fortran, BASIC, and Pascal).

While productive, Perl is a crummy language to learn first. It has no rigor. "There's more than one way to do it" can go too far, especially for a beginner.

Since almost any interactive in C/C++/G/G++ requires stdio.h/stdio.lib, that file handling is in stdio is pretty much treated by every one of the dozen books I've used on that clade as not really being a library call, but the library call as mandatory boilerplate..

Several others have similar "called so often that people forget they are library calls rather than integral." Especially casual programmers like me. (I don't do pretty. I often brute force. I use suboptimal languages because I know them. Of late, QB64, python, and Javascript. Haven't touched C/C++ in a few years.)

The board's code has many of the SSS header/library calls buried inside page-type headers, which are called from the drawing code.
 
In QB64, is there a way to make it larger than 80 columns wide ? I have a hard time seeing the text.

Thanks.
 
In QB64, is there a way to make it larger than 80 columns wide ? I have a hard time seeing the text.

Thanks.

Yes. Options -> Display (or alt-O alt-d)
You can set the width (in characters) height (in text rows) and size (in points) of the fixed width display font.
 
Ah, it did an update and unchecked 'ask me'. All fixed. Now to just learn what this version of BASIC is different than AmigaBASIC and Apple ][+ BASIC.
 
Ah, it did an update and unchecked 'ask me'. All fixed. Now to just learn what this version of BASIC is different than AmigaBASIC and Apple ][+ BASIC.

It reimplements M$ QBasic, and adds graphics support and 64-bit variables.
 
I'm purely a BASIC coder, and not very sophisticated. I started out in Applesoft, lo these many years ago. Then I went to PC computers and stopped coding for a time. Then I discovered QBasic and wrapped my head around procedural programming and not having to screw around with line numbers. Then Microsoft decided to drop DOS and unless I used an emulator I was out of coding again.

Then I discovered QB64 and have been playing catch up ever since. The new tools that QB64 brings to the basic table have me considering taking another crack at coding a ship vector ap that never seemed to pan out before...
 
I'm purely a BASIC coder, and not very sophisticated. I started out in Applesoft, lo these many years ago. Then I went to PC computers and stopped coding for a time. Then I discovered QBasic and wrapped my head around procedural programming and not having to screw around with line numbers. Then Microsoft decided to drop DOS and unless I used an emulator I was out of coding again.

Then I discovered QB64 and have been playing catch up ever since. The new tools that QB64 brings to the basic table have me considering taking another crack at coding a ship vector ap that never seemed to pan out before...

The language that inspires you to code more in your chosen domain is the best language for you!

If you want to have others read and use your code, we have a GitHub repository to make it easier. PM me if you have any questions.
 
Forth is an interesting challenge. I learned it when I found postscript is forth, and wrote a .ps file to output hex paper by generating the hexes. That, and printing source code in a 6 point font in a 4-up per page so I could read my whole source file at once.
 
I'd *heard* of forth from another Citizen, AGorski, when I was a teenager. I learned enough to be a hazard when I discovered that a Forth REPL (read-evaluate-print loop) was used as the boot PROM shell for Sun workstations. And the best description I can give for SmallTalk is "Object-Oriented Forth". SO it saved me some pain in understanding and maintaining someone else's magnum opus in SmallTalk.
 
Back
Top