The future of Codeigniter

# About the state of CI3
@narfbg was the only long time maintainer of the CI3 repo in the last 6 years or so. He stopped supporting it in mid May. Since then no issue or pr was handled by anybody. The whole repo is abandoned. Bc of this i think we can say its basicly dead. CI 3.2's large new thing should have been exceptions in the core but it was developed by Jim and also he stopped to work on it long ago. I'm using the latest dev branch in production its seems stable enough for me. And yes I'm still starting new projects on it! My ecommerce, crm, erp like systems are all based on CI3.

# About CI4
@Davcon you mentioned some hollistic problems and there are no clear answers for those as I know about, the project lacks any long term vision. Also this is a non profit not like Symfony or Laravel. Lonnie did everything he can do in the curcumstances but he's only one guy and have to mention that he isnt the owner so he almost can't make any money from it unlike Taylor or Fabian. In the recent months some new devs starts to gather around the fw and I glad to see that but they need time to create a whole ecosystem.

I don't know why you think CI4 has way worse performance... its perform slightly worse but not rlly significantly also if you use caching you cant see any difference.

In CI4 you use namespaced "modules" and widget like view cells or you can create a simple widget base class to mimic the HMVC behavior.

# Some further info for you
- CI AFAIK currently owned by a foundation https://forum.codeigniter.com/thread-74677.html
- The HMVC problem was solved 2 years ago in the wiredesign bitbucket repo by multiple contributor but never merged. If you took 10 sec to look around you would found it. I'm using one of it in prod.
- Copyright notices are exactly the same in every other fw using MIT license the only difference is that in CI its included in every file which decision was made way back in 2011? by Ellislab + the Reactor team if I remember correcly, why? I dont remember... search for some ancient podcast about it...
- You mentioned some rlly fcking large bs, you clearly dont have a clue about the industry at a large... about packagist/npm, angular etc... Im only laughing... om my... DDD I can find sources about earth is flat but suddenly it doesnt become real... DDD

## Why anybody should use CI4?
I dont have a clear answer but these are the advantages:
- simple, beginner friendly structure (ofc you have to know what is a class and a namespace but its now php 101... if you dont know about it pls dont work in this industry yet)
- still fast, faster than sf or laravel
- orm like features without the perf penalty of a real orm
- stable api, there are no breaking changes every month (unlike laravel... i had a project which was migrated from l3 to l5... l3>l4 was almost a complete rewrite - just like ci3>4 now - but 4>5 migration took almost a month too)

## Why you should not use it?
- its not really stable (see issues on github)
- db support is lacking compared to ci3
- lacks the community
- lacks the vision

## My personal stance
I like some aspects of the new fw but not all. I have huge problems with the architecture I discussed some of it in the forums years ago. Its not built for me or my company. After the rewrite the community doesnt get any real advantage from using it besides some familiar naming or simplicity.
I will stay around bc i have to. My entire company is built around CI3. But still dont know what i will use in the long run.

## +1
@Davcon Where are the resources blog posts, videos you created? Im rlly curious...