|
You make some good points 
I'm still sticking to C# though 
By the way, what I liked about JS (MongoDB, Node, and front-end particularly) is that it's not trouble at all to work with the same objects throughout your stack (and then on the fly add some new ones). Only one language can do that 
|
|
|
|
|
C# is a good choice!
Have you ever tried Bridge.NET? It does a pretty good job of compiling C# to JS, so you can easily use C# for both back-end *and* front-end development.
|
|
|
|
|
That looks interesting, thanks!
|
|
|
|
|
Ya I rejected Javascript for many years. Until I was forced into it kicking and screaming. I found it is much easier to use, supports functional programming styles and is 100% compositional. It lacks LINQ which I really miss but other than that it's a good rugged general use language for novices as well as experts. With NODE getting stronger, who knows maybe someday it will rule the world more than it does today. Today I like Javascript and Typescript (imagine that?)
|
|
|
|
|
|
Over the years I've been migrating more towards functional styles anyway. LodAsh is very cool indeed. It was my work in Node that showed more functional style, in particular the callbacks. Whenever I return to C# which is often my code looks more like Javascript as I create functional extension methods instead of huge classes. I also honestly believe that over the years the payoff will be huge due to the fact that the functional support in my toolbox will cover 90% of what I need. I was never good at being a manager of thousands of classes all over the place in different projects. But now I have one dedicated project with only extensions. I take it with me to all new projects and it's supported 100% by intellisense. Yet C# will never have the open source libraries that javascript has and that's why I feel compelled to move towards Javascript! There's some excellent work out there like D3 to name just one!
|
|
|
|
|
There's definitely some good work going on the the JavaScript world. At a previous job I had, we used D3 to build visualizations that helped our customers catch a pretty significant amount of fraud.
I agree that a more functional style is very appropriate for a lot of the work a typical developer does today, especially when it comes to web development. At the end of the day, a large chunk of web and business app development just involves grabbing some data, piping it through a series of transformations, and then outputting the result.
When working in the .NET ecosystem, I've found F# very enjoyable for work like this. This little app ended up being quite a bit shorter than its C# equivalent. I especially like how easy it is to use the |> operator to pipe to output of one function into another. It makes it really easy to use the 'data pipeline' approach.
|
|
|
|
|
It's powerful, fast and does not need contorsions to get low level. Low level is usually not needed, except when you write real time systems, drivers, kernel pieces or painfully heavy but necessary algorithms (Image Processing, I'm accusing YOU!).
Since I develop for each of them (except kernel pieces, for now) I prefer C++. Maybe for business oriented or consumer application (NOT GAMES) I'd really think about C#, even if C++/CLI still appeals to me more than C#, even if those new symbols make me cringe looking at the code - I think it's a matter of habit.
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
|
|
|
|
|
|
Webmaster forgot about these 2 GPGPU languages!
Cg, HLSL and GLSL shader language are also C based.
|
|
|
|
|
Turbo C, VAX C, DEC C, HP C, etc. -- but went with C#; it's just easier.
|
|
|
|
|
But i miss the native pointer mess from C++ a lot. 
And I hate the resource xaml sh*t. 
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
you can get your pointers just work 'unsafe'
|
|
|
|
|
I never use XAML; I write mostly backend, WinForms, and command-line utilities.
|
|
|
|
|
You can use pointers in C# just fine. I do it all the time.
|
|
|
|
|
It is all about our tastes...
|
|
|
|
|
...so paste a comment on your favourite one that's missing. There's only so much space on the homepage.
cheers
Chris Maunder
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
