Skip to content

Instantly share code, notes, and snippets.

@alexanderschnitzler
Created May 19, 2015 18:28
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save alexanderschnitzler/13f167bedf3c82e5ee8f to your computer and use it in GitHub Desktop.
Save alexanderschnitzler/13f167bedf3c82e5ee8f to your computer and use it in GitHub Desktop.
Seperate Ways

Seperate Ways

Well, earlier this day I read an interview with Robert Lemke on the website of the german PHP magazine about the split off of Neos.

There is one quote from the article I used in one of my tweets. https://twitter.com/alex_schnitzler/status/600672348900065280 It says "Neos und TYPO3 haben sich zu unterschiedlichen Produkten entwickelt." which can be translated to "Neos and TYPO3 have evolved into different products." and I commented it as such "Falsch, Neos wurde nicht als Nachfolger für TYPO3 entwickelt." which means "Wrong, Neos has not been developed as a successor of TYPO3."

Later that day I received a direct message with the hint, that Neos actually has been developed as a successor of TYPO3. It's the moment I realized (again) that 140 chars maybe really are made for telling people how awesome your food is. However, I never intended to say that Neos wasn't planned to be the successor of TYPO3 – the Berlin Manifesto would prove me wrong in seconds – but that there hasn't been enough effort to make Neos the successor of TYPO3.

Robert Lemke says that the products evolved into different products which is simply not true. TYPO3 hardly evolved at all in about 7 years until there were too many doubts that Neos could be a proper successor anytime soon. Since then, TYPO3 evolved just technically, the main ideas of how it works are still the same. Actually Neos didn't evolve into the successor people waited for. It's as simple as that.

There's really no resentment from my side (any more). I accepted Neos not to be what it should be but instead I welcome the new drive of TYPO3. But there's one thing to say, now that Neos and TYPO3 officially go seperate ways:

Back then there was a clear vision and one distinct leader which clearly defined success, fail and responsibility. And for all people who may have put their faith, money and trust in the product and it's leader, there should be a little "sorry", at least. IMHO it's simply a matter of respect. Yes, it's easy to put the responsibility on something intangible like a community, a team or circumstances but boy, bew brave, take the blame and then there's a better chance that "let's stay friends" comes true.

@brgmn
Copy link

brgmn commented May 19, 2015

-1

@alexanderschnitzler
Copy link
Author

Code-Review or Verified?
I don't understand that gerrit syntax.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment