Jump to content

Using a framework or not?


Digital
 Share

Recommended Posts

I make my own when I'm working on new sites, I don't know how to use frameworks anyway. A friend of mine did our layout for my site though (I didn't know how back then). 

Edited by Hare
  • Like 1
Link to comment
Share on other sites

I started developing in Laravel (I developed DStable in CodeIgniter.. which I'm unsure if that ever released, but then I moved over to Laravel). I will always use a framework for larger projects. If it's something small, then no, I don't use a framework. But if it's a large project, I will always use one. It has great security, stability, community, etc. There is no reason not to and reinvent the wheel in my eyes.

  • Like 1
Link to comment
Share on other sites

All from scratch. I work on a day-to-day basis with Wordpress development and really like concepts from how they do things, but I wanted the organization of Laravel. It's a mash-up between the two that speeds up development for adding new features to an existing feature set. Sort of a CMS MVC. :P

I am possibly going to add a library for database migrations though. Been looking at a few of those. It's something that doesn't make sense to code from scratch.

  • Like 1
Link to comment
Share on other sites

1 hour ago, Digital said:

For @Nate and @Bedouin, do you make use of any libraries or actually do it all from scratch?

I've developed the backend from scratch, however for the front end I'm using jQuery to handle communication with the server. As @halichu pointed out - for some thing there is no point re-inventing the wheel.

As for the backend though, I wrote it myself purely because I wanted it to work in a particular way which just wasnt possible using things such as Laravel and CodeIgniter.

 

  • Like 1
Link to comment
Share on other sites

I always use a framework for any large projects and use Laravel at work as well so use a framework most of the time. Overall, I would highly recommend using an already established framework. While you can build your own, you are going to take longer doing things that aren't going to make your project better by doing it on your own. Frameworks give you a good starting foundation with even lightweight ones including routing and other base functionalities. I also think a good Object Relational Mapper is great for speeding up developing and just make common database interactions easier. I also like using a template engine for front end code. Not strictly necessary but I think it keeps things cleaner and helps me keep backend logic separated from the front end.

  • Like 3
Link to comment
Share on other sites

I personally really stand by use of MVC frameworks for complex systems like pet sites. Some projects really don't need a framework, but as a programmer I've always felt my job is to keep things streamlined and organized so the code is easily expanded and read for future developers that might look at your project. Strictly looking at performance, overuse of a large MVC framework such as Laravel for a project that is small and really doesn't need much abstraction may be unnecessary, but in larger projects the layers of abstraction and extra tools are really invaluable for streamlining the production process.

Edited by koafox
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...