Slashdot Mirror
PHP 5 Release Sparks Up PHP-GTK 2.0
joeldg writes "Since the release of PHP5 a lot of interest has reverberated down through the whole PHP community. In particular, there's a call for a PHP-GTK 2.0 which will utilize GTK2 and will have an entire rewrite of it from the ground up to make use of new features. Additionally there is an open call to help add to the documentation and to help with the website, post to and join the php-gtk-general mailing list to follow along with the activity.
The forthcoming PHP-GTK version 2.0 will bind GTK+ 2 to PHP 5. Until then, PHP-GTK 1.0.0 works only with PHP 4."
sure, writing gui code in a web language is more an entertaining trick then really good practice... but I'd still prefer a binding to wxWindows(or whatever they have decided to rename it too) then just gtk...
That's one of the reasons I bothered to learn python, so I could write once, run anywhere and the code would look native on any given gui
ah well
On Arrakis: early worm gets the bird. Magister mundi sum!
It's all in the theme...you can compare one theme to another in terms of looks, and one widget set to another in terms of performance and functionality.
Slashdot: Where people pretend to be twice as smart as they really are by behaving like children.
"PHP is the nicest language I know, aside from Javascript."
That's sad, thats really really really sad. You have NO idea how sad that is, but trust me, it's sad.
Sad so so sad.
LOL. Even I laughed.
;-) But I've tried the following:
Well, you have a low UID, so I can't dismiss you right off the bat.
C, C++, Java, JavaScript, Perl, Python, BASIC (and variant) Fortran, Pascal, and ASM. I've red about LISP, but have yet to actually write in it; though I think its right up my alley.
I've been around the block enough to not care about the low-level implementation issues. The older you get the less you care about re-inventing the wheel, and you just want to get things to work and get on to the next thing. That's why Linux is turning me off. I just want to install it and get the damned thing working, so I can get working. No etitinf fstab or my Xfree86 config file. No recompiling the kernel, etc. I come back to it periodically and I have to say It's made great strides, so I'm more interested than ever. Programming is very much like that. The more times you've been around the block, the more times you've been down that road, the faster you just want to get where you're going to get your task done. If I'm writing s/w for the space shuttle, I don't want to have to be insmoding drivers, unless I an writing them myself.
So when I said PHP and JS are nice, it is because they (like most scriping langs) don't bother me with low level implementation issues (unless I want to be bothered by them).
The other great observation I've made in my many years, is that it's not about the code, it's about the data. C is really bad at allocating memory and designing data structures. PHP and JS make that trivially easy.
I am a firmware devloper. I work in C 99% of the time. When I'm writing support software for the C code, I do it in some scripting language because it takes 20 times less to develop and I have no performance constraints. For the stuff I'm doing now, I have my scripts generate C files. I also generare SQL files from PHP structures.
JS and PHP may have thier quirks but such annoyances are [usually] inconsequntial. Dealing with a quirk or too is more time-saving than doing it in a strict, clean language like C.
What this is all getting to is that PHP and JS are great languages to me and my job. Or, IOW, YMMV.
Slashdot's rate-of-post filter: Preventing you from posting too many great ideas at once.
I agree with you that 2 years out is just too long to sit around waiting for a fix. From everything that I've read, its not the core of PHP that is incompatible with Apache 2 threading, but its the various misc modules. The PHP group needs to step up to the plate and make a hard decision. They should declare the incompatible modules depreciated and stop distributing them until they are fixed. That will be the only thing that motivates the module maintainers to get off their duffs and get the darn things fixed for good. No doubt that that kind of decision would cause lots of pain, wailing, and gnashing of teeth ; but sooner or later it has to be done. Now with the release of the PHP 5 series is as good as time as ever.
Yeah, I know somebody will say "shut up and hack", but I don't think your average end users should have to become PHP subsystem hackers, especially on a project as large and important as PHP.