Phoenix 1.7 is View-less

#1

Post by todsacerdoti » Fri, Dec 30, 2022, 6:52 PM UTC

Phoenix 1.7 is View-less
germanvelasco.com

Re: Phoenix 1.7 is View-less

#2

Post by drannex » Fri, Dec 30, 2022, 7:57 PM UTC

This definitely reduces some of the cognitive overhead of designing out a Pheonix service, thats for sure. A really welcome change in my eyes.

Re: Phoenix 1.7 is View-less

#3

Post by Crazyontap » Fri, Dec 30, 2022, 8:00 PM UTC

Speaking as an amateur programmer, is this like Laravel's livewire or intertiajs with inline blade component? (but in Elixir). Or is this something else?

Re: Phoenix 1.7 is View-less

#4

Post by thedangler » Fri, Dec 30, 2022, 8:02 PM UTC

Crazyontap wrote: post #3

Speaking as an amateur programmer, is this like Laravel's livewire or intertiajs with inline blade component? (but in Elixir). Or is this something else?

livewire was inspired by liveview. I think livewire 3 will be more like the newer version of liveview

Re: Phoenix 1.7 is View-less

#5

Post by jnsaff2 » Fri, Dec 30, 2022, 8:02 PM UTC

Crazyontap wrote: post #3

Speaking as an amateur programmer, is this like Laravel's livewire or intertiajs with inline blade component? (but in Elixir). Or is this something else?

I think livewire was inspired by phoenix liveview. I remember there was even a podcast interview about it.

Re: Phoenix 1.7 is View-less

#6

Post by tiffanyh » Fri, Dec 30, 2022, 8:03 PM UTC

Elixir/Phoenix has hit full-stride.

I feel like the next big unlock in user adoption is continued improvements to BeamAsm. Hopefully something on the order of 100-200% raw performance speed up. Note: I’m talking about raw perf, not concurrency.

A few other additions to Phoenix 1.7 include:

- verified routes

- tailwind built in

- additional web server support (bandit)

https://www.phoenixframework.org/blog/phoenix-1.7-released

Re: Phoenix 1.7 is View-less

#7

Post by gnutrino » Fri, Dec 30, 2022, 8:04 PM UTC

This makes sense to me. Views always seemed a like unnecessary boilerplate to me. Better to keep all the code together in one module, and just import common functions. On the other hand, I don't typically like defining the template in a sigil, unless it's a really small one, so I probably won't do that much.

Re: Phoenix 1.7 is View-less

#8

Post by sergiotapia » Fri, Dec 30, 2022, 8:08 PM UTC

I'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

Re: Phoenix 1.7 is View-less

#9

Post by oDot » Fri, Dec 30, 2022, 8:20 PM UTC

People using Phoenix Liveview -- how do you serve native apps relying on the same backend?

Re: Phoenix 1.7 is View-less

#10

Post by freedomben » Fri, Dec 30, 2022, 8:20 PM UTC

gnutrino wrote: post #7

This makes sense to me. Views always seemed a like unnecessary boilerplate to me. Better to keep all the code together in one module, and just import common functions. On the other hand, I don't typically like defining the template in a sigil, unless it's a really small one, so I probably won't do that much.

I agree in the case of HTML rendering, but I write a lot of JSON APIs and putting the JSON definition in the View has been very pleasant. It didn't say in OP, but how does this change an API? Maybe a `GreetJSON` instead of `GreetHTML`?