3 ms·
Anything that liberates me from the current state of matters is welcome. The current state of matters is: use CSS preprocessor to generate CSS use fram
by flavio81 9y ago
Anything that liberates me from the current state of matters is welcome. The current state of matters is:
use CSS preprocessor to generate CSS
use framework (i.e. React) to transformate pseudo-HTML component model to HTML5 at runtime
use a tool like Babel to transform your-favorite-pseudo-JS (i.e. Typescript) to the JS-supported-by-the-users-browser-at-that-session
... all of this only for making alive a GUI.
Seriously, it is like a sick joke. HTML was never designed for declatatively describing an UI and we have had to kludge it for the last 15 or 20 years. First, with forms and input tags and postbacks, then with AJAX, now with S.P.A. tools. It's still a heap of kludges.
The sooner we can have a good,state of the art, portable, declatative UI language, the better.
- majewsky 9y ago> all of this only for making alive a GUI. All of this for making alive a GUI using the 2017-summer-season toolchain. Meanwhile, plain HTML with <form> elements and server-side processing miraculously continues to work.
- flavio81 9y agoYes, but "plain HTML with <form> elements and server-side processing" is not what the users (and thus our customers) expect, for good or bad. Of course i would be very happy if I could still do everything done in such way...