I switched from PHP to Java once again, after a few months, to add new features to JetriX (Java QetriX :-) Those switches always hurt: different environments, different editors, different coding habit requirements, different debugging. But this time it was... different.
Even after quite a long time with PHP I didn’t have much struggle, because core parts of QetriX has been already made and my current task was mostly to update converters, datastores and modules. And the only difference between QetriX in Java and PHP were in variable types – hints and “arrays”.
This was my main goal with QetriX, to unify programming. I know QetriX isn’t optimal and it even may take some worse parts of a language, but ultimately it saves me time I'd otherwise spend on Stack Overflow, and overall it actually works quite well.
To be honest, I mostly make rather simple CRUD stuff nowadays, but even than it’s wonderful to see, that QetriX is capable to make it work smoothly only with general QView, QList, QForm and QElem components.
I’ve always tried to do the most optimal solution, but sometimes it’s obviously pointless. On the other hand, QetriX is for me a nice way how to teach myself new languages in the futures. Perl? Python? Ruby? Well, probably all of them, one at a time.