TYPO3 Core

Benni Mack wrote in #note-3:

Hey Christian,

this is not really related to MenuProcessor (see the related issue) but HMENU sucks big time. I heavily recommend using EXT:menus (https://github.com/b13/menus) which solves all issues regarding caching for TYPO3 v9+.

I recommend not using `put into any feature from TYPO3 core`. That is not the advice I'd like to get from the TYPO3 project lead.

Ingo Fabbri wrote in #note-5:

I recommend not using `put into any feature from TYPO3 core`. That is not the advice I'd like to get from the TYPO3 project lead.

I don't understand the sentence, can you rephrase?

Benni Mack wrote in #note-6:

Ingo Fabbri wrote in #note-5:

I recommend not using `put into any feature from TYPO3 core`. That is not the advice I'd like to get from the TYPO3 project lead.

I don't understand the sentence, can you rephrase?

Ingo dislikes the fact that you recommend to not use a TYPO3 core feature :)

Ingo dislikes the fact that you recommend to not use a TYPO3 core feature :)

In other words: "fix it in core". Which is probably the intention long term, I hope.

What I personally dislike is that you need a lot of "insider knowledge" to successfully use TYPO3. A lot of it you don't get from reading the documentation (though tremendous effort has been put into it and I think it has improved a lot). I regulary attend bar camps, user groups. I worked in the documentation team for a while. All that helped me, but I regularly have moments were I would like to bang my head against the wall.

I have been using TYPO3 for 10 years but I am regularly frustrated because it is so hard to really use it well and has an incredibly long learning curve, things are often changed and often there are "secret solutions" where you have to spend a lot of time and effort to even find out about it.

Why is the menu such a mess from a performance point of view that you need a third party extension (from the project lead)? After years.
Also this extension (b13/menus) does not clearly state that it is a solution for performance in the README.

How long does it take new people using TYPO3 to find out how to create a website (professionally)?

On the one hand, the association seems to be putting effort to send people to other events (Symfony etc.), to create a "TYPO3 book", to make TYPO3 known or easier to use. On the other hand it still feels like a secret circle or cult where you cannot participate unless you spend a lot of time in camps and in Slack (or working somewhere where there is a good onboarding process and you have a sufficient amount of colleagues who specialize and share knowledge also helps).

Is TYPO3 a finished project? If yes, then you can put effort into marketing.

If not, I think zero effort should be put into marketing and 100% effort into fixing it.

This is not the best place to discuss it but I agree 100% with everything Sybille has written. And this is either a big coincidence or apparently a common problem.

Whenever I have to do something in TYPO3 I basically spend half my time figuring out why something isn't working instead of building or improving things.

For the past 4 months I have been working on upgrading to TYPO3 11 and PHP 8 (from TYPO3 10 and PHP 7) and the time it took me to figure out why things weren't working went from 50% to about 90%.

I have always had the impression that TYPO3 is "sold" as a car to compete in Formula 1. Unfortunately, then one realizes that in this splendid and modern car a bolt does not screw or a button is missing in the steering wheel and all this potential is canceled immediately. In the end, you certainly can't win the championship like that.

And then I wonder, why all this rush to release major versions with related breaking changes and new little useful features instead of stabilizing the current version as best as possible? Is it a question of ELTS economies?

I'm sorry to be so negative, I still love many things about TYPO3, but over the years my frustration has grown and at some point the rope breaks.

Thanks for your feedback. I am also frustrated.