Is Ash Framework the Real Deal for Elixir Devs? (Part 1)

แชร์
ฝัง
  • เผยแพร่เมื่อ 10 พ.ย. 2024

ความคิดเห็น • 30

  • @shannonsands6707
    @shannonsands6707 ปีที่แล้ว +10

    Wow, here I was just hoping for some brief example of Ash in action with Phoenix and you went ahead and lined up the creator himself for a deep dive 😁. Amazing work! I learned a ton from that, hope others did too

    • @JoshuaPlicque
      @JoshuaPlicque ปีที่แล้ว +1

      The video today is gonna be craaaaaaaazy

  • @jsonkody
    @jsonkody 8 หลายเดือนก่อน +1

    2:45 .. yep, that's exactly why I've started to learn Elixir .. I have enough of JS madness. I'll still use Vue but not much more than that.

  • @alditascheplastick8772
    @alditascheplastick8772 ปีที่แล้ว +2

    Nice talk, very professional setup

  • @BrianMyOtherPants
    @BrianMyOtherPants 5 หลายเดือนก่อน +1

    Sounds like the Naked Object pattern with appropriate off-ramps. Interesting.

  • @TerencePonce
    @TerencePonce ปีที่แล้ว +14

    I think this framework is revolutionary and is what's missing in Elixir, at least for me. The biggest pet peeve that I have with using Elixir and Phoenix is that the lib folder can be structured however you want. This usually results in a messy directory structure once your project has reached a somewhat serious level of maturity.
    I've tried multiple ways of arranging the directory structure to make it sustainable in the long term, but it's really hard to find a good balance. My mind was blown when Zach mentioned this exact problem and that fixing this problem is the main motivation for Ash Framework.
    Honestly, I think this is the missing piece needed to convince enterprise-level Ruby developers to try out Elixir. Huge Ruby projects usually incorporate libraries like Trailblazer to give structure which makes collaboration across multiple teams easier. From my perspective, Ash scratches that same itch.
    Thank you for making this video.

    • @zach_daniel
      @zach_daniel ปีที่แล้ว +3

      We do our best :D Thanks for the kind words!

    • @liveviewmastery
      @liveviewmastery  ปีที่แล้ว +2

      Loving this perspective. Thank you, Terence!

    • @jamescarr99
      @jamescarr99 หลายเดือนก่อน

      This is a good point, and a common problem for me in Laravel. Working across multiple Laravel applications there is a wildly different dir structure and layout.

  • @gonzalooviedo5435
    @gonzalooviedo5435 ปีที่แล้ว

    Wuoh!!!!!, Ash seems pretty Domain Drive Development

  • @tomodiero7524
    @tomodiero7524 ปีที่แล้ว

    I don't want to put you on the spot, but I am asking because I don't know any better, would you code your apps using ash? or just use plain old elixir/ecto etc

    • @liveviewmastery
      @liveviewmastery  ปีที่แล้ว

      At this point, I would feel comfortable coding a web application in Ash. Using plain Elixir/Ecto would put a ton of work on you to make a custom web framework for your application. I would always use something like Phoenix/LiveView/Ash.

  • @sriramkota
    @sriramkota ปีที่แล้ว

    Very interesting presentation. The recording cut off midway though. I will come back later and check the recorded version.

    • @liveviewmastery
      @liveviewmastery  ปีที่แล้ว +1

      Thanks Sriram! This was our first "premiere". We'll get it figured out!!

    • @zach_daniel
      @zach_daniel ปีที่แล้ว +1

      It’s part one of two, and the transition at the end was pretty quick so it’s easy to miss :)

    • @ja2347
      @ja2347 ปีที่แล้ว

      @@zach_daniel when are we gonna see part 2?

    • @zach_daniel
      @zach_daniel ปีที่แล้ว +1

      Very soon 😎

  • @peterdecroos1654
    @peterdecroos1654 ปีที่แล้ว

    "highly formulaic" isn't necessarily bad. there's a lot of highly formulaic apps that people are willing to be paid to be built. the biggest issue I see with a lot of these higher level frameworks is that they encourage garbage sql queries. Ecto at its base is nice because it lets sql be sql and I can write highly performant queries inside Ecto. (thats not to say Ecto doesn't have its own footguns) I perused the ash docs but it seems like a level of abstraction that could let junior devs blissfully write inefficient code.

    • @liveviewmastery
      @liveviewmastery  ปีที่แล้ว

      Zach was arguing that it works for "highly formulaic" apps and ones that aren't!
      haha! @ "it seems like a level of abstraction that could let junior devs blissfully write inefficient code" :D

  • @pixelstriko1642
    @pixelstriko1642 ปีที่แล้ว

    "There's a migration generator." At that moment, the ash framework instantly slipped into my mix.exs, created a new resource and deployed itself on 84 kubernetes nodes 😂

  • @somosworld
    @somosworld ปีที่แล้ว

    Are we familiar with type classes? This sounds a lot like auto/semi-auto type class derivation from the Haskell or Scala world

    • @liveviewmastery
      @liveviewmastery  ปีที่แล้ว +1

      Due to being an exclusive Elixir junkie, I haven't had to look into typeclasses. I'm very grateful lol

  • @Ashton351
    @Ashton351 ปีที่แล้ว

    I think we're getting digital distortion from your mic. Makes it hard to listen to.

    • @liveviewmastery
      @liveviewmastery  ปีที่แล้ว +1

      Ashton, thank you for this feedback. we will look into this

    • @Ashton351
      @Ashton351 ปีที่แล้ว

      @@liveviewmastery NP. It sounds like you're overdriving the input that the mic is connected to. You want to do a sound-check while wathcing the 'peak' indicator. It should only light occasionally when talking at your loudest.

  • @SpittingMage
    @SpittingMage ปีที่แล้ว +1

    a loudness warning would be welcome....ears hurt! :P

    • @liveviewmastery
      @liveviewmastery  ปีที่แล้ว

      My bad! We adjusted the gain on the microphones to counter balance the frequent exclamation lol