So now we have no shipped preferentially treated extensions and we lack some way of distributing these. We already have TER and it works wonderfully (but could use a performance checkup). But what TER doesn't have is an official way to indicate that an extension is worth while; a favourite of the community proven to add value. Twitter has the "verified" badge, Apple's App store has the "Featured Apps". TER has a download count and graph which by the way lacks a time scale.
Why don't we introduce a "recommended" and/or "official" flag on TER? Allow such extensions to be listed specially. Raise them as top priority for suggestions. Ship the core extensions from our Swiss army knife as "official" extensions. And let the community decide which ones will get that distinction; not some arbitrary number hits from an Apache log (sincerely, no offence! I realise exactly why the solution is the way it is and I respect it! I only wish to make it better).
There's another perspective here. It's almost a tradition in TYPO3 that if XYZ does not fit our exact intention, we go ahead and roll our own. If we got around this and were able to pipe efforts into improving existing solutions I am certain we could all benefit. The examples are plenty. I don't mean to appear arrogant or hipster about this, but again: in my experience FluidTYPO3 and before that, FED, were first movers - later on joined by other alternatives like Gridelements and DCE (the former of which is at least planning to adopt the principles of Flux). This is nothing personal against those projects or their teams but they're solving the same problem already solved by FluidTYPO3. But they all make the same mistake of not relying on convention-over-configuration and not fully utilising the powers given to us through Extbase. If these efforts had gone in one direction instead, imagine where we could have been now?
So the second perspective is: having a way to selectively recommend extensions might encourage the pooling of efforts into those extensions. I hope FluidTYPO3 to be among those selectively recommended, but that's up to the community. But I digress into meta - ever so slightly.
(taken from https://fluidtypo3.org/blog/news/open-letter-call-for-conventions.html)
Just for the record: When Gridelements was created in early 2011, there was no existing Flux or Fluidcontent to be improved. Even when GE was released to the TER for the first time there was no Flux around yet. And there are good reasons, why we did not have Gridelements based on Extbase.
While "convention over configuration" might be a good idea and Fluid together with the VHS view helpers works like a charm in the frontend, the additional Fluid layer you created to configure old school flexforms IMHO still is questionable. Gridelements will have a dataprovider to enable Flux users to provide grid layouts based on Flux though, so people don't have to decide between the solutions and can use the best of both approaches without conflicts.
After all: These are the reasons, why we went into the same direction but used another path to get there. IMHO this is the good thing about an Open Source product providing a complex but solid API, that you are not forced to do it in a certain way, but are free of choice.