I switch between programming languages quite a bit; I often wondered what happens when having to deal with the different syntaxes, does the syntax allow you to be more expressive or faster at coding in one language or another. I dont really know about that; but what I do know what keys are pressed…
Trying to decide between best tool for the job, or something a bit easier for non-techies. I’ve had an idea for a little project (yes, another one) but the software I want to use, Sphinx is not common on Shared Hosts. I’ll be releasing it as an Open source project, but the lack of shared host support will limit the perspective user-base.
Only those with a minimum of VPS and enough know-how to install and configure Sphinx will be able to run it. Not exactly the casual user market. But then again I don’t even know if the project will appeal to casual users, or anyone so it has to be fun to build for me, and I kinda wanna learn how to use Sphinx. Plus anytime I’ve had to roll-my-own search, its sucked. This should help me on my work projects from now on as well.
I’ve still got 2 personal projects to get out the door first so I have time to decide…
I’ve just been looking at a PHP MVC Framework by a very talented Twitter friend of mine and while it does look great, and I will be using it in my next project, it suffers from the same flaw as many of the others. Web root pollution.
The diagram above shows how a framework should be laid out.
It is more secure, easier to upgrade and IMHO neater than having everything in the Web-Root. It is also the first thing I do when I perform a new CI or Kohana install.
I also think this might be how Django and Rails does it. But I’ve only ever had a fleeting glance at both, so I might be wrong.
I understand why Framework authors do it this way, not everyone’s shared host lets them have folders outside of web-root. But the most secure way should be the default, with instructions for moving folders into web-root if required for host.
Click view raw above, paste the code into a new file. Save as ‘something.php’ and run it. Then spend the next 15 minutes trying to figure out what the syntax error on line 3 is.
