A few little concerns about Laravel 4

I jumped into Laravel as my PHP Framework of choice about a month ago after deciding to switch full time to PHP from Coldfusion. Though I’ve only used it for a month, I really believe Laravel 3 is an awesome framework. However, now that the beta 1 of Laravel 4 has come out, and I’ve been looking into what it would take to port my first Laravel 3 app to 4, I do have a few concerns and I’m not the only one.

I’m not so concerned about the controller/action naming conventions or the use of Composer in general, but the practical day-to-day stuff that will affect me as I’m developing.

One of the first things I noticed in my attempt to port over my app was the absence of the HTML, FORM, and URI (I think) helper functions. This was explained to be a result of using replacement packages available via Composer. That’s fine, but here’s my biggest concern regarding a heavy reliance on Composer (and this is not restricted to Laravel at all):

As a newbie I rely HEAVILY on documentation. The more you strip out of the framework and farm out to Composer, the more places I have to go to find documentation. This can be a pain.

Now I’m seeing there’s a movement afoot to buy a license for Redactor.js so it can be included in Laravel 4. That sounds great to me, but why would Laravel’s developers want to include a wysiwyg editor as part of the core, when they’re stripping out stuff like HTML and FORM helpers?
I can see not including a Twitter library like Zend, buy why remove something that was already there and relied upon by many developers?
I’m just ranting here, and I’m very hopeful that as things stabilize and the smoke clears, L4 will be awesome and even better than L3 has been for me so far.

But I’m still just a little concerned.