Thank you for the suggestion! I’ll add that idea to the list ❤️

That’s a GREAT suggestion! Working with HTTP and JSON is on the top of my list for the next course, I’m glad you’re enjoying the series so far!

@@HeyRyanHaskell It would be really helpful😊 looking forward to it 😊

Great suggestion- thanks for calling that out!

Practically speaking, you aren’t wrong! 😃 It’s designed to solve the same problems as FE frameworks, it just solves them by choosing a different approach than building on top of JavaScript!

Thanks for following along, hopefully more to come in the future 🤞

RIP notifications (for now!) At least you can relive the video content whenever you’re feeling nostalgic 😅

​@@HeyRyanHaskellI'll watch your other series since I feel I have a stronger foundation now

Thanks, Gary! 😊

Thanks, I’m glad you enjoyed it! I love working with Dillon, elm-pages is great!

Thank you, and I love your suggestion too!

Thank you!! There isn’t a repo for these Elm examples, but I’ve heard some folks are creating their own as they go as a learning exercise 😎

I was also wondering if you disabled elm language server also because the rapid feedback in the editor was missing imo

If you don’t have any need to work with existing NPM packages or other build steps like TailwindCSS, there’s no need to upgrade! I originally made this Vite plugin for use with Elm Land, where folks had more varied and advanced needs. If you’re already using elm-watch, I’d stick with that!

you would love to have all your ports in typescript so even the outside world is typesafe

I'll add that to my list for upcoming course ideas, thanks for your suggestion!!

@@HeyRyanHaskell you are a blessing to the community

Thank you for taking time to leave feedback! I’ll need to brainstorm some alternatives 🧠

totally. the url from document -> to application is something I've never thought about in all my pet projects I've done in elm this is sooooo much valuable. also I'm still struggling to make a mapper fn from Msg map And Cmd map I hope I can learn in the next sections.

This is the most advanced unit and includes the stuff it took me the longest to learn! Might need a while to sink in 🧠

@@HeyRyanHaskell it is clicking. I'm watching it on repeat in different parts of the day so it clicks more

Definitely! This is a very common reason why folks prefer working with other languages in the web space. With Elm, you get the guarantee that your type system works BUT it comes at the cost of needing to be more cautious when working with raw JS or JSON values. For my personal experience, this tradeoff is worthwhile- but using a language with an "any" type has more ergonomic benefits. I encourage folks to try both and see which style they prefer!

Thank you, go for it and build something cool!

You're very welcome- I'm glad you enjoyed the video!

Hello! Yes, there are many companies offering long-term Elm roles. ( Although you'll find a HUGE number of JS framework jobs! ) I have used Elm UI and think it's great, especially for backend folks who want to avoid HTML/CSS altogether. I personally use HTML/CSS because I'm familar with the technology, and like to have more explicit control over my UI. I have not heard of iced before, however!

Thank you, I’m glad I could trick at least one person into accidentally becoming an Elm developer - hope you enjoy the learning journey! 😃

@@HeyRyanHaskell 😂lol

That’s great to hear! Elm was my first functional programming language, and it convinced me that I was smart enough to figure out how to build real stuff in a functional way. Glad I’m able to pay it forward! 😊

yeah always wanted to feel elm as a prod developer and his series hit the nail

Thanks, Tom! Glad you’re enjoying the videos so far - there’s more exciting stuff to come!

That’s a great question! We’ll answer that in detail later in the series- that was the part of Elm that took me the longest to figure out!

Thanks, Max! This is one of my favorite videos in the course, I’m glad you enjoyed it too ☺️

I don’t want to spoil anything, but I think you are REALLY going to like the second half of this series 😁

@@HeyRyanHaskell haha nice!

I’ve played around with Roc a bit and I think it’s an exciting new language! Would be awesome to see folks making Roc backend applications that work with Elm on the frontend 🤩

Thanks for the encouraging comment- more fun Elm stuff to come!!

You’re very welcome! If you’re familiar with Elm, I think you're really going to like the unit on Project Architecture - it’s the one that took me the longest to wrap my head around

Elm UI is a wonderful package- I'm glad you are having a great time using it! ❤️

I love that question! The helpfulness of my answer will depend on your specific problem, but my most common use case is when I've used a custom type like this for ID values: type ID = ID String This made it so I wouldn't mix up IDs with other string types, but now it isn't ergonomic to use it with something like "Dict ID Project" or "Set ID". In the past, I've tried a few things: 1. Created a separate `Id.Set` module with an identical API, that handles wrapping/unwrapping this custom type before inserting in the set. (This preserves the type-safety and speed, but takes some work!) 2. Gave up some of the type safety, by storing ID as a String directly. This means using "type alias ID = String" instead, but allows me to use Dict and Set normally 3. Gave up on the speed, by using the "elm-community/assoc-set" package. This has the Set API, but uses a List under-the-hood. (Because Elm is only for web apps, there's rarely been something I've been storing that's been big enough to see a significant speedup) After working with Elm for a few years, the 3rd option seems to give me the most bang-for-my-buck. Converting custom types to/from comparable values is rarely worth it in my experience, but you might encounter scenarios where it is worthwhile!

@@HeyRyanHaskell Thank you very much, I seem to like option 3 the most so far. But the challenge itself goes to show that Elm could have benefited from some sort of typeclass support, at least something like Haskell's `deriving` for custom types.

That's a GREAT question! Something that surprised me when first working with Arrays in Elm (coming from JS) is that you can't set indices past the array's size. So in our specific example if we tried this: Array.set 5 "hi" (Array.fromList [ "ryan", "scott", "alexa" ]) It would NOT insert "hi"! In the next video we cover the "Dict" type: Dict.insert 5 "hi" (Dict.fromList [ (0,"ryan"), (1,"scott"), (2,"alexa") ]) Calling insert on a dictionary works fine! It will add "hi" in the place we expect: Dict.fromList [ (0,"ryan"), (1,"scott"), (2,"alexa"), (5, "hi") ] Hope this explanation makes sense!

Thanks!

Thank you for watching! Hope you enjoy the rest of it 😊