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

Minimum Viable Phoenix

petecorey.com

Post reply on HN
Print view View original

1–10 of 29 posts

Re: Minimum Viable Phoenix

#4

Post by verttii »

seeker61 wrote: post #2

Another framework. May merciful Providence deliver us.

In all fairness it's been around for quite some time.

Moreover, the abundance of frameworks is not inherently a bad thing in my opinion. You don't need to learn it if it doesn't solve a problem for you after all.

Re: Minimum Viable Phoenix

#5

Post by theonething »

verttii wrote: post #4
seeker61 wrote: post #2

Another framework. May merciful Providence deliver us.

In all fairness it's been around for quite some time. Moreover, the abundance of frameworks is not inherently a bad thing in my opinion. You don't need to learn it if it doesn't solve a problem for you after all.

I'm not agreeing with the GP's attitude about more frameworks. In fact, I really enjoy working with Phoenix and am glad the author(s) put in the hard work to build it.

But

> You don't need to learn it if it doesn't solve a problem for you after all

is not true. I don't like React and I have to use it at work because that is what was chosen.

Re: Minimum Viable Phoenix

#7

Post by nicolas_siplis »

theonething wrote: post #5
verttii wrote: post #4

Earlier quoted context omitted.

In all fairness it's been around for quite some time. Moreover, the abundance of frameworks is not inherently a bad thing in my opinion. You don't need to learn it if it doesn't solve a problem for you after all.

I'm not agreeing with the GP's attitude about more frameworks. In fact, I really enjoy working with Phoenix and am glad the author(s) put in the hard work to build it. But > You don't need to learn it if it doesn't solve a problem for you after all is not true. I don't like React and I have to use it at work because that is what was chosen.

Whether or not you like React, the point is that it's solving a problem. Maybe not for you, but (I'd like to believe) at the very least for some of your colleagues.

Re: Minimum Viable Phoenix

#8

Post by colonelpopcorn »

theonething wrote: post #5
verttii wrote: post #4

Earlier quoted context omitted.

In all fairness it's been around for quite some time. Moreover, the abundance of frameworks is not inherently a bad thing in my opinion. You don't need to learn it if it doesn't solve a problem for you after all.

I'm not agreeing with the GP's attitude about more frameworks. In fact, I really enjoy working with Phoenix and am glad the author(s) put in the hard work to build it. But > You don't need to learn it if it doesn't solve a problem for you after all is not true. I don't like React and I have to use it at work because that is what was chosen.

Ostensibly, because it helps to solve the problems you've been hired to solve...

Re: Minimum Viable Phoenix

#9

Post by eropple »

theonething wrote: post #5
verttii wrote: post #4

Earlier quoted context omitted.

In all fairness it's been around for quite some time. Moreover, the abundance of frameworks is not inherently a bad thing in my opinion. You don't need to learn it if it doesn't solve a problem for you after all.

I'm not agreeing with the GP's attitude about more frameworks. In fact, I really enjoy working with Phoenix and am glad the author(s) put in the hard work to build it. But > You don't need to learn it if it doesn't solve a problem for you after all is not true. I don't like React and I have to use it at work because that is what was chosen.

React is nigh-universally agreed to solve a set of problems related to frontend web development. You may not recognize the pain of those problems and it may not solve them the way you like it, but the way you've attacked the sentence is really strange.
Post reply on HN