![]() I know that is very different from your use-case, so not saying you are wrong or anything, just that this is what annoys me about html/css. On the web I can do that with bootstrap (and it's 100.000s of themes), native I can do this with the native libraries but in the html5-for-desktop-apps space it seems I have to spend time on doing stuff I don't want to do or even care about to make it look anything different than vomit that is simply not worth the time. ![]() I don't want free-form I want something I can put together in a few minutes without having to think about design and it still having it look acceptable on the platform I deploy it on. > free-form "rectangles and text" building blocksĪs a backend dev, I find that the most annoying part. So when you use "native UI" please take the above into consideration. Adobe Suite must be cross-platform, right? Yet there are c), d) up until z) reasons why they do that, I can speak about that forever, e.g. They prefer GC-able runtime environments for those reasons. One of the reasons: "native UI" is not expressive enough.Īnother reason: these are complex UI systems with complex data model underneath and so complex update graphs. None of these are using "native UI" as you know. Productive applications: MS Office, Adobe Suite, even IDEs like Visual Studio, JetBrain, SublimeText, VSCode, etc. Such applications must follow modern UI trends - who will trust antivirus if it looks as dinosaur from prehistoric times? That's why AV vendors prefer to use CSS, just to minimize maintenance costs, see. 1 second looking on window to make decision what to use. So the UI shall be self descriptive, pictographic, etc. hot-keys don't work there - no one is bothered to remember them. The ones that used time to time (what I name as "one big red button applications") must have descriptive UI - e.g. There are two major types of applications:ī) and productive applications used 24/7 - parts of job workflow. My wife (as an example) has Windows notebook, iPhone and Android based book reader - "native UI" for her is meaningless at best. So "Native UI" these days shall look closer to default Bootstrap theme then to something that OS provides. But rest of us (99%, sic!) consume UI in form of Web sites, right? You (as a software developer), is one of 1% of UI users. Ĭouple of words about "native UI" and on statements like: "I (a hard-core software developer) prefer gray boxes". There was a thread by the author on Reddit some time back that vented the idea of open-sourcing the library. Pricing (even if fair comparatively) and the closed source is also a roadblock (for me). Īlso, as far as I can see it is not truly cross-platform, i.e. ![]() But the list of included libraries certainly look like it could compensate for some of that, with implementations that can mimic modern features like promises and CSS3 transitions. There are similar issues with the DOM and CSS. Their flavor of Javascript (TIscript) diverged from ECMAScipt more than 10 years ago, so there would be syntax switching involved when developing in Sciter and doing normal web development in parallel. Sciter is a small company (single person ?) project, but the list of enterprise clients is an assurance. Please correct me if I've misunderstood anything. For the benefit of anyone interested, these are my tentative conclusions. This has been posted a few times to HN and I've looked into it superficially without actually trying it out.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |