Slashdot Mirror

← Back to Stories (view on slashdot.org)

Get Your Moto On

Posted by michael on from the keeping-busy dept.

corz writes "Has PHP got you down? Are you tired of writing those Perl CGI scripts? Why not check out The Moto Programming Language. Released under the GPL, Moto allows for two modes of execution: interpreted and compiled. Moto is different from the rest of the field in that you can develop a site using interpreted mode for quick testing, then when the site is ready for production you can compile the it into an Apache DSO and serve it straight from memory. If you are looking to learn a new language, or would like to help with development, consider giving Moto a chance. Go download it now."

1 of 44 comments (clear)

  1. Re:Embedded languages - pah by Anonymous Coward · · Score: 1, Interesting

    Anonymous coward? Nah, just too lazy to remember my account.

    I'll step up and take some responsibility for the barrage of flames. ;-)

    Having worked with the Moto author a long time ago (anyone remember ptml?!) and thus likely contributed to his Moto predilection.

    Speaking from the better, faster, cheaper camp (management) Moto has the following merits:

    1) Limited Modifiability: As the presentation/view of a web based app, Moto represents a modifiable yet occult strategy - this is great for deploying highly customizable apps when you don't want your client messing with the actual code. Give'm perl or php, they're gonna touch it.

    2) Security through obscurity: (I'm ducking related flames on this one) But if you are an ISP deploying quick and dirty apps for customers and want apache modules with very little understanding of those apache modules, well cool.

    3) It is eventually C: The C output is quite nifty - it is probably safe to assume that this C is highly portable and could be used for some embedded applications. Don't people want to run dynamic pages from their wrist watches?

    4) Lifecycle: There are times when a system should be designed to be disposable. While a pretty brutal view, if a small system gets written in Moto, the big system will need a re-write in something a little more 'architectural'. e.g. j2ee, xsl, etc..

    5) Configuration management: Moto is simple, and doesn't have many moving parts.

    6) Cult: people love knowing something other people don't. That has managerial implications. ;-)

    Anyway enough of that, I'm steering clear of the technical discussion, - but as a niche language I think there are places where Moto could be used.

    - Rich