Need advice about which tool to choose?Ask the StackShare community!
Common Lisp vs F#: What are the differences?
<Common Lisp vs F#>
1. **Paradigm**: Common Lisp is a multi-paradigm language supporting imperative, object-oriented, and functional programming, while F# is primarily a functional-first language that also supports object-oriented programming.
2. **Tooling and Ecosystem**: Common Lisp has a smaller ecosystem and less robust tooling compared to F#, which is supported by the .NET ecosystem and has integration with Visual Studio and other Microsoft technologies.
3. **Syntax and Language Features**: Common Lisp has a more expressive syntax and extensive language features such as macros, while F# has a more concise syntax and benefits from type inference and pattern matching.
4. **Concurrency**: F# has built-in support for asynchronous programming and easy concurrency management through its functional programming paradigm, while Common Lisp offers concurrency support through libraries and extensions.
5. **Platform Support**: F# is designed to run on the .NET platform, enabling interoperability with other .NET languages, whereas Common Lisp is typically implemented on top of a Lisp-based virtual machine or compiler.
6. **Community and Adoption**: F# has a larger community and higher adoption rate in industry due to its integration with the .NET ecosystem, while Common Lisp has a smaller but dedicated community focused on Lisp programming.
In Summary, Common Lisp and F# differ in their paradigms, tooling, syntax, concurrency support, platform compatibility, and community adoption.
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?
animefanx1,
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?
Yes.
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!
PS1: .NET is an end to end environment now. With the introduction of Blazor and Razor pages one does not need JavaScript or other browser scripting languages, it even interops with JavaScript. PS2. Microsoft is working on unifying .NET. Soon there will be only one version: .NET 5! Caveat: Some features such as WinForms will still be specific to the windows environment but all of those are likely things you don't need in Mac or Linux
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!
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
Pros of Common Lisp
- Flexibility24
- High-performance22
- Comfortable: garbage collection, closures, macros, REPL17
- Stable13
- Lisp12
- Code is data8
- Can integrate with C (via CFFI)6
- Multi paradigm6
- Lisp is fun5
- Macros4
- Easy Setup4
- Parentheses3
- Open source3
- Purelly functional3
- Elegant3
- DSLs1
- Multiple values1
- CLOS/MOP1
- Clean semantics1
- Will still be relevant 100 years from now1
- Still decades ahead of almost all programming languages1
- Best programming language1
- Simple syntax1
- Powerful1
- Generic functions1
- Can implement almost any feature as a library1
- Formal specification, multiple implementations1
Pros of F#
- Pattern-matching53
- Makes programming fun again42
- Type providers38
- Delightful32
- Frictionless30
- Static type inference26
- Composable21
- Ml syntax19
- REPL17
- Succinct17
- DDD10
- Making invalid states impossible9
- Great community7
- WebSharper7
- Language support for units of measure7
- Functional Programming6
- Powerful6
- Beautiful Code5
- Compact5
- Multiplatform5
- Functional paradigm5
- Computation Expressions5
- Open source5
- Less bugs5
- Productive5
- Allow use JS and .NET libraries4
- Object oriented features4
- Fun to write4
Sign up to add or upvote prosMake informed product decisions
Cons of Common Lisp
- Too many Parentheses4
- Standard did not evolve since 19943
- Small library ecosystem2
- No hygienic macros2
- Inadequate community infrastructure1
- Ultra-conservative community1
Cons of F#
- Microsoft tend to ignore F# preferring to hype C#3
- Interop between C# can sometimes be difficult2
- Hype1
- Type Providers can be unstable in larger solutions1
