Re^4: Perl losing momentum ?

Caveat: I don't currently do Web programming (but would like to).

What language would you recommend for developing a front-end, and what mechanism (flat-file, TCP/IP, Sybase table, sockets) would you use for relaying its input to a Perl app?

Comment on Re^4: Perl losing momentum ?

Replies are listed 'Best First'.
Re^5: Perl losing momentum ? by Fletch (Bishop) on Jan 30, 2008 at 21:41 UTC
FSVO front end, Objective C and Cocoa (presuming the constraint of said front end residing only on OS X was acceptable :). For something more cross-platform, ~~Macromedia~~Adobe's Flex toolkit is pretty neat. Using it for some reporting stuff (the free compiler along with the for-pay charting and graphing components) at `$work` and it's not that bad (once you get over the fact that you're writing strongly typed Javascript (of a sort)). And in both cases there's XML and JSON output generators that can be POST'd to a backend web server using whatever Perl framework you want. More thoughts: Alternately in the ObjC case you could just write to flat files or an sqlite DB and pass things back and forth that way. Or use CamelBones and have your perl run as part of the front end itself (don't know offhand what the status of CamelBones on Leopard is though . . .). The cake is a lie. The cake is a lie. The cake is a lie.	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: Perl losing momentum ?
by Fletch (Bishop) on Jan 30, 2008 at 21:41 UTC

FSVO front end, Objective C and Cocoa (presuming the constraint of said front end residing only on OS X was acceptable :).

For something more cross-platform, ~~Macromedia~~Adobe's Flex toolkit is pretty neat. Using it for some reporting stuff (the free compiler along with the for-pay charting and graphing components) at $work and it's not that bad (once you get over the fact that you're writing strongly typed Javascript (of a sort)).

And in both cases there's XML and JSON output generators that can be POST'd to a backend web server using whatever Perl framework you want.

More thoughts: Alternately in the ObjC case you could just write to flat files or an sqlite DB and pass things back and forth that way. Or use CamelBones and have your perl run as part of the front end itself (don't know offhand what the status of CamelBones on Leopard is though . . .).

The cake is a lie.
The cake is a lie.
The cake is a lie.

[reply]
[d/l]