|
I don't have a main language......
I do not fear of failure. I fear of giving up out of frustration.
|
|
|
|
|
C# is my main programming language, and it's the best I've ever used. But sometimes I reached its limits, and I'd like to see Aspects integrated into the language (I know there are some third party tools trying to achieve that).
Sadly, Microsoft prefers to integrate other features geared towards convincing script kiddies to use C#, and recently even C programmers (C#7 feature of e.g. ref int type), thus encouraging to write C or JavaScript when it actually ought to be C#...
|
|
|
|
|
|
That's because a decent craftsman knows to invest in decent tools.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Quite love C++. The language is amazingly broad making it more interesting.
|
|
|
|
|
I'm programming in C# at home but doing C at work. C laid a good programming foundation for me and it made the transition to C# a breeze. Only thing is that I'm starting to enjoy C# more than C. I fear that I will get a cut in pay if I move.
|
|
|
|
|
I have the luxury of using whichever language I prefer for projects. I typically use:
C# for projects requiring GUIs
C++ for projects that require high performance and/or exact control over a structure (at the bit level)
C for hardware interfacing or O/S kernel programming
Python for quick-and-dirty scripting
As always, it's a matter of choosing the "best"(*) tool for the task at hand.
(*) Reasonable people may differ on the meaning of "best" in this context
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
It's about time I started dabbling in Go, though.
|
|
|
|
|
Asday wrote: It's about time I started dabbling in Go, though. What are you waiting for? Go!
|
|
|
|
|
Doing my best.
Need to get my motivation back though. Spending a lot of evenings just vegging out.
|
|
|
|
|
The Holy Grail!
I've got my fingers in several languages and I find rewarding aspects in each. I do appreciate C# a great deal but really am looking for the emergence of a Holy Grail of coding languages to emerge in the future that will consolidate the strong points of each of the others. And not just the language but the IDE's as well that can take up some of the more tedious work and allow us to think through the code in a more elegant manner.
Till then, I'm pretty happy with what I got.
|
|
|
|
|
They tried that with ADA, PL/1, and a few others. It doesn't seem to have caught on.
A "Swiss army knife" approach may work for knives, but it doesn't seem to work very well for programming languages (or any other set of tools).
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Try SWIFT. This is what caught me recently.
|
|
|
|
|
I've been considering SWIFT for expanding my base for two reasons. One because I'm dabbling in iOS development via VS and that's led to wondering about the more 'natural' approach to the task. And two, I have a growing interest in coding for Apple platforms both mobile and desktop.
If I were to do that I think I would want to jump on with the latest version being broke out by Apple as the platform seems to be really maturing.
|
|
|
|
|
Mainly Delphi 6 (Yes, from 2001). Why? Because I enjoy eating and sleeping indoors.
Transitioning to Java as that's the language of most of the other projects here.
Voted Ok with my langauges.
|
|
|
|
|
VB6, from 1998. Same motivation. Transitioning to... who am I kidding, we'll not transition unti catastrophe hits, as always.
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
I am with you. I am teaching myself C# (while transitioning my application to that language, but only so my customers can find a programmer to replace me when I finally get shot by a jealous husband .......
|
|
|
|
|
den2k88 wrote: VB6, from 1998. Same motivation. Transitioning to... who am I kidding, we'll not transition unti catastrophe hits, as always.
Yeah, me too. I've got 2 major projects (400K LOC each) and over 60 modules still in VB6. Just about all of the Classic ASP projects have finally been migrated, and just getting started on the modules which will migrate to VB.Net. Thanks to 'It Just Works', it looks like I'll have at least 5-6 years to get everything moved over. Luckily for me, it's my own code.
"Go forth into the source" - Neal Morse
|
|
|
|
|
kmoorevs wrote: Luckily for me, it's my own code That is something I envy - most of the code here was written by inexperienced programmers handling things too big for their hands. Result: logic, GUI and hardware management mixed all unhappily together.
It's taking years to descramble them, which means that we're getting to a faster and leaner platform... on a dead technology. And sicne we sell custom software for each customer we have to maintain hundreds of versions of the same software. Add that most of these environment cannot be changed, which means that we often have to maintain 10 yeras old versions... We'll be digging more and more.
The ETA to rewrite everything from scratch is 2 years, which actually means 3, and that would require us to stop doing every ordinary work to concentrate only on building the new software - of course this is unfeasible. Training a new resource would take us approximately the same time... we're down in a hole and we're keeping to dig it. If only they paid overtime I'd readily write the new software on my rest days, but for 8€/hour and no overtime they can really duck my sock.
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
No regrets or plans to go back.
|
|
|
|
|
Wastedtalent wrote: No regrets or plans to go back.
"It is unavoidable. It is your... destiny." - Darth Sidius
|
|
|
|
|
If you made the switch you can change your user name to something like "TalentPutToGoodUse"
|
|
|
|
|
C# learned a few lessons from Java. Java was OK as a prototype. C# is a production version based on experiences with the prototype. (And you might say that C++ was an OK prototype for Java.)
|
|
|
|
|
C++ is an entirely different beast.
IMHO, some of the bad decisions made by Sun when creating Java were sadly copied by C# - for example lack of support for multiple inheritance. I also prefer languages with full control resource management using RAII (C++ and Rust)
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Rob Grainger wrote: I also prefer languages with full control resource management using RAII (C++ and Rust) I tended to think the same way until I read a fairly thorough discussion of how the .net memory manager works. Several times through the discussion, my reaction was: Wow, that's smart! I would never have thought of that!
"Handwritten" memory management tends to be rather primitive. Memory leaks are more frequent than we are willing to admit. One technique often used is to not free, but manage freelists of typed elements; this can avoid leaks in the 'technical' sense, but it ties up unused memory so that it cannot be used by objects of other types. And you may have stray pointers into free memory that can cause nasty heisenbugs.
To me, explicit memory management is like assembly programming. Yes, I know that the compiler sometimes generate different code than I would have made by hand. But nowadays, I trust the compiler to know better than me.
|
|
|
|