Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How we got to LiveView

fly.io

Post reply on HN
Print view View original

161–170 of 293 posts

Re: How we got to LiveView

#161

Post by brainbag »

cs44 wrote: post #83
akoutmos wrote: post #46

Earlier quoted context omitted.

For a lot of the LiveView applications that I write (which is actually quite a few these days), I will usually lean on something like AlpineJS for frontend specific interactions, and my LiveView state is for things that require backend state. For example, if I have a flag to show/hide a modal to confirm a resource delete, the show/hide flag would live in AlpineJS, while the resource I was deleting would live in the s…

I'm surprised to see so few mentions of AlpineJS. Personally, PETAL has become my de facto stack.

What is PETAL?

Re: How we got to LiveView

#162

Post by ec109685 »

sgrytoyr wrote: post #35
chrismccord wrote: post #2

Creator of Phoenix here. I'm happy to answer any questions folks have about LiveView, Phoenix, or Elixir in general. We've had some big LiveView features land recently with uploads and HEEx so now's a great time to jump in!

Almost every time I see a discussion about LiveView there’s someone complaining about the issue of latency/lag, and how it makes LiveView unsuitable for real-world applications. From what I understand, the issue is that every event that happens on the client (say, a click) has to make a roundtrip to the server before the UI can be updated. If latency is high, this can make for a poor user experience, the argument goe…

Here's a demo that illustrates that delay: https://breakoutex.tommasopifferi.com/

Agree it's super neat framework and hope a client side implementation can be written to "stage" the change.

Re: How we got to LiveView

#164

Post by mrkurt »

iudqnolq wrote: post #156
mrkurt wrote: post #151

Earlier quoted context omitted.

This is a pretty good liveview tutorial: https://github.com/dwyl/phoenix-liveview-counter-tutorial We also have a hiring project that's designed to ease people in to Phoenix + LiveView. We extracted this from a real app and tried to make it as simple as possible to work on: https://github.com/fly-hiring/phoenix-full-stack-work-sample

What sort of experience level are you hiring for? I've been teaching myself elixir and liveview over the past year for my first job (building dashboards for a non-technical nonprofit) and I've been hoping to transition to working somewhere technical but I have no idea how to do it. Thanks!

Your experience level, actually. Here's the full post:

https://fly.io/blog/fly-io-is-hiring-full-stack-developers/

Re: How we got to LiveView

#165

Post by iudqnolq »

mrkurt wrote: post #164
iudqnolq wrote: post #156

Earlier quoted context omitted.

What sort of experience level are you hiring for? I've been teaching myself elixir and liveview over the past year for my first job (building dashboards for a non-technical nonprofit) and I've been hoping to transition to working somewhere technical but I have no idea how to do it. Thanks!

Your experience level, actually. Here's the full post: https://fly.io/blog/fly-io-is-hiring-full-stack-developers/

Thank you!

Re: How we got to LiveView

#166

Post by sarchertech »

brainbag wrote: post #161
cs44 wrote: post #83

Earlier quoted context omitted.

I'm surprised to see so few mentions of AlpineJS. Personally, PETAL has become my de facto stack.

What is PETAL?

Phoenix, Elixir, Tailwind, Alpine, and LiveView.

https://changelog.com/posts/petal-the-end-to-end-web-stack

Re: How we got to LiveView

#167

Post by e9 »

subpixel wrote: post #121

This strikes me as sort of like Meteor, only without the suggestion that real time apps will be trivially easy to build.

I thought exactly this. I wonder if we can get author to elaborate on the differences with Meteor.

Re: How we got to LiveView

#168

Post by travisgriggs »

I’m not a hard core web dev, but it seems that from a high level, Phoenix is similar to the Smalltalk Seaside web framework that people were excited about 10+ years ago. Can anyone who is similar with both speak to that? Are they really similar, or is there a key distinction I’m missing?

(I’ve become a big fan of Elixir as a former Smalltalker)

Re: How we got to LiveView

#169

Post by davidw »

tptacek wrote: post #134
davidw wrote: post #101

Earlier quoted context omitted.

Looking more at things like #2. Sidekiq isn't terrible though, and if you get big enough, you're going to want some more management than just spawning a BEAM process to do something. What have people settled on for that with Elixir/Erlang?

Sidekiq is great, but it is a thing you have to think about (in particular, how you're shuttling state from workers to a place where front-end can see it). The big win with Phoenix as I understand is not having to think about it at all: it has a natural expression in the language and the platform, and that expression is performant.

If it's just a small fire and forget thing in Erlang, you can just spawn the process, sure. My point is that once people start to care about what happens with those background jobs, you probably need some infrastructure around them, and then the Erlang thing might start to resemble Sidekiq a bit more.

Re: How we got to LiveView

#170

Post by mmaunder »

mdip wrote: post #118
mmaunder wrote: post #105

"Do you remember when Ruby on Rails was first released? I do. Rails was also a revolution." I remember and I disagree. It was dog slow, run by a guy who made slides that said "Fuck you." and was rife with memory leaks.

I worked for a gentleman[0] who, while not a programmer by trade[1], he was an old Unix guy and a Linux early-adopter. All of that to say that when he'd made a recommendation for me to explore this or that technology, I generally listened. He pointed me at Ruby on Rails. I admit I came into researching Rails a little reluctantly and pretty early on, as well. That probably biased my opinion of things a lot more than i…

Looks like the brogrammers found you, friend. You’ve also been downvoted into oblivion. Know that I see you.
Post reply on HN