Skip to content

Instantly share code, notes, and snippets.

Alexander Schnitzler alexanderschnitzler

Block or report user

Report or block alexanderschnitzler

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile

TYPO3 Composer Integration (Wishlist)

This document gives an overview of the issues I see in the current composer implementation in TYPO3. First of all I'll write it in the form of user stories and afterwards write an actual text.

Composer Related Wishes

As a developer I want to:

  • ☑ composer init and require typo3/cms
  • ☑ install TYPO3 extensions via composer


This is statement regarding my tweet:

Still don't get that #TYPO3 Surf Hype. It's a NIH product and resembles everything we try to avoid in the community recently.

People started asking me about what I use instead, what NIH means and why exactly the problem with TYPO3.Surf is. As twitter only allows 140 chars, I decided to shortly write down this gist.

What is NIH and why does it harm?



  • Extension created by Kaspar, then Robert Lemke, Steffen Kamper, Dmitry Dulepov.
  • Later managed by Tolleiv Nietsch.
  • Applause for a dying open source project during TYPO3 Camp Stuttgart 2013 made me think.
  • Took over the development for 6.2 together with Wouter Wolters.


  • I am feelancer and code for a living.
View Seperate

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. 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 p

View the future of

TYPO3 Flow Performance

Yesterday evening our beloved @t3popcorn accoutn did post this tweet For all that cannot see it as the account is private: It has a link to in it and asked why Flow isn't part of the benchmark.

I then checked out the repository and tried to get Flow benchmarked as well and after some minutes it already worked quite well, though it just ran in the development context. But what exactly did I do? I just install Flow in a subdirectory with this command: composer create-project --dev --keep-vcs typo3/flow-base-distribution typo3flow as stated in At this moment of writing this command installs Flow 2.3. To test a real world sc

alexanderschnitzler /
Last active Aug 16, 2018
An open letter to the Neos development team

An open letter to the Neos development team

Dear members of the development team, CU a few days ago I commented the announcement, that Neos and Flow get rid of "TYPO3" as part of their names, as follows:

Removing "TYPO3" from Neos and Flow makes it easier to quietly abandon these products. \o/

Additionally to this tweet I had a small twitter conversation resulting in this tweet:

View segfault.css
/* - - - - - - - - - - - - - - - - - - - - -
Context Sensitive Help (CSH)
- - - - - - - - - - - - - - - - - - - - - */
a.typo3-csh-link span.typo3-csh-inline {
display: none;

Keybase proof

I hereby claim:

  • I am alexanderschnitzler on github.
  • I am aschnitzler ( on keybase.
  • I have a public key whose fingerprint is B1A9 6FD5 28B8 DE71 16F7 430C 7510 6759 FB60 C838

To claim this, I am signing this object:

You can’t perform that action at this time.