league/container 2.x dependency version conflict about route

[rmrhz]

Why not just use the RC release to test things out? Either way, most of the functionality would simply be the same. Given that you'll be also providing feedback whenever you'd encounter something

[AkenRoberts]

I certainly could use the RC release, and I will during my project's development. However, if an experienced developer like myself can run into conflicts, so can someone less experienced. And they will likely have little to no idea what to do about it. Providing even a small bit of documentation for how to circumvent the issue would be better than nothing. :)

On Sat, Nov 7, 2015 at 11:48 AM, rmrhz [email protected] wrote:

Why not just use the RC release to test things out? Either way, most of the functionality would simply be the same. Given that you'll be also providing feedback whenever you'd encounter something

Reply to this email directly or view it on GitHub:
#83 (comment)

[rmrhz]

I highly doubt inexperienced developers would run into problems. As you say, they're inexperienced. No intentional offense implied. Though if you can observe people who are using individual components such as these, safe to assume they know what they're doing.

[AkenRoberts]

In the world of open source libraries, that's a poor assumption to make. You always want to help your users, without assuming their skill levels. Sometimes people will require these libraries as they begin to play around, attempting to learn, maybe following a tutorial or two.

A simple blurb in a readme is a much better solution than convincing yourself that everyone is smart enough to not make a mistake.

[rmrhz]

Wrong context though, but still a good point.

Point is, whether experience can be assumed what I define inexperienced are on the borderline of venturing out of their comfort zone or simply saying just playing it safe. There's a different culture here on the other side of the world, and generalizing the idea is also a poor assumption.

[AkenRoberts]

I'm not sure I follow on what the "correct context" would be.

There's a different culture here on the other side of the world

That's an elitist attitude and exactly what people should consciously avoid.

[philipobenito]

I think this discussion has gone a little off topic. @cryode it is a general version mismatch error that I agree is confusing, however, for how close we are to release of the new version, I don't see too much benefit to documenting as the same people who would take the time to find that documentation I think would know where to look for the issue and see the version mismatch in a timely manor.