4 ms·
I wonder how good a desktop app will work if we drop the JS part altogether and use HTTP and regular client-server architecture (i.e. every click will have to r
by johnnydoebk 10y ago
I wonder how good a desktop app will work if we drop the JS part altogether and use HTTP and regular client-server architecture (i.e. every click will have to rerender the template)? I guess something like Mozilla's servo can be used for that instead of a full featured Chromium to improve performance.
- tonyedgecombe 10y agoOr even better we could use the native window API's.
- chii 10y agoBut isn't the point of this project write once, run anywhere?
- pjmlp 10y agoJust throw away the HTML part and make a proper native application using network protocols, e.g. the "HTTP and regular client-server architecture". That is what I went back to doing in these last three years (Forms/WPF/Android/iOS/WP) and couldn't be happier to have regained some sanity away from the Web world, fad of the day with browsers bended to pretend native UIs.
- simplyinfinity 10y agoI'm a full stack dev that can't stand JS, now i started to do UWP (xaml) app, the learning curve is a bit steep, but the UI building is SOOO much better than html/css/js and everything behaves exactly as you would expect and vertical positioning just works!
- alexflint 10y agoAuthor here. I have been thinking about writing a react-like component system for Go, that outputs HTML. The major down side is that then you can't re-use much between your web-based app and your desktop app (which I think is a common pattern now).