alexanderschnitzler

Keybase proof

I hereby claim:

• I am alexanderschnitzler on github.
• I am aschnitzler (https://keybase.io/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:

alexanderschnitzler

/* - - - - - - - - - - - - - - - - - - - - -
Context Sensitive Help (CSH)

- - - - - - - - - - - - - - - - - - - - - */

a.typo3-csh-link span.typo3-csh-inline {
	display: none;
}

alexanderschnitzler

TYPO3 Flow Performance

Yesterday evening our beloved @t3popcorn accoutn did post this tweet https://twitter.com/T3Popcorn/status/582994007858368512. For all that cannot see it as the account is private: It has a link to https://github.com/kenjis/php-framework-benchmark 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 http://docs.typo3.org/flow/TYPO3FlowDocumentation/Quickstart/Index.html. At this moment of writing this command installs Flow 2.3. To test a real world sc

alexanderschnitzler

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 p

alexanderschnitzler

#region Assembly mscorlib.dll, v4.0.30319
// C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll
#endregion

using System;
using System.Runtime.InteropServices;

namespace System.IO
{
    // Zusammenfassung:

alexanderschnitzler

#region Assembly mscorlib.dll, v4.0.30319
// C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll
#endregion

using System;
using System.Runtime.InteropServices;
using System.Security;
using System.Security.AccessControl;

namespace System.IO

alexanderschnitzler

#region Assembly mscorlib.dll, v4.0.30319
// C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll
#endregion

using System;
using System.Collections.Generic;
using System.Runtime.InteropServices;
using System.Security;
using System.Security.AccessControl;

alexanderschnitzler

#region Assembly mscorlib.dll, v4.0.30319
// C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll
#endregion

using System;
using System.Runtime;
using System.Runtime.InteropServices;
using System.Threading;

namespace System.IO

alexanderschnitzler

#region Assembly mscorlib.dll, v4.0.30319
// C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll
#endregion

using Microsoft.Win32.SafeHandles;
using System;
using System.Runtime.InteropServices;
using System.Security;
using System.Security.AccessControl;

alexanderschnitzler

#region Assembly mscorlib.dll, v4.0.30319
// C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\mscorlib.dll
#endregion

using System;
using System.Collections.Generic;
using System.Runtime.InteropServices;
using System.Security;
using System.Security.AccessControl;
using System.Text;