React/JavaScript fatigue

Re:React/JavaScript fatigue by pbhowmic on Sunday December 27, 2015 @11:07PM (#10799798)

This is something I have observed about every language/framework front end combo I have ever used and I have done it long enough to go all the way back to Qt 3 and even before. There is no terse way to describe a UI. Period. C++ or Java I understand they are typed languages with an avowed aim of giving the programmer fine grained control over the program. Objective C may have become popular more recently but it too is an older typed language. The unbrevity of JavaScript is inexcusable and it extends to every UI framework it offers. Tooling is no way to try and ease the problem.

[ Parent | on HN ]

Re:React/JavaScript fatigue by pixie_ on Monday December 28, 2015 @12:36AM (#10800047)

The last time I felt productive doing UIs was with WinForms and before that VB6.

[ Parent | on HN ]

Re:React/JavaScript fatigue by laichzeit0 on Monday December 28, 2015 @12:54AM (#10800078)

At the end of the day, this is what the web community will ultimately end up re-inventing.

https://polymer-designer.appspot.com/

[ Parent | on HN ]

Re:React/JavaScript fatigue by snaky on Sunday December 27, 2015 @11:28PM (#10799863)

> There is no terse way to describe a UI

Did you ever seen Tk?

[ Parent | on HN ]

Re:React/JavaScript fatigue by epoch1970 on Monday December 28, 2015 @12:00AM (#10799948)

Tk was only ever feasible for very simple, often throw-away, UIs, and not much more than that. Tk can't be compared to Qt or the other full-featured UI toolkits that exist.

[ Parent | on HN ]