4 ms·
I find this a pretty unconvincing comment, bordering on bad faith. A lot of vaguely defined negatives with no details. > Deploying Phoenix is a nightmare when
by sho 4y ago
I find this a pretty unconvincing comment, bordering on bad faith. A lot of vaguely defined negatives with no details.
> Deploying Phoenix is a nightmare when compared to Laravel.
It ships with a Dockerfile which is simple to deploy if you know docker at all. How is this a nightmare exactly?
> In Phx you have to reinvent a lot of things and often, of course, choosing the wrong path.
Like what? Give examples. I find the ecosystem pretty well developed, actually.
> Also, Phoenix is bad in environments with bad wi-fi.
Do you mean the (optional) liveview, which your preferred framework Laravel is in the process of also implementing with blade/livewire?
Programmed in a reasonably defensive way, Liveview will perform and behave mostly like any SPA application - often better, because there's less front end code to load up front. Of course, in cases where internet access is known in advance to be bad, it should probably not be used. This will be a pretty rare case, though.
> The experience with 1.6 and 1.7 rc was bad
The RC process was long, yes, but how can you fault the framework for this? What could they have done differently? It sounds like you wouldn't be happy either way?
> PHP is made for sloppy web programmers (like me).
I think I know why you didn't have a great experience with Phoenix.
- biorach 4y ago> What a ridiculous comment. Firstly, I am not very inclined to take the advice of anyone using PHP in 2023 If you want your own comment to be taken seriously you should dial back on the bitchiness
- sho 4y agoYou're right, dialled back.
- jadbox 4y agoFwiw, I respect that you took feedback. It's special moments like these that reinforcement my faith in humanity (on the Internet).
- sieabahlpark 4y ago[dead]
- ravishi 4y agoI actually found it informative. It gave me a quick overview of the issues with this famous web framework that I would probably not find anywhere else.
- h0l0cube 4y ago> informative [...] of the issues with this famous web framework The conflation of LiveView with Phoenix web framework is dangerous misinformation. LiveView is just a subset of Phoenix, with very specific trade-offs and unfamiliar programming patterns compared to usual web development. I've found Phoenix to be very productive for regular web programming.
- toolz 4y agoGenuinely curious, but which part was informative of anything other than one users opinion? I'm a huge fan of elixir and found it to be one of the easiest languages[1] I've learned to date, so I'm definitely biased, but I'm struggling to find anything in GP's post that is informative in an objective way (outside of the tutorial thing that presumably posts more content). I believe I could replace php/laravel with elixir/phoenix in GP's post and be subjectively just as correct in stating my opinion. [1] the easiest standard library to learn...the OTP library is often treated as a core part of the language and that did take a fair amount of learning before it clicked.
- h0l0cube 4y ago> the OTP library is often treated as a core part of the language and that did take a fair amount of learning before it clicked. For me, probably the 2 most foreign concepts coming in with a non-functional mindset were GenServers and tail-recursion. They require a shift in mindset about how to handle state and do flow control. These two things would be stumbling blocks to beginners, especially someone who claims to prefer "sloppy" code
- toolz 4y agotail-recursion is just an implementation detail...but with recursion, I find non-programmers struggle no more with them than simple loops. It's only programmers who develop a strong familiarity with loops that feel some sense of unnecessary friction. Neither are more than code that says "do this thing until this condition is met"
- yurishimo 4y agoSmall nitpick, but Livewire is not part of the core Laravel framework; it is a community managed package.