I love how web development has gone full circle. In 2006 I wrote a chatroom site that was server-side with Ruby on Rails-based javascript sprinkled in for realtime page updates. It was long polling of a single HTTP request (websockets didn't exist then) but it worked extremely well. Never liked SPAs and the npm bloat. Happy that stuff like Svelte and Phoenix is taking it back to the server-side with JS sprinkles place which seems optimal to me.
Phoenix 1.7 is View-less
41–50 of 224 posts
Re: Phoenix 1.7 is View-less
#42We're building a startup ( https://www.batteriesincl.com/ ) with Elixir and Phoenix 1.7rc (git master really). It's been amazing; I could not be happier. - We went hard on components and it's made building UI's easy. In fact I wrote a test library to make component testing easier. - Live view is so easy with a good component library. I'm not a designer, but with snappy interactions and easy to use components, it's no…
I'm also doing a solo-startup right now that relies heavily on LiveView and Channels/Websockets. I wouldn't have been able to build it by myself without Elixir/Pheonix. It's absolutely fantastic, can't recommend it highly enough.
Re: Phoenix 1.7 is View-less
#43Earlier quoted context omitted.
Has anyone figured out how to do static typing in Erlang yet? FB a few years ago announced they were going to work on it for WhatsApp but then it was indefinitely delayed. There’s also been a few other attempt, but I don’t believe anyone has succeeded. I know Gleam exists but haven’t dug into it. Anyone more in the know care to share?
Jose has been working with some PhDs to attempt to implement static typing https://elixir-lang.org/blog/2022/10/05/my-future-with-elixi... In the meantime I don’t know what people have against using @spec. It’s a far more powerful type specification than the majority of static-typed languages out there
> Actually, I think the next big unlock in user adoption is static typing.
From reading that post, it sounds like Jose does not believe static typing is needed. But a nice to have to address a very narrow set of use cases that primarily would help for documentation, not bug mitigation.
Re: Phoenix 1.7 is View-less
#44Can someone _please_ get around to building a framework for Gleam[0] so that I can finally get over my hesitance to dive into a BEAM language over erlang's/elixir's dynamic typing?
Re: Phoenix 1.7 is View-less
#45Can someone _please_ get around to building a framework for Gleam[0] so that I can finally get over my hesitance to dive into a BEAM language over erlang's/elixir's dynamic typing? [0] https://gleam.run/cheatsheets/gleam-for-rust-users/
[deleted]
Re: Phoenix 1.7 is View-less
#46Earlier quoted context omitted.
What is your point?
Just to point out that "ZERO react/JS nonsense" is based on looking down on mainstream languages even after they've improved and even though the platforms use them.
It sounds like you’ve never used Liveview to me. There are many advantages to it besides just zero JS.
Re: Phoenix 1.7 is View-less
#47Earlier quoted context omitted.
LiveView has been pretty great. Mostly it's just a couple of `handle_event` methods away and we have a fully reactive UI. I haven't seen any scaling issues for LiveView. Under the hood there's a websocket that push and pull events from a running GenServer for each session. Since each process is independent it's horizontally scalable as long as your able to route websockets to the same process in a cluster. While not…
@chrismccord If you’re reading this, would be super interesting to update this 7-year-old benchmark to use Live View (and the latest stack). Thanks for all you do btw.
Could even switch over to Bandit which was on a recent Thinking Elixir podcast
> In recent performance tests, Bandit's HTTP/1.x engine is up to 5x faster than Cowboy depending on the number of concurrent requests. When comparing HTTP/2 performance, Bandit is up to 2.3x faster than Cowboy
Re: Phoenix 1.7 is View-less
#48So many great changes! I can’t wait!
I’ve been using Phoenix / Elixir since 2016 and i’ve been really happy with it
Re: Phoenix 1.7 is View-less
#49I'm building a startup in my free hours using Phoenix Liveview. I can ship features in hours vs days thanks to the simplicity liveview gives me. ZERO react/JS nonsense. I back to writing server side rendered templates with for-free reactivity. Give it a try it's very productive
The downside as I understand it is the extra work to manage UX for connections with high latency and/or going offline, correct?
To me that's a non-issue. How are you going to access a website without internet anyways?
If you're talking about "slow" internet, then use Alpine JS to run truly client-side things in those very rare cases.
Re: Phoenix 1.7 is View-less
#50Earlier quoted context omitted.
What is your point?
Just to point out that "ZERO react/JS nonsense" is based on looking down on mainstream languages even after they've improved and even though the platforms use them.
I've used them enough to have my own informed opinion on the languages, frameworks and mentality in the ecosystems I talk about. We're both right -- because we both are sharing our opinions.