There’s some news for you… a Web Developer starts a new project! Basically the same thing as hearing that a Doctor saved someone’s life, except way more anti-climactic and much less awesome!
Today, that changes…
Who am I kidding. If you’re still reading this, you’re in for a really big let down!
Now that you’ve read the title, and my asinine intro, what is LaraEdit?
LaraEdit is meant to be a platform that should be insanely easy to set up and start developing with any and all resources you need at your fingertips. Imagine a code editor that runs in your web browser that can actually be compared to Sublime Text or any of the JetBrains editors. Only this time you also get access to a real terminal, an SQL/ORM editor, a Dockerfile generator, a single package manager that can pull from Composer, NPM, Bower, PIP or Rubygems, and even a built-in Git client.
Sound far-fetched? I can assure you that all of this is possible, and more. But it will take quite a bit of time and effort. And since Forbes has no clue who I am yet, I have decided to make this project open-source. If LaraEdit sounds like a project you would like to work on, you can fork the project on GitHub and send me your pull requests.
LaraEdit is actually not a new project, just a revived one. There were two earlier versions that didn’t quite pan out. Third times a charm right? Ha ha, try telling that to a Baltimore Ravens fan (they’re currently 0-3)! But seriously, I started LaraEdit the first time in late 2014 as a Laravel package. I managed to get the code editor working as well as the terminal. However, there was still much left to be desired and then Taylor Otwell (the creator of Laravel) announced Laravel 5.
This meant that all of my work now needed to be re-done. Thanks, Taylor!
Of course I procrastinated a bit, why would I keep working on a Laravel 4 package when Laravel 5 was just a couple of months away? Then once Laravel 5 came out, all I could think while writing the second version is “I’ve already done all of this.”, “Why am I doing all of this again?”. Then I stopped altogether.
So why bring back LaraEdit now, what’s changed?
After putting so much time, thought and effort into the first two versions of LaraEdit, it has haunted me during every project since. I can’t work on a new application without wondering how much easier this would be if I had LaraEdit.
As for the changes… I would say that the biggest change is that it will no longer be a Laravel package. Instead, LaraEdit will now be a Laravel Application!
My thought process before was that you should be able to install LaraEdit in whatever Laravel project you were working on and on include it on your development environment. But that route is what forced me to keep up with Laravel releases.
Now that I have decided to go the full application route, it becomes standalone and it doesn’t really matter what version of Laravel it’s built on top of! Which means my code doesn’t become obsolete every ~6 months or so.
Well I guess that is enough rambling, I’ve got a ton of work to do! If you have any questions and/or suggestions, leave a comment below. Thanks for reading.