PHP

This is the official* page on BuckysRoom for the PHP programming language. You can use this page to post cool stuff that you're learning about PHP, ask questions, and share why you love (or hate) the language.
Enjoy!
*whatever

file_get_contents could go to fgc
file_put_contents could go to fpc
mysql_connect could go to mc
mysql_real_escape_string could disappear completely
file_exists -> fe
get_html_translation_table should be ghtt or something similar
etc.

The more libraries and frameworks that are created the better. No one will really use the bad ones. The problem is that it's easier to create a framework/library than it is to change a programming language. But you're right, a good standard would help a lot. What kind of things do you think should be in the standard?

If everybody and their brother wouldn't try to make a new PhP framework (just like in JavaScript and CSS) and followed one standard then it would be nice. But you get everybody trying to come up with new and shorter ways to accomplish certain feats and it starts to get ridiculous. Just like with JavaScript and CSS. Don't get me wrong. I'm not saying there's no good ideas out there and there are a lot of smart people who figure out new things all the time. It's just that there's too many people trying to accomplish the same tasks differently. More cohesion and stability and a solid standard could be a possible fix to all the different frameworks and whatnot.

I think shortening is not such a good idea. It can lead to identification issues. You can't just see fgc and understand what it may stand for. Moreover, you can have a pretty hard time recalling it. Convention issues may follow, that is, you can't have a function named in a way and other functions named in a completely different way. Think about Java, its classes and methods are named in the best way, following a nice strict convention. PHP has a long way to go to fix its weird naming system.