[Qt-interest] Are there any disadvantages with OT

[Jason H]

I think the only point I was tring to make bring .Net/Java into it is that Qt cannot be used to make web services, and is definitely not ideal or websites. This is something that .Net/Java do far better. Using web services, we should be able to have our native client and a browser-based client too, both calling SOAP/Ajax. I imagine a system that compiles UI/QML files to HTML. (Or a browser plug-in)



---------------
Ben Said:


Personally I wouldn't use .Net or Java for web-apps. Call me old but:

- If you're doing a website, then make it a website, not an embedded program ala Flash/Silverlight/what-have-you. JavaScript/ECMAScript is often more than enough to do most websites, and AJAX makes it even more so.
- If you need more then just make a native application; it'll run faster and perform better; plus you remove the limits that would otherwise be placed on you (e.g. hardware access, etc.). If you're concerned over whether or not a user can install it, then come up with a way to do web-deployment to a sandboxed install - e.g. running from /tmp or %TEMP% - so that's not much of an issue. More likely than not, you need more than what your environment can provide.
- If I really had to do more than JavvScript/ECMAScript could provide client-side, then I would do Java; but then I'd be doing a bigger more full-fledged app and have to justify why it's not a regular application to start with - and there really are only very few areas where that is really justifiable.

Ben

P.S. Yes, I've used .Net for websites; it sucks pretty badly. There are far better ways to do websites.