Slashdot Mirror

First time accepted submitter waslap writes "I have a leading role at a small software development company. I am responsible for giving guidance and making decisions on tool usage within the shop. I find the task of choosing frameworks to use within our team, and specifically UI frameworks, exceedingly difficult. A couple of years back my investigation of RIA frameworks lead me to eventually push for Adobe Flex [adobe.com] as the UI framework of choice for our future web development. This was long before anyone would have guessed that Adobe would abandon the Linux version of Flash. I chose Flex mainly for its maturity, wealth of documentation, commercial backing, and the superior abilities of Flash, at a time when HTML 5 was still in the early stages of planning. Conversely, about 15 years ago I made a switch to Qt for desktop applications and it is still around and thriving. I am trying to understand why it was the right choice and the others not. Perhaps Qt's design was done so well that it could not be improved. I'm not sure whether that assessment is accurate. I cannot find a sound decision-tree based on my experiences to assist me in making choices that have staying power. I hope the esteemed Slashdot readers can provide helpful input on the matter. We need a set of fail-safe axioms" Read on for more context. The backing of Adobe, an industry giant, gave me what I later discovered was a false sense of security. I thought that the Flex framework would not get lost in a back alley like so many open source projects. We invested heavily in Flex and were disillusioned a couple of years later when Linux support for Flash was ended. (Linux support is vital for us for reasons outside this discussion.)

I had evaluated Adobe Flex alongside OpenLaszlo, which at the time had the ability to use a DHTML back-end instead of Flash with the flick of a switch. In retrospect, this alone apparently made it a better choice in the long run regardless of its flaky state when I first looked at it.

A similar scenario arose with CodeIgniter, which we chose for getting away from classical spaghetti PHP. CodeIgniter was recently dropped after we've invested a Tesla Model X worth of money into using it. (EllisLab Seeking New Owner for CodeIgniter.)

I am standing at a cross-roads once again as people are pushing Laravel [laravel.com] for PHP, and giving other suggestions. I am scratching my (sore) head and wondering how to prevent eventual failures in the future. It seems there is no way to predict whether a tool will survive.

Even in retrospect, when I consider my decision-making processes, everything was reasonable at the time I made the choices, yet some turned out to be wrong.

SimHacker writes "Sun and Laszlo Systems have announced project "Orbit": OpenLaszlo for J2ME. OpenLaszlo is an open source platform for creating zero-install 'AJAX' web applications with the user interface capabilities of desktop client software. The OpenLaszlo 'Legals' project supports multiple deployment runtimes, including Flash and DHTML, and soon J2ME! The FAQ says a proof-of-concept demo will be available later this year."

SimHacker writes "Sun and Laszlo Systems have announced project "Orbit": OpenLaszlo for J2ME. OpenLaszlo is an open source platform for creating zero-install 'AJAX' web applications with the user interface capabilities of desktop client software. The OpenLaszlo 'Legals' project supports multiple deployment runtimes, including Flash and DHTML, and soon J2ME! The FAQ says a proof-of-concept demo will be available later this year."

SimHacker writes "Sun and Laszlo Systems have announced project "Orbit": OpenLaszlo for J2ME. OpenLaszlo is an open source platform for creating zero-install 'AJAX' web applications with the user interface capabilities of desktop client software. The OpenLaszlo 'Legals' project supports multiple deployment runtimes, including Flash and DHTML, and soon J2ME! The FAQ says a proof-of-concept demo will be available later this year."

gse writes "The friendly folks at Laszlo Systems (of which I am one) have just announced the release of OpenLaszlo 3.0. Cool new features in this release: SOLO deployment (compile standalone .swf applications that don't need a proxy server), dynamically loadable libraries, a drawing API, and a bunch of optimizations. Info and downloads are at openlaszlo.org. (OpenLaszlo has been covered before on Slashdot.)"

gse writes "The friendly folks at Laszlo Systems (of which I am one) have just announced the release of OpenLaszlo 3.0. Cool new features in this release: SOLO deployment (compile standalone .swf applications that don't need a proxy server), dynamically loadable libraries, a drawing API, and a bunch of optimizations. Info and downloads are at openlaszlo.org. (OpenLaszlo has been covered before on Slashdot.)"

cying writes "Today, Laszlo Systems released their entire rich internet applications platform (standards-based, zero-install, all-singing / all-dancing) under the CPL. Check out their cool Laszlo-powered web site and see some rockin' groovy demos. Also, read the press release, news, and blogs; download the goods; and join the community."