This feels like a more low-level version of phoenix live view. There's so much magic going on in elixir and phoenix land, so I appreciate the fact that you have to wire everything up yourself for the learning effect. Love it!
I really enjoy your content, and I'm a big fan of Gleam as well! I've just started learning it, and I'm excited about its potential. I'd love to see you create a video on building a backend API with Gleam-that would be incredibly helpful! Looking forward to more of your videos. 😊
Any way to make client.mjs cacheable? Even better would be to have a hash in the name, and be able to use "cache-control: public, max-age=31536000, immutable". I would also be interested in seeing how to improve other lighthouse issues.
Did you read "Crafting interpreters" by any chance? You mentioned Lox, which is a toy language invented by the author of the book. If not, I would strongly recommend reading it, as it truly is a great book!
@@IsaacHarrisHolt Perfect I'm working on a school project right now, I'm making a payroll app and trying to use Gleam as the backend it's been great. Recently switched from using Rust for my last project
way too much boilerplate for lustre. that's why i don't like elm architecture. also the view syntax is very unintuitive. gleam needs a macro that generates a jsx type of ast.
The problem with XML stuff and Gleam is you need a preprocessor step and things can easily get out of sync. You'll learn the syntax pretty quickly. And boilerplate is good! I'd rather spend time typing and making something understandable than using layers of abstraction and creating a debugging nightmare
It scales absolutely fine, you just have to be clever about state management, same as in any framework. Lustre also allows you to have "components" for more complex things like comboboxes, so you can avoid the complexity that Elm added there
@adaszko here you go: github.com/lustre-labs/ui/blob/v1/src%2Flustre%2Fui%2Fcombobox.gleam This is an implementation being worked on for the official Lustre UI package
This feels like a more low-level version of phoenix live view. There's so much magic going on in elixir and phoenix land, so I appreciate the fact that you have to wire everything up yourself for the learning effect. Love it!
Yes! That's about right, but Lustre is more focused on individual components rather than making the whole run on the server
A very good Intro to Server Components! I also loved how you explained when to use them in the end.
Thanks! Glad you found it helpful
Great content! We can feel the effort you put into this, the animations, the topics ! Very cool ! Thanks for that.
I'm glad you found it helpful!
I really enjoy your content, and I'm a big fan of Gleam as well! I've just started learning it, and I'm excited about its potential. I'd love to see you create a video on building a backend API with Gleam-that would be incredibly helpful! Looking forward to more of your videos. 😊
It's definitely on the cards!
@@IsaacHarrisHolt nice!!!
I love your videos mate, just getting into Gleam again. You just get straight to the point with very concise information.
(the code link 404s btw)
Fixed! Thanks for letting me know
I love this series so much thank you for making gleam content 🙏
I'm glad you're finding it helpful!
Love the gleam content, thank you sir!
Glad you're finding it useful!
Gleam is my new favorite language.
It's so good
Any way to make client.mjs cacheable?
Even better would be to have a hash in the name, and be able to use "cache-control: public, max-age=31536000, immutable".
I would also be interested in seeing how to improve other lighthouse issues.
You can do whatever you like! It's your code 😉
I kinda like his video editing skills ;)
Thank you :)
Hey man is there any opportunity available to work with you as video editor? Let me know i can help to increase the watch time
My business email is available on the channel page. Send a pitch there.
@@IsaacHarrisHolt I couldn't find.
It's in the about section
Great video! I'm definitely interested in building an app with a mix of server and client components. Maybe a social media feed or a chatroom? 🤔
Sounds like a great use case for server components!
Try another project instead of another chatroom, media feed, Todo app, etc.
@@kowaihana Good to know that you're looking forward to my small learning exercises so much that you'd like for them to be new & exciting :)
Did you read "Crafting interpreters" by any chance? You mentioned Lox, which is a toy language invented by the author of the book. If not, I would strongly recommend reading it, as it truly is a great book!
I'm partway through it! The CodeCrafters Interpreters course is kinda like a practical walkthrough of that book
Say homie can you show us how to do some login and session functionality
Absolutely! I've recently implemented this in a (pre V1) library called Pevensie. You can have a look at the source for that if you like
@@IsaacHarrisHolt Perfect I'm working on a school project right now, I'm making a payroll app and trying to use Gleam as the backend it's been great. Recently switched from using Rust for my last project
Awesome! Gleam is wonderful for backend stuff
I think I’m too react pilled for this but it seems cool!
No harm in giving it a go!
Ohm Gleam....I love gleam....
It's so goooood
hello brother i hope these become the Next laravel in the future and to do these we need to create job and to do it we must build resource
i am a laravel dev and i will like to see gleam go well
Awesome! Laravel is very cool
Glem backend with Nextjs 15
You could, but I think Lustre works better!
way too much boilerplate for lustre. that's why i don't like elm architecture. also the view syntax is very unintuitive. gleam needs a macro that generates a jsx type of ast.
The problem with XML stuff and Gleam is you need a preprocessor step and things can easily get out of sync. You'll learn the syntax pretty quickly.
And boilerplate is good! I'd rather spend time typing and making something understandable than using layers of abstraction and creating a debugging nightmare
@@IsaacHarrisHolt you say that for a small app but you will hate it when you do anything serious with it. elm architecture doesn't scale at all.
It scales absolutely fine, you just have to be clever about state management, same as in any framework.
Lustre also allows you to have "components" for more complex things like comboboxes, so you can avoid the complexity that Elm added there
Can you point me to the combo box component code? I'm interested in the implementation
@adaszko here you go: github.com/lustre-labs/ui/blob/v1/src%2Flustre%2Fui%2Fcombobox.gleam
This is an implementation being worked on for the official Lustre UI package