Jorge Castro
1 min readJan 6, 2019

Like this article says, PSR is a specification. For good or bad, PSR is condemned to the failure. People never learn!

For example, Java has the same feature, it is called JCP, and it is way more structured and ordered than PHP’s PSR.
However, we learned from Java’s JCP that standard and popularity are not always the same. In this case, JCP is collecting dust while Spring Boot (a framework of Java) is the way of go.
The reason is simple, both JCP and PSR are voted by a small fraction of the community, so a group of people is deciding what it’s good or bad arbitrary.

In my opinion, developers don’t want specifications but libraries.

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

Responses (1)

Write a response