|
I'm a little grumpy and have read way too many "tech X sucks" (and I'm responsible for some of them).
So what do you love about the languages you use?
I'll start.
C#: It runs everywhere. macOS, Linux, Windows, Raspberry Pi's, in the browser via WASM, on mobile devices, you name it. Literally every platform I support I can write code using C#. The type safety and static checking is amazing, the syntax (generally...) very clean, and given it's basically the grandson of C, the syntax is like my Mother Tongue.
Python: Again, it runs everywhere, and it often runs everywhere because it's built in by default everywhere. It's interpreted so awesome in notebooks, great to run on the command line to quickly test something, and there's just so, so much code out there. Sure the indents take getting used to, but no brackets certainly cleans the place up.
JavaScript: I love it because I deploy it one: on my server. It then runs everywhere there's a browser and I never have to worry about hardware or libraries or graphics cards or harddrive space. If there's a bug I upload a new version and everyone, immediately, is also updated.
What about you lot?
cheers
Chris Maunder
|
|
|
|
|
C#'s async/await is a billion times easier to follow and reason with than the chained callback hell of java on android.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
They have different purposes. Callbacks for heavy background processes, async/await - a simple way to avoid blocking your main process/interface thread.
Advertise here – minimum three posts per day are guaranteed.
|
|
|
|
|
Hard to put a finger on it, but C# was the porridge that was just right, after: assember, Autocoder, RPG, Fortran, Cobol, PL/I, Pascal, dBase I, II, III, IV, Clipper, FoxPro, Visual FoxPro, VB, VBA, Access, Delphi, Paradox, C++ ... and some names I can't remember.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
You know how with some things you can tell that a committee was involved in the design?
That every member of the committee had different priorities, and insisted that they weren't approving it unless at least some of what they wanted was in there?
And as a result, you get something that does the job, but doesn't make life easier for anyone? The Fiat Multipla for example. Or Vista.
C# isn't that. VB is. C++ very, very much is. Javascript is as well.
But C# (although it is heading that way) was designed to be easy to use, consistent, and hard to muck up as well as extremely powerful because it was solidly integrated with a (pretty much) consistent, solid, and flexible framework.
It's still a damn good language, but the ex-C++ people on the committee appear to be directly things a bit too much and it's losing sight of why it was designed in the first place.
And as a first language I'd still say it's the best for beginners because it just refuses to assume you know better that it does ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Hear hear! -- Except with the caveat that I use C# v3.
C# v1 and .net v1 should never have left the lab and seen the light of day. Supporting v1 continues to be a thorn in my side.
|
|
|
|
|
OriginalGriff wrote: C# isn't that.
Somebody sure got something wrong with allowing linq to be used for database calls.
|
|
|
|
|
I simply don't use Linq at all.
Database access is one of several things which any developer who is adept is better off not using what has been built-in tacked on.
|
|
|
|
|
I'm pretty much C# and SQL only these days -- and Windows only, so I don't care about "runs everywhere". If you consider Regular Expressions to be a language, then I'll throw that in as well. How about XPath and XSLT?
In any case, C# kinda hosts the others anyway.
C# does what I need. And that also includes implementing what might be considered domain-specific languages of my own design.
(My boss has again -- like just a half hour ten minutes ago -- stated that he thinks I should learn Python. Most fans of Python seem to completely ignore its limitations. Undoubtedly it is the right tool for some jobs, but not for any jobs I have at the moment.)
|
|
|
|
|
Because I'm working on embedded a lot lately;
Assembler:
PRO: Because it's fun to write, fast and bare metal
CON: I'm working with several different processor and they each have their own version of assembler and therefore require different assemblers.
C:
PRO: Runs on pretty much all platforms, it's fast and using sdcc compiler you don't need but a single compiler for many processors.
CON: None really
Give me coffee to change the things I can and wine for those I can not!
PartsBin an Electronics Part Organizer - An updated version available! JaxCoder.com
Latest Article: Simon Says, A Child's Game
|
|
|
|
|
CON: You might run off the end of th*&^$*#*^#*^%#*$@&#*^%
|
|
|
|
|
Yeah that does happen and no amount of cursing and gnashing of teeth helps.
Give me coffee to change the things I can and wine for those I can not!
PartsBin an Electronics Part Organizer - An updated version available! JaxCoder.com
Latest Article: Simon Says, A Child's Game
|
|
|
|
|
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.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
