Slashdot Mirror
Delphi For PHP Released
Gramie2 writes "Codegear (now a subsidiary of Borland) has just released version 1.0 of Delphi for PHP, a RAD development environment (running on Windows) that produces standard PHP code. It features a large set of built-in components, including ones that use AJAX for database access; and Codegear is encouraging users to develop their own components. The framework, VCL for PHP, is open source, and documentation follows the PHP model. Initial database connectivity is for MySQL and Interbase (Codegear's commercial database that spawned the open-source Firebird), but more are promised."
Another desperate attempt by Borland/Codegear to appease their dwindling developer community.
Delphi is dead. Nothing to see here. Move along.
Y
"Web apps need to be written in proper code, with MVC, and templates, not as code embedded in individual pages."
No kidding? Have you ever seen a quality application written in PHP- it can do all these things and more. I've written many quality PHP applications that use a modified MVC architecture and has all the PHP code separate from the output templates. On top of that it uses OO where it makes sense to do so, it's fast and secure.
It helps to know what you're talking about before you spout off. Just because lots of people build rickety shacks out of stone, doesn't mean you can't build a solid castle out of it too.
It's this kind of generalization that pisses me off. It's not the language, it's your crappy skills.
Please mod me down as an old fashioned technology-phobic luddite .....
:!! out to a shellscript that generates a template given a table name. Its not rocket science.
.. its just a few javascript functions and a bit of PHP on the receiving end. You should be able to code that in your lunch break.
But I read TFA, and viewed the demo vid, and I cringed.
Maybe Im getting old, but Im perfectly content writing my PHP code in vim, and trusting that my template/rendering classes that I rely on will automatically look after the 'drawing of the screens' part of the application, in an efficient manner.
Im happy just writing code that twiddles attributes, performs calculations, and calls SQL. The only 'visualisation' that happens during coding time happens in my head. If you need to pull in the description of an SQL table at coding time - just
The mental state of mind that you need to be immersed in whilst coding is very different to the state you need to be in when testing, or viewing the result from an aesthetic POV. Coding belongs in a text editor, and anything else is a distraction.
Even Ajax - Im perfectly content coding that longhand. Its only a few pitiful javascript functions after all, and I dont see the need to wrap them in a framework. Lets not go around pretending that because we are using AJAX, that we are super-coders on the cutting edge of technology
OK, so my vim/PHP environment might put me back in the dark prehistoric stone ages, but at least I can sleep well at night knowing that none of my webby code is dependent on the fate of a 3rd party commercial product. After all - thats the main reason I use FOSS in the first place. The whole world wide economy can collapse in a radioactive heap tomorrow, and it wont affect my development at all.
And surely to goodness, isnt vanilla PHP with the standard libraries already way high level enough ? What sort of sheer sloth and laziness leads one to think that they need to front-end PHP with something even higher level ? Are we evolving into a race of Jabba-the-hut's, or what ?
Anyone that commits the blasphemy of 'developing an application' using mostly mouse-clicks honestly needs to be placed into a jar of isopropyl alcohol, and donated to medical science - it is just plain wrong, and always has been.
I tend to take the machine's side of the argument anyway - the less code the machine has to munch through in order to come up with any given result, the happier I am. The end result is just pixels on a screen when you think about it, and a lot of frameworks just add more and more layers of code munching for the machine to produce those same pixels and same behaviour. Silly - just keep it light, simple, scalable and avoid dependencies on proprietary products.
Whats so hard about that ?