|
I'm mainly a Microsofty, used VB6, VB.NET and C#, because that was required to get a decent job where I live.
The most fun I had however was during my early Atari ST days with 68000 Assembler, MegaMax-C and GFA Basic.
Recently I took a look at Linux and tried to use VS Code, but it was no fun at all and although I got things working, I decided I'm too old for that. 
|
|
|
|
|
I love the ability to afford food with the paycheck that comes with using the languages.
|
|
|
|
|
My favorite times were when my wife (or my father before that) did the earning part and I just stayed home and played.
|
|
|
|
|
Yep, I loved C when that was what got me paid.
Delphi 6 when that was it and it's what got me in my current job where I transferred over to Java. I will NEVER rag on that language.
Currently loving Java because it allows me to sleep indoors.
Wouldn't mind going back to C, I felt really smart back in those days. All those other languages are for people who are afraid of pointers so they hide them.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
I’m begging you for the benefit of everyone, don’t be STUPID.
|
|
|
|
|
I love C as well.
Juggling pointers is the challenge and fun.
Like rivets in a building, you do them right
and the structure has the strength and solidity one can see.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
This plus the bonus of familiarity. I am really good with the languages I use, and even though I do wander out to see what else might be attractive, I'm not as willing as I was in my youth to risk the paycheck and the expertise/confidence to do more than just play.
|
|
|
|
|
I like C++ because it saves me from C. And I like C# because it saves me from C++.
Advertise here – minimum three posts per day are guaranteed.
|
|
|
|
|
Chris Maunder wrote: C#: It runs everywhere. macOS,
Java: ClassLoader is much better for plugins than C# AppDomains. So much so that Microsoft is now phasing AppDomains out (not sure how that is going to work since the app itself runs in a AppDomain.)
Perl: Been using it for 40 years. Absolutely nothing beats it for munging.
Both run everywhere I care about. And many places that I will never go.
|
|
|
|
|
Although I started with C I prefer C++ over it. Close enough to the low level but high enough to be "comfortable".
I started C# a couple of years ago, but I haven't really done so much. Still I liked it a lot.
But my big love is and will be PLC-LAD (kind of similar to assembly). I had soooo much fun in the industry automation... It was pretty addictive to see so much repercussion in the real world when programming something.
Robotics was pretty cool too, the mix of programing instructions and searching for good positions / paths make the fastest and / or most efficient execution.
The big project I mentioned in the thread of Honey about working time... I received a robot program with 11 different functionalities using more than 2500 position. I increased the functionality to almost 25 different routines and reduced the positions to something between 350 and 400. Boosted stability of the system from 70% to 98% and got the "evolved" routines around 30% to 35% faster than the original ones.
Oh man, I am proud of that time / project. It was the highest point of my career in that company. Then the company screwed it up   and I left some months after handing over the project to the customer 
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
And THAT is probably what makes a language the most fun. Working a solution and delivering real positive impact the customer can actually see and feel.
|
|
|
|
|
First job out of college was with Assembler and Fortran. They were fine languages and I learned a lot using them. But, about 4 years in ('84 or '85) I learned C and I loved that language. It gave me all the control over the machine (that I needed) as assembler and at the same time was a higher level language than Fortran.
In the mid to late '90s I picked up C++ and came to prefer it. It had most of the same advantages as C and added the object oriented paradigm into the mix.
I changed jobs again in 2000 and started working in Windows and VB 5/6 (previously my work was on mainframes and Unix workstations). I liked the rapid GUI prototyping of VB 6 but not the language syntax so much. After about 5 years of that I transferred to a different group and started C++ MFC programming. The GUI programming wasn't quite as easy but I greatly preferred the language.
Along about then I also picked up C#. I came to like that language more than C++. I found it easy to pickup and to be very powerful at the same time. It wasn't as close to the metal but I didn't need that for the C# projects I had, though most of my work was still in C++.
I'm now retired. My home system is Linux (I settled on Ubuntu) and what programming I do is in Java. When I made the Linux shift Visual Studio and C# weren't easily available on Linux so I chose Java. I've come to like that language quite a lot as well for many of the same reasons as for C++ & C#.
Along the way I learned various Unix shells, Perl, SQL, Snap (touted as an early AI language) and a few others. But, as you can tell I'm rather biased toward the curly-brace languages. I think I have C to thank for that.
|
|
|
|
|
C++ is the only language i know and use post C which i prefer not to go back to as objects are the way to go . i like C++ because it seems to permit implementation to match the syntax which seems most natural to me though the other day an exception to this occurred though i do not recall what it was now . i should stress i am not a serious well educated and wide ranging programmer w/ impressive resume or credentials so my opinions should probably hold little weight .
|
|
|
|
|
A late reply so no one will notice except maybe you, lol.
Yup, C# and Python, but TypeScript over JavaScript always. That type safety thing, lol.
|
|
|
|
|
Haskell: it makes me feel smart.
If you can't explain something to a six year old, you really don't understand it yourself. (Albert Einstein)
|
|
|
|
|
I retired and I'm trying to forget everything I ever knew about computers. So about the languages I use.
Spanish: it is pronounced the way it is spelled, unlike English. It has fewer exceptions than the other languages I know. (I'm fluent)
French: so much of English comes from French. The spelling sucks, but not as bad as English. (I'm conversational)
Mandarin: It is logical, but the tones drive me crazy. (I'm a high beginner. Give me two years)
English: English is totally illogical. There are so many exceptions. The rules for plurals have two pages of exceptions. I honestly feel sorry for my students learning English. (My native language)
|
|
|
|
|
Member 12415033 wrote: English: English is totally illogical
Definitely.
|
|
|
|
|
C#: Has good market share and will be around for a while, so I have a paycheck. I do WinForm and web development, but it's a plus that it runs on other platforms, should I need to go there. The con is that the MS C# dev team struggles to remain relevant, so 95% of new features do nothing more than make the language more complicated than it should be.
SQL: It's the language of the major DBs I use and is mostly the same. The con is that it's mostly the same across DBs ...
In the past: VB 4/5/6: At the time highly popular, which ensured a paycheck. Syntax is highly readable and was designed for rapid development -- C++ guys whined about how hard it was to create screens while I was producing entire applications that ran for years. The cons? MS stupidly killed its cash cow, and folks still whine about "go to".
For me, the major plus of any language is that it has sufficient market share and longevity to keep me employed. A lot of the details that folks list don't mean much to me -- it's just another language.
Upstream a responder listed about a dozen tech's that went the way of the dodo -- I did most of the ones listed, plus a few others. After a few decades, having to learn yet another language for a short-term assignment lost its magic. 
|
|
|
|
|
BryanFazekas wrote: For me, the major plus of any language is that it has sufficient market share and longevity to keep me employed. A lot of the details that folks list don't mean much to me -- it's just another language.
True for me also.
Although I will say I have no desire to write COBOl lambdas.
|
|
|
|
|
I like C#6 because it's clean and smart. It's easy to write code in, and quick. As a sort of RAD language, it's great.
I love C++ primarily because of the ability to do metaprogramming with it, which makes it unlike any other major language out there. Beyond that, I love its flexibility. It does take a long time to acclimate to it, and make avoiding all the gotchas instinct, but once you do you it's so worth it.
There's smoke in my iris
But I painted a sunny day on the insides of my eyelids
So I'm ready now (What you ready for?)
I'm ready for life in this city
And my wings have grown almost enough to lift me
|
|
|
|
|
The language I use is better than the language you use!
I have been around long enough to have actually used Fortran and COBOL.
Several years ago I got involved in a project that uses JavaScript. Ugh! Why do we have to use it?
Now that I am proficient in it, and with it's new features, I really like it. It is now my code of choice.
In time, I will probably be forced, under duress of course, to use another language; and the cycle will repeat.
Nothing succeeds like a budgie without teeth.
To err is human, to arr is pirate.
|
|
|
|
|
Heh, as an embedded developer (now retired) C/C++ was pretty much my only option. A lot of my career was spent on TI DSPs and something like C# was never an option.
|
|
|
|
|
Yeah, I gotta stick up for C++. People with less than 20 years experience all think C++ is complicated and weird. They are too young to remember that C++ was perfectly compatible with C's weird declaration syntax, and that a whole generation of C programmers got to learn C++ gently and incrementally. The compatibility of C++ with C and with previous C++ standards is why there is a modern language for high performance code, and we aren't all stuck with C. C++ is the reason Java and C# look like they do.
Back before github, before sourceforge, when there weren't vast code libraries online, being able to use the code you found was important, and C++ let you do that with C++ and C source code.
The reason less experienced people brag that they don't need to learn algorithms and data structures is because Alexander Stepanov created STL, the library of generic algorithms and data structures in 1995, for C++.
C++ is still where the programming world goes for high performance. Someday, maybe Rust...but not today.
|
|
|
|
|
may i please inquire what is weird about C declaration syntax . i should state i have much experience w/ C and C++ and in fact only those languages so syntax of other languages i do not know of for purposes of comparison and judgement . i find nothing weird re/ C or C++ but of course as implied i am not expert in such matters .
|
|
|
|
|
int* i,j; declares a pointer-to-int called i and an int called j, not two pointers like you'd think, because part of the type is in the declarator (the part with the name). A pointer to a function returning an int has to be parenthesized like int (f)(float v); Don't even get me started on abstract declarators. You can declare a function that takes an array like f(int a[10]) but the type of a is int. Unless this is part of a template declaration template <typename T, int N> f(T a[N]); in which case the type of a is T[10], and there's that abstract declarator thing again. Forgive me for not trying to compile these, I might have got some of it wrong. C declaration syntax, and therefore C++ declaration syntax is just strange. If C++ syntax was created from scratch, I sure hope they'd have done something different, maybe more like Pascal or Modula.
|
|
|
|
|
thank you kindly for the straight dope . re/ declarations as best as i recall the superb text by Harbison & Steele which explains such are to be performed merely by following the rules of precedence . the Kernighan Ritchie text i found confusing on this subject even they seemed confused . i compiled the code below and displayed the types for the aforementioned int a[10]. i present as a minor curiosity . they seem logical to me . may i say what i find weird/confusing/odd/uncertain/strange is utilizing const and * . thankfully i rarely utilize pointers . -Best
#include "pch.h"
using namespace std;
const char narrow_space = ' ';
void foo(int a[10])
{
cout <<__LINE__ <<narrow_space << typeid(decltype(a)).name() <<endl;
}
int main()
{
int a[10];
cout << __LINE__<<narrow_space<<typeid(decltype(a)).name() <<endl;
foo(a);
const int* p;
int const* p_;
cout << typeid(p).name() << endl;
cout << typeid(p_).name() << endl;
return 0;
}output :
13 int [10]
7 int * __ptr64
int const * __ptr64
int const * __ptr64
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
