3 ms·
Frankstein-ing frameworks like this is asking for trouble. This smells like something that was made by devs because they hated working on WP, not understanding
by charlie0 2y ago
Frankstein-ing frameworks like this is asking for trouble. This smells like something that was made by devs because they hated working on WP, not understanding that the reason why WP is picked if often due to political reasons, not technical ones.
I predict two forces will turn these kinds of projects into spaghetti: Actual devs working on resolving issues with code, less technical people fighting to use plugins and other add-ons to add functionality.
- rob 2y ago> This smells like something that was made by devs because they hated working on WP, not understanding that the reason why WP is picked if often due to political reasons, not technical ones. Made by the roots.io team, who have been doing this since 2011: https://roots.io/about/ https://roots.io/about/ Other projects in this space include: https://roots.io/sage/ https://roots.io/sage/ https://roots.io/bedrock/ https://roots.io/bedrock/ Great projects!
- jrgd 2y agoI second this; have been using Roots “frameworks” for years now and cant state enough how great this is compared to wordpress-traditional-workflow. It’s great.
- newzisforsukas 2y agoLaravel itself is a Frankenstein with Symfony, so...
- solarkraft 2y ago> This smells like something that was made by devs because they hated working on WP, not understanding that the reason why WP is picked if often due to political reasons, not technical ones But that’s the point? When WP is picked for political reasons, this is how you can make it nice on the technical side.