2 ms·

I empathise with the love/hate relationship w/ php. It is the most deployment friendly option out there (seriously). But as a programming language it can someti

by olefoo 17y ago

I empathise with the love/hate relationship w/ php. It is the most deployment friendly option out there (seriously). But as a programming language it can sometimes feel like like you are attempting to knit chainmail from steel wool; if you squint it looks sort of right, but you know it's not as sturdy as the real thing. My general rule of thumb is that if you find yourself using more than a few classes that aren't directly producing output, you should reconsider your application and move the heavy lifting into some piece of middleware that the php talks to.

jacquesm 17y ago
my biggest issue is the number of projects that I have that are already running PHP and the decade that I invested in to getting to know the environment. That's going to be hard to let go... Even java starts to look pretty good compared to PHP these days and I can hardly believe that I'm writing this. Not so long ago java was spelled s-l-o-w now it's only drawback seems to be that it takes about 4 times as many lines to do the same job. But at least the end result is somewhat maintainable, which is always a difficult thing to achieve with PHP. It's possible, but it will cost you a lot of extra time.