[Info-vax] User Interface Design, Implementation

[Arne Vajhøj]

On 6/7/2019 5:35 AM, Richard Maher wrote:
> On 7/06/2019 8:54 am, Arne Vajhøj wrote:
>> On 6/6/2019 6:45 PM, Richard Maher wrote:
>>> On 5/06/2019 6:59 am, Arne Vajhøj wrote:
>>>> There are probably way less GUI frameworks available on VMS than
>>>> the more popular platforms.
>>>>
>>>> But if the GUI framework is available on VMS, then it should
>>>> support MVC just as well as on any other OS.
>>>>
>>>> Various Java frameworks (Swing, Struts 1, Struts 2, JSF, Spring MVC).
>>>>
>>>> Various PHP frameworks (Laravel, CodeIgniter, Symfony, ZF, CakePHP).
>>>>
>>>> Maybe RoR and Grails would run as well.
>>>
>>> I and most others now use mvC or just "C"ontrollers for RESTful APIs. 
>>> Any language could support this.
>>
>> Without M then I would consider it to be a very trivial application.
>>
>> :-)
> 
> Please explain. JSON in, JSON out,

M in MVC represent/expose the business logic - the data and the rules in 
the application.

No M (or equivalent of M in non-MVC context) means no data and no
business rules.

>> But yes - no V - or you can say that V is moved to client tier.
>>
>> On the other hand some JS frameworks talk about full MVC client side:
>> AngularJS, Ember etc..
> 
> Can someone **please** explain to my why they would willing handicap a 
> project with AngularJS React/Redux or Vue??????
> 
> TypeScript, Node, NPM, Bootstrap, Babel transpiling/dumbing down your 
> code to previous versions, Lint, LowDash, Wank . . .
> 
> What do you perceive Angular, React, and Vue do for you? Apart from 
> wreck your app's performance and team productivity.
> 
> Turn on debug and just see how many unnecessary times your Render() 
> method is called.

I don't think I have the experience to argue exactly what value those
frameworks provide.

I can observe that the majority of client side developers use
those frameworks.

Arne