Clojure for C# Developers

Поділитися
Вставка
  • Опубліковано 7 чер 2024
  • Introduction to Clojure for C# developers on the .net platform. In this video I give an example of what it's like to program in Clojure so you can take the first steps of trying it out for yourself.
    Support my Work 🤝 / raw_coding
    Buy my Courses 📚 learning.raw-coding.dev
    Buy my Merch 🛒 shop.raw-coding.dev
    Join the Community 💬 / discord
    X 📣 / anton_t0shik
    Tune in LIVE! 🎥 / raw_coding
    Timestamps
    00:00 Introduction
    04:34 Syntax
    10:40 Fibbonaci
    25:22 Dog Facts
    #clojure #dotnet

КОМЕНТАРІ • 23

  • @Thiago1337
    @Thiago1337 10 місяців тому +7

    Why bother? haha

    • @RawCoding
      @RawCoding  10 місяців тому +9

      Programming is problem solving aka thinking.
      To get better you gotta get better at thinking, Clojure makes you better at thinking by introducing a new way to think.
      Solving problem a may help you solve problem b; you’d be stupid to not learn a new way to think to keep exponentially improving your problem solving ability.

    • @habui4149
      @habui4149 5 місяців тому

      company/cooperation: "Why should we hire you? haha"

  • @employee9911
    @employee9911 9 місяців тому +1

    I am starting to see why Clojure is the #3 most loved language. Even if you don't learn to love clojure some of the talks by Rich Hickey are pure gold.

  • @nullentrophy
    @nullentrophy 7 місяців тому +2

    I want to know if you have tried F# after this video. Would love to hear your thoughts in it

  • @mumk
    @mumk 9 місяців тому +1

    fantastic language, thanks for the quick tutorial!

  • @dirtyworkinc
    @dirtyworkinc 9 місяців тому +5

    @RawCoding, I got it, you don't want to use F# and I don't ask you to try. But I am still wondering is there are some GOOD reason for that? Cause I got a TASK from my mentor in the company that I might try to use F# just to learn how to think differently and how to better understand LINQ data flow, your concept is basically the same: you offer us to learn this staff to think differently. Can you explain why F# is not the best way to do so?

    • @RawCoding
      @RawCoding  9 місяців тому +1

      I don’t know anything about c#

    • @dirtyworkinc
      @dirtyworkinc 9 місяців тому +1

      @@RawCoding ??? Can you explain WDYM? I clearly saw couple of your videos that explains some C# staff :)

    • @RawCoding
      @RawCoding  9 місяців тому +1

      Haha, I mean f#

  • @nitrovent
    @nitrovent 10 місяців тому +1

    Reminds me of the scheme (a lisp dialect) courses in university :)

  • @ddrsdiego
    @ddrsdiego 10 місяців тому +5

    We have a language that is easy to understand and we have another that does the same things but needs the rosetta stone to understand what is being done

    • @okharev8114
      @okharev8114 10 місяців тому +2

      As some would say, git gud

  • @Qrzychu92
    @Qrzychu92 10 місяців тому +2

    I really wanted to like this video, but I could n't really follow. I am somewhat familliar with F#, bit of Elm, but this still feels like black magic. I would really want to know what exact epiphanies you had while using Closure though

    • @RawCoding
      @RawCoding  10 місяців тому +1

      You start seeing data. Things like classes, interfaces all of that falls away.

    • @nitrovent
      @nitrovent 10 місяців тому

      You could start with scheme for learning/understanding lisp based languages such as clojure. Could be a bit easier because it lacks the vectors and maps, only lists are available iirc.

    • @Qrzychu92
      @Qrzychu92 10 місяців тому +2

      @@RawCoding so same goes for any other functional language, including F# - I now hate that I cannot just have global functions in C#, everything has to go into a static clas... F# is really great in this regard

  • @iuribrindeiro5009
    @iuribrindeiro5009 10 місяців тому +15

    Hello, try F#. Thx

  • @mariobroselli3642
    @mariobroselli3642 3 місяці тому

    Please try F# . Joking . 😅 I actually use Racket.

  • @user-dc9zo7ek5j
    @user-dc9zo7ek5j 10 місяців тому

    I agree, functional languages give a different view on programming. The most important things that I understood, when using these toy languages like clojure and f# is: immutability and purity (pure core impure shell). Both terminologies helped me better the already existing software that I make. The reason on why the give a different view on programming however, is because they are very limited and are self restricting. You can use try catch... but don't use try catch because it is not pure you should handle all cases beforehand, those types of restrictions I am talking about. While more popular languages on each update just give you so much ways to do one thing. FP languages don't have 100% alternatives for all of the libraries that you are using, so you are stuck with semi/functional language with imperative features built-in so that something can actually happen.

  • @armagedon4o
    @armagedon4o 7 місяців тому

    All recommending F# MS treats it as second rate language. At one hand it bloats C# with new features and F#s smaller team has trouble keeping with it as you need to interact with C# constantly. At other hand CLR is heavily OOP(JVM with Scala for example supports them) focused and result F# lacks more advanced functional features from OCAML its based on .
    TypeScript is the MS language with the most "fancy" type system at this point.