[Info-vax] OpenVMS Development Annoyances

[Arne Vajhøj]

On 4/21/2019 6:12 PM, seasoned_geek wrote:
> On Sunday, April 21, 2019 at 12:48:36 PM UTC-5, Arne Vajhøj wrote:
>> QML is just declarative UI definition. Everybody wants that today.
>> Adobe Flex got MXML. .NET got XAML. Java got FXML. Etc..
> 
> No serious developer wants it. No qualified developer would ever consider it.
> 
> Let's take a scripted language which is interpreted at run-time. (No
> p-compiling is not compiling.) Then lets have your application load 2
> different engines because under the hood QML has to run a whole lot of
> JavaScript.
> 
> Only useless Script Kiddies want it or anything like it.

Declarative UI definition.

Maybe not what the Qt world wants.

But it is what the world in general wants.

Web.

Native Android and native iOS.

Cordova and Xamarin.

Windows WPF.

>>> While I'm sure, for the correct amount of dollars, Qt company (I
>>   > think that is Digia's new name) would be willing to port, but it would
>>   > require a valid C++ compiler and rather current JavaScript. Since VMS
>>   > on x86-64 is going to be server only it would require a highly
>>   > restricted Qt core be ported and QtCreator to be given cross
>>   > compile support for VMS.
>>
>> And will probably not happen. Too much work = too many dollars. :-(
> 
> A much more useful port would be of Qt 4.8, before QML really
> butchered the product. Just the core, none of the GUI because OpenVMS
> x86-64 is server only. QML became such a malignant tumor in Qt 5 I
> don't think it is possible to root it out.
Spending money porting something old and unsupported to VMS
seems pointless to me.

Arne