O$10: what is the rationale to skip O$9 ?

Bryan Brodie brb at appimatic.com
Tue Nov 6 20:59:50 EST 2018

>>On 6 Nov 2018, at 07:49, Bruno Del Sol <bruno.delsol at bydesign.fr> wrote:
>>>The ability to fix problems while you debug and see the effect of your changes right there and then without ever leaving the environment you are in nor having to restart anything, that is what makes it possible to double if not quadruple your productivity compared to other languages.
>>>Yes, the ability to change code while debugging it is the main <extra bold> unique selling point </extra bold> of Omnis !!!  No Java, Python, JS, PHP environment comes even close to this unique feature. 

Hi Bruno, $all,

I run an apache / MySQL server on my mac (MacOS 10.14) for development. 

I can open all my source code and log files using TextWrangler and make changes on the fly and re-execute (mac, windows, mobile) and see what happens.

It's not the Omnis environment, but it's a fantastic workflow for me. Very solid, stable, lean and no debugger (a good developer does not _need_ a debugger - I write trace text to the log files to figure out what's happening).

I develop in a minimalist operating environment that is close to actual live production. Less surprises going live.

>>On 6 Nov 2018, at 07:49, Bruno Del Sol <bruno.delsol at bydesign.fr> wrote:
>>>Omnis IDE delivers you out of the box several dozens of standard and design libraries ready to use, tested and integrated, and they maintain it for decades. To get the same features with a Java, Python, JS, PHP environment you gonna have to pile up a lot of external frameworks and libraries prior to code your first line. And then, congrats, you are now personally in charge of dealing with the rapid obsolescence and scary safety issues of each of these bits of code for the next 10 years

I made the jump from PHP 5 to 7 with virtually no issues. I use a conservative approach to code structure and design, honed over decades of seeing updates break things. My initial public-facing design template was not responsive, and now it is, and it cost me $25 to license it. 

Granted it took a little time to migrate to responsive design (five months back in 2016), but I hit Stack Exchange and googled heavily for solutions, and they are working well.

For example, I use the open source mPDF code to generate PDFs (invoices, etc), and it broke after migrating from PHP 5 to PHP 7.

It only took me 3 days to get the latest (v7 compatible) version of mPDF working again, because there is so much reference available on the web.

PHP is ubiquitous - almost every API offers a version and when they don't, there is always a way to use an external to do what I need. 

I interface with Google APIs (drive, mail, calendar, oAUTH) freely and it all works really really well. 

PHP is not necessarily what the cool kids use, but my customers could find a thousand developers to modify my code or schemas if I was out of the picture. 

Also, using google and Stack Exchange, there are a thousand reference points for obsolescence and safety issues - my code passes most confirmation / PEN tests.

After my new code / changes finally execute bug and vulnerability free, I migrate them to a Linux (centos - 'free' red hat!) server environment. 

I am able to produce small business solutions just like I did for years when I was running Omnis runtimes on Mac / Windows. 

My licensing costs are nil. Hardware is cheap - if they want to run in AWS, I have deployed there. I have no interest in containers at this point but I am evolving. 

All the gravy goes to my bottom line. I am developing a mobile ordering and payment solution for food truck operations that is going to be a goldmine. 

Again, totally cheap software licensing and inexpensive hardware (at the scale I operate) equals maximum flexibility for my deployment and financial model.

I am encouraged to see the responses to my original post asking for a native runtime for iOS and Android. This is what Omnis needs if it wants to dominate development again, like it did back in the late 1980s. 

Why I would need to 'suggest this to development' when the need for a native runtime for iOS and Android is so patently obvious?

Come out with an iOS / Android Omnis runtime, I'll invest $5000 / year (or more) in a proprietary Omnis solution. 

I could make a fortune with that product. We all could. It would be worth investing the time and money.

It would augment the work I have done in the LAMP / responsive design web application realm.

Otherwise it's probably gonna be the $249 Omnis version every few years, and Omnis will not survive that business model.

Bryan Brodie

More information about the omnisdev-en mailing list