Need advice about which tool to choose?Ask the StackShare community!
C# vs Julia: What are the differences?
C# and Julia can be categorized as "Languages" tools.
"Cool syntax" is the primary reason why developers consider C# over the competitors, whereas "Lisp-like Macros" was stated as the key factor in picking Julia.
Julia is an open source tool with 22.5K GitHub stars and 3.4K GitHub forks. Here's a link to Julia's open source repository on GitHub.
Stack Exchange, PedidosYa, and Coderus are some of the popular companies that use C#, whereas Julia is used by inFeedo, Platform Project, and N26. C# has a broader approval, being mentioned in 684 company stacks & 1119 developers stacks; compared to Julia, which is listed in 5 company stacks and 5 developer stacks.
Hi there. I want to expand my coding toolset. So I want to learn a second backend language besides Kotlin. Kotlin is fantastic. I love it in every aspect, and I think I can never return to Java. And also why should I? It is 100% interoperable with java and can co-exist in every project.
So my question here is. Which language do you think will bring me more joy? I think F#; it is more like Kotlin. Then C# (it's more or like 100% java). But, let's say I learn F#. Is it 100% interoperable like Kotlin? can they live side by side? Can I, then, apply to .NET jr jobs after a while, for example, or is C# the holy cow? I would like to learn .Net.
If it is the worst and only C# is acceptable, then which language should I learn? Dart? Go?
Exceptional decision to go with Kotlin. For the other story, go full with C#. "is C# the holy cow? Yes it is.". Specially now when netCore is crossplatform and you can build asp.net core applications on Windows, Linux and macOS via Visual Studio Code which is also multiplatform. Nothing will beat C# in the near future. Also, at the end of 2021 Microsoft will release Net 6.0 which will include MAUI.
"For those new to .NET MAUI (standing for .NET Multi-platform App UI), Microsoft says it's "the evolution of Xamarin.Forms extended from mobile to desktop scenarios with UI controls rebuilt from the ground up for performance and extensibility."
So, C# all the way sire!
First let's get your questions sorted: Which language do you think will bring me more joy?
This you will have to decide for yourself, I am a long time C# developer and have seen it grow into a very compelling platform. The language and I'd compare it more to Kotlin than Java (by a long margin). More on .NET in a bit.
say I learn F#. Is it 100% interoperable like Kotlin?
You can have 100% interop with a caveat, your F# libraries have to implement certain guidance in order to be referenced from C#. Some (dare I say most) of the differences between F# and C# are predicated on language constructs that are not available in C#. For instance F# functions that return Unit.
can they live side by side?
Can I, then, apply to .NET jr jobs after a while, for example, or is C# the holy cow?
I don't know if I take your meaning, but let me say this: Learning either C# or F# will likely force you to understand concepts such as garbage collection, primitive types, etc. which apply to all .NET languages, thus a lot of the effort you put into .NET is bound to pay off regardless of your choice.
If it is the worst and only C# is acceptable, then which language should I learn? Dart? Go? You can't go wrong with any of these and I venture to say whether you select C#, F#, Dart or Go as your next adventure, your willingness to learn will take you to try other languages, some which mey not even exist yet!
I think you can learn go instead C#. C# is cool, but Golang also cool. It can run on any OS without specific software. C# can run on linux too but it's only the .NET Core as I know. But golang is flexible. So try it and decide what do you think about Golang
Also, any tips & good practices are greatly appreciated :)
If you want to learn
C# to write some backend code you can also check out
A good entry to
Express.js. It is the most common web framework for
Node. It's well documented and there are a lot of educational materials for it.
I prefer functional programming because it produces less buggy code (thus I recommend
F#), and is simply better to learn this paradigm earlier on in your coding career rather than later. It can also do most stuff
C# can do, namely code with
.NET core. If you're going to learn
.NET then you should learn
Express first though before doing web development with
I think you can manage to find something about this topic. it's pretty popular one. ex: https://www.educba.com/c-sharp-vs-js/
Something I don't see discussed enough over the internet is the performance difference. I don't think you should worry about this. 95% of the time you won't notice the difference on your day to day projets. You will know what you need in terms of performance when you get there.
Hi all, I have been working on the development and automation of construction software using C# and Python. Recently I have started working on Django python web framework and basic frontend for web development. I am really confused to choose between C# and Python to move forward in my career. Seeking your advice on these technologies and their future market value from a career perspective. Thanks,
It depends on your preferred career path, if you want to work in start-up/scale-up environments, you probably want to go with a language like Django for the rapid development (fast to production). On the other hand, C# or Java would be better for building long term and large scaled applications, although, Django could certainly achieve this as well. I also want to second that it won't hurt to know both languages, pick your technologies wisely according to the use case, don't stick to a single technology stack. :)
C# and Python are both great languages. With great communities, libraries, frameworks, opportunities. I think it will be the same in a near future.
It’s matter of your likes, and your next jobs.
Dot net core is a little faster on performance. Python more popular with dynamic types. Probably the most lovable language.
I need some advice to choose a language for back-end development. Right now, my REST APIs were created by using Flask/Django, and I'd like to create a more reliable and more efficient API with static typing. On the one hand, Go is young, very light, and syntax like Python's, but C# has a large number of libs and more built-in methods. Which is the best solution today?
From times to times I asked or was asked that same question. Technology aside, it's important to consider the skills and expertise that the dev team has. Whether you use language A,B or C or framework X,Y and Z, if your team has a strong background and experience with something make it count too.
I would recommend Go simply because as you mentioned, it's super light. No need to bring in the whole .NET suite to get a simple REST API up and running. Even if your API is a bit complex, Go should be able to handle it.
I'm new to Go, I've got very little experience but the 'feel' of Go, isn't like Python in my opinion. Go has a pretty steep learning curve, much steeper than C# in my opinion. So if you are willing to consider Node/Express/TypeScript, I think you may really like it. If you're picking between Go and C#, I'd go for C# as of today, but once I am more comfortable with Go (which I anticipate being a slow process) I may change my mind.
At this moment in time, in late 2020- Node/Express/TypeScript feels like the obvious choice to me as a former C# developer.
The best language for you is the one that you know best!
Its a bit of a guess, but from your question and the difficulties you have with Python it seems to me the problem you describe is the manifestation of a bad design/architecture/code quality. These are not the problems of a language itself!
The experience you gained over the past years with your current programming language will outmatch any benefits of another language that you start from zero.
Because in the end of the day languages aren't all that different when it comes to fullfil the same task, it's more the tools, framework and ecosystem for a particular problem that make a difference.
I worked with Java, C#, Go and recently in Phyton, and I would choose Phyton over Go for WebApps, even I like compiled languages more. Go is a very simple language, I would even say maybe too simple. I can't stand all those go boilerplate if err checks, the broken filesystem, the date/time mess and many more things that aren't actually relevant for business application at all. Go has its advantages but not for WebApps.
Keep the lang and improve your skills and architecture you will benifit more from it than from a new language.
I recommend Go for backend. It's younger than C# doesn't mean it's not mature. It's already mature enough to be run on production. You can see there are already many companies in the world adopting Go as their backend business logic or tooling. I can name a few like Github, Shopify, uber, twitch, and many more. It's easier learning curve, low entry barrier, better performance than C#, better memory consumption than C#, since there's no VM/runtime needed. It's suitable for large scale system and large codebase for readibility and long maintainability. It's simpler than C# since no class, inheritance(this can cause hard to maintain software), exception, etc. You can still implement OO way in Go without those feature. Simple file structure, only main files and package files. It compiles to single binary and easy to deploy and work around it, unlike C# who compiled to IL and you need to wrap all those IL files to be run inside separated web server(even .Net/.Net Core platform provide built-in web server). For libs, don't worry, there are many open source libs you will found on Github and already adopted by many companies. Go is employed in personal, startup, even corporate level.
I suggest Go because it has a simple and clean ecosystem. The language is simple. You don’t need complex configs or installs either. You’ll be up and running very quickly. It doesn’t have as much as .NET but its standard library is more than sufficient for RESTful APIs. Concurrency is much, much easier too.
C# I’d definitely recommend later on. The .NET framework, especially core, is extremely powerful and there’s little you can’t build with it. Go won’t take you long to be productive with.
The database your are going to connect and the needed libraries could decide. Because both are awesome languages.
If you want to stick with python you may want to consider Fastapi. It uses Pydantic to give you strongly typed models and validation. It generates openapi docs for you out of the box. They have good documentation as well and they claim it is really fast.
I would recommend C#, particularly Simplify.Web web-framework. C# is easy to start with (especially .NET Core). Simplify.Web is also easy to start with, no extra setup required for simple API, but on the other hand you have power of C# and full control over your API with ability to extend.
I have some systems on production using both languages. I tend to use golang if the API is small or medium size, but if I am going to build a large system definitively I use c#(asp netcore).
I was considering focusing on learning RoR and looking for a work that uses those techs.
After some investigation, I decided to stay with C# .NET:
It is more requested on job positions (7 to 1 in my personal searches average).
It's been around for longer.
it has better documentation and community.
One of Ruby advantages (its amazing community gems, that allows to quickly build parts of your systems by merely putting together third party components) gets quite complicated to use and maintain in huge applications, where building and reusing your own components may become a better approach.
Rail's front end support is starting to waver.
C# .NET code is far easier to understand, debug and maintain. Although certainly not easier to learn from scratch.
Though Rails has an excellent programming speed, C# tends to get the upper hand in long term projects.
I would avise to stick to rails when building small projects, and switching to C# for more long term ones.
Opinions are welcome!
After writing a project in Julia we decided to stick with Kotlin. Julia is a nice language and has superb REPL support, but poor tooling and the lack of reproducibility of the program runs makes it too expensive to work with. Kotlin on the other hand now has nice Jupyter support, which mostly covers REPL requirements.
In 2015 as Xelex Digital was paving a new technology path, moving from ASP.NET web services and web applications, we knew that we wanted to move to a more modular decoupled base of applications centered around REST APIs.
To that end we spent several months studying API design patterns and decided to use our own adaptation of CRUD, specifically a SCRUD pattern that elevates query params to a more central role via the Search action.
Once we nailed down the API design pattern it was time to decide what language(s) our new APIs would be built upon. Our team has always been driven by the right tool for the job rather than what we know best. That said, in balancing practicality we chose to focus on 3 options that our team had deep experience with and knew the pros and cons of.
That left us with two options. We went a very unconventional route for deciding between the two. We built MVP APIs on both. The interfaces were identical and interchangeable. What we found was easily quantifiable differences.
We were able to iterate on our Node based APIs much more rapidly than we were our C# APIs. For us this was owed to the community coupled with the extremely dynamic nature of JS. There were tradeoffs we considered, latency was (acceptably) higher on requests to our Node APIs. No strong types to protect us from ourselves, but we've rarely found that to be an issue.
As such we decided to commit resources to our Node APIs and push it out as the core brain of our new system. We haven't looked back since. It has consistently met our needs, scaling with us, getting better with time as continually pour into and expand our capabilities.
C# and .Net were obvious choices for us at LiveTiles given our investment in the Microsoft ecosystem. It enabled us to harness of the .Net framework to build ASP.Net MVC, WebAPI, and Serverless applications very easily. Coupled with the high productivity of Visual Studio, it's the native tongue of Microsoft technology.
Pros of C#
- Cool syntax347
- Great lambda support289
- Great generics support261
- Language integrated query (linq)207
- Extension methods178
- Automatic garbage collection91
- Properties with get/set methods88
- Backed by microsoft81
- Automatic memory management69
- Amaizing Crossplatform Support60
- High performance43
- Great ecosystem of community packages with Nuget33
- Vibrant developer community25
- Great readability22
- Dead-simple asynchronous programming with async/await20
- Visual Studio - Great IDE16
- Open source15
- Strongly typed by default, dynamic typing when needed14
- Object oriented programming paradigm13
- Easy separation of config/application code11
- Great community9
- Operator overloading8
- OOPS simplified with great syntax7
- Events management using delegates7
- Linq expressions6
- Good language to teach OO concepts6
- Conditional compilation6
- Organized and clean5
- Coherent language backed by an extensive CLR5
- Comprehensive platform libraries5
- Top level code4
- Concise syntax, productivity designed4
- Statically typed2
- Sophisticated overall1
- Far more sleek and sphisticated than other languages1
Pros of Julia
- Fast Performance and Easy Experimentation24
- Designed for parallelism and distributed computation21
- Free and Open Source18
- Dynamic Type System17
- Multiple Dispatch16
- Calling C functions directly16
- Lisp-like Macros16
- Powerful Shell-like Capabilities10
- Jupyter notebook integration9
- String handling4
- Emojis as variable names4
Sign up to add or upvote prosMake informed product decisions
Cons of C#
- Poor x-platform GUI support15
- Closed source8
- Fast and secure7
- Requires DllImportAttribute for getting stuff from unma7
Cons of Julia
- Immature library management system5
- Slow program start4
- JIT compiler is very slow3
- Poor backwards compatibility3
- Bad tooling2
- No static compilation2