3 ms·

> And nothing "better" and more practical came out ever since paradigm wise. I think this is a pretty poor take on the problem. If that were really the case w

> And nothing "better" and more practical came out ever since paradigm wise. I think this is a pretty poor take on the problem. If that were really the case we'd all be using winforms 3.1 (or whatever the original version number was...). Here's the "Better" that a browser does - It's got standards and open documentation describing most behavior - It's got incredibly robust networking code. - It's got an insanely flexible markup language for describing both what form elements are present, but also how they're visually displayed. (Show me how to do animations in Lazarus... last I looked it was all manual) NOTE: Not only is it insanely flexible, it also is well documented and described by standards. - It avoided the trap of being GUI first at development time, encouraging an eco-system of tools that generate and modify the text based definition of the GUI you're going to present to users - It has good separation of concerns. My form elements can be styled completely differently by just swapping out a style sheet. - It has good (although often underused) A11y support. For most disabilities that you can think of. - It has first class debugging tools available, supporting a wide variety of environments. ---- That's what the browser brings. Is it heavy? Sure. Is it bloat? Not really.... depends a lot on your use case.

FpUser 5y ago
From that list the only valid points I see are - a) animations. yes you have to do it manually in Lazarus. or you can spend few days and write a component which would animate any published property of any component on a form. Will take a few days to write it in a flexible way and not to be ashamed to submit in public repo. I suspect such component maybe written by someone already but since I did not need it I did not research the area. b) Debugger is a sore point. It is adequate but falls way of behind what you have in browser or in Delphi (commercial IDE Lazarus is trying to imitate). But they're not standing still and it is getting better. c) A11y - Highly unfamiliar with the subject so you are most likely correct here.

FpUser 5y ago

From that list the only valid points I see are - a) animations. yes you have to do it manually in Lazarus. or you can spend few days and write a component which would animate any published property of any component on a form. Will take a few days to write it in a flexible way and not to be ashamed to submit in public repo. I suspect such component maybe written by someone already but since I did not need it I did not research the area. b) Debugger is a sore point. It is adequate but falls way of behind what you have in browser or in Delphi (commercial IDE Lazarus is trying to imitate). But they're not standing still and it is getting better. c) A11y - Highly unfamiliar with the subject so you are most likely correct here.