Slash Lustre Load Times with Server Side Rendering

[@sadkebab]

Looks like we finally have a real contestant for the monopoly of JS in full-stack development

[@IsaacHarrisHolt]

Hopefully! Gleam is great

[@callowaysutton]

Monopoly? Hahahahaha If you only watch KZbinrs/Twitter maybe

[@sadkebab]

​@@callowaysutton specifically I was talking about single language options and yeah you have Phoenix, Livewire and so on but they limit a lot what you can do client-side (that's why IntertiaJS is so popular for their reference frameworks)... so yeah JS is the only option that gives you "uncompromised" full-stack development.

[@simonricard4403]

@@sadkebab I haven't encountered a single thing I couldn't do with Phoenix Liveview that I could do with an SPA framework. Just gotta use a JS hook for those few cases, but you still write 90% less JS versus using a traditional front-end framework

[@sadkebab]

​@@simonricard4403 yeah and you have 90% more points of attrition. You will always build complex UXs faster with any JS metaframework. I think Phoenix is really great, don't get me wrong and it's great that it allows Elixir developers to build cool stuff without getting delving too much into JS. But rich UXs normally involve a lot of client-side stuff going on and unless you use something like InertiaJS on top of Pheonix, you will be slower and will struggle much more to get the job done. For simple webapps I don't think it really matter tho, use what you are confortable with and you'll get the best results.

[@lowerclasswarfare]

Really great explanation, speed (not too fast), and just a really well done video.

[@IsaacHarrisHolt]

Thank you!

[@naomieowdev]

Brilliant video as always Isaac!

[@kollpotato]

too much unnecessary gifs in my opinion

[@IsaacHarrisHolt]

Thanks Naomi!

[@IsaacHarrisHolt]

I'm trying to cut down the number, but creating the animations etc. takes a lot of time I don't have at the moment 😅

[@cryptonative]

who in the history of blasphemy orders pokemon alphabetically

[@IsaacHarrisHolt]

😂 that part of the program only has the names to go by! It's open source if you wanna upgrade it 😉

[@cryptonative]

@@IsaacHarrisHolt Jk! Thanks for the video mate

[@IsaacHarrisHolt]

Glad you enjoyed!

[@cristobalgajardovera5433]

@@cryptonative Smogon does hahaha 🐒

[@StingSting844]

Me who doesn't know anything about Pokemon

[@rajmajumdar5253]

I had to do doubletake while looking at that framework name lol 🤣🤣🤣🤣 Though i was recommended something else lmao 🤣🤣🤣🤣

[@IsaacHarrisHolt]

What do you mean 👀

[@Heshamelfakharani]

how long have these things been in development, this is great

[@IsaacHarrisHolt]

I'm not sure! A few years, I think

[@hayleigh-dot-dev]

Gleam has been in development for a few years now, but we officially released v1 in march. Lustre in its current from is about a year old at this point :)

[@AsherDMckoy]

Put a different trainer hat on the Gleam star for every video

[@IsaacHarrisHolt]

Haha good idea!

[@らい-m7i]

How do we handle having multiple routes?

[@IsaacHarrisHolt]

In this scenario you can render them separately, but typically you'd have a model per route, and this would exist as a field in a larger overall model that also stores global state. Check out the Modem library for client side routing

[@らい-m7i]

@@IsaacHarrisHolt Thank you! I'll try it out.

[@codingszy]

Whats the vim theme?

[@IsaacHarrisHolt]

AstroNvim

[@JLarky]

We didn't have SSR in the 90s, we had dynamic rendering. I'm going to die on this hill

[@IsaacHarrisHolt]

What do you consider to be the difference?

[@JLarky]

@@IsaacHarrisHolt there was no "server side" of PHP rendering :) PHP was always on the server. Only once technologies like React showed up we started talking about rendering our JavaScript apps on the "server side" as opposed to the normal "client side" :) basically the term SSR didn't exist until Next.js showed up

[@IsaacHarrisHolt]

@JLarky Sure, the term didn't exist, but the concept was the same. Server gets request and returns personalised/dynamic HTML to the client. I think the language has probably evolved, but I'm not sure the concept has

[@JLarky]

@@IsaacHarrisHolt it's not the same concept :) dynamic page generation includes SSR, but SSR is a more narrow concept that only makes sense when you have an isomorphic app (which we didn't have in 90s)

[@IsaacHarrisHolt]

I'm not sure I see what the actual differences are here. What does dynamic rendering do/allow that SSR doesn't?

[@SpektralJo]

I really dont like the idea of writing html using function composition

[@IsaacHarrisHolt]

How come?

[@SpektralJo]

@IsaacHarrisHolt I think it just looks off and includes a lot of visual noise like a lot of brackets (often semantically useles ones like [], if an element has no atributes) the html. prefix (or you have to import the functions you use) etc. I really just like looking at actual HTML way more.

[@IsaacHarrisHolt]

That's fair, but I don't think it's enough of a reason not to try Lustre. It's pretty great, and you get used to the syntax very quickly

[@SpektralJo]

@@IsaacHarrisHolt can you use lustre just on the Server. Because I want to try out htmx for the frontend

[@IsaacHarrisHolt]

Absolutely!

[@someofmyinterests]

Gleam is great, but Elixir with Phoenix Liveview is even better 😎😎

[@IsaacHarrisHolt]

What about Gleam liveview? 👀

[@dandogamer]

​@@IsaacHarrisHolt yes would love to see a gleam phoenix project!!