this is very cool, I think the first thing most people do when starting a new Laravel project at the moment is things like deleting the models directory, creating a src folder etc, this should save a bit of time doing that stuff.

Really what 4.3 should offer is options. The new file structure is good, but I think continuity is critical. I would like to see the current file structure remain for the new blood coming from other frameworks. What I would strongly suggest is the option to install the new structure, or the 'classic', by adding a parameter to the composer command to create a new Laravel project. As with any tech project that starts off well, the most vocal community members are the power users. The tendency is to support these users by making the product more and more 'techy' to the point that newbies are no longer attracted. I believe it is critical that Laravel keep a door open for newbies.

My opinion is that a laravel newbie presented for the first time to 4.3, and getting the same explanation depth we received for 4.0/1/2, should learn the new structure without too much trouble.

The real problem is not Larave itself, it's the growing amount of tutorials for free all around the web getting outdated and building frustration/confusion to the community.

@larapetit Just my outlook here, but the psr loading in the app structure with everything namespaced would allow you to make pretty modular code. This would give you more options for a flexible setup with less work. Currently to do this in Laravel takes a little work but not much.

The only problem I ever see with options is at some point too many options just create a mess. You have to have opinions and make decisions about some things, right? I do agree on making things accessible for newbies (I was once one myself) but also the want to learn about some of the concepts that drive frameworks like this should make you a better developer in and of itself.

@alfonsan I will say I learned on 3 and by the time I kind of understand something 4 happened and then once I wrapped my head around that 4.1 and 4.2 happened. I was pretty frustrated for a long time.

I was watching a video from the NY Laracon about hexagonal architecture just before I watched Jeff's first video on the new features. Looks like a move in the hex direction, which is very, very cool.

Seems Taylor has some tricky decisions to make without Laravel becoming too opinionated about structure. Hats off to the fella, it would be very easy to start off in the wrong direction and ruin what makes the framework such a joy to use.

I'm intrigued.
Where should I put my models and views?

I understand an MVC framework when Models, Views and Controllers are in maps named after what's in them, and all on the same level.

But since everybody here sounds excited about the changes,
there is probably some very smart logic that I just don't get (yet).

Can anybody explain why this is cool in just a few words?

In a few words I find removing the models directory leads to better structured applications.

If you're building a very small application throwing a few models in the models directory is fine. But as they get bigger it's beneficial to separate your application into smaller classes which have clear responsibilities.

Where would you put them? maybe having a look at this application may help https://github.com/LaravelIO/laravel.io

One thing I don't like with this change mind is the removing of things like the the form builder and the db migrations and seeders from the out of the box soultion

@pobble Do you have a link to this video?

@ross.edman - See here: http://userscape.com/laracon/2014/chrisfidao.html

I have no idea why language files are out of the app directory? And why removed the models directory? everyone still will create this directory manually :) And what actually means the "app" directory? So how do I must create multiple websites with one laravel?

Godamn, who necro'd this thread lol.

I thought the folder structure had changed again.