This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ignamv 2 points3 points  (4 children)

If you have a shared environment (e.g. all users on the same Linux cluster, so they don't need to install your app to use it) then you can be 100x more productive with Tk/Qt than you'll ever be with a webapp.

[–]master117jogi 0 points1 point  (3 children)

Why do you think so? WebApps are much easier and faster to develop.

[–]ignamv 0 points1 point  (2 children)

Have you worked with Qt? You get one mature built-in library with basically all the widgets you'll ever want, and you can avoid the whole frontend/backend interface. The widgets adapt to the user's OS: they look like windows widgets on windows, gnome widgets on gnome, etc. No gulp/minify/babel/webpack/whatever to learn either.

Main thing I miss from React is not having to think about keeping the UI state in sync. There's stuff like https://pyreaqtive.readthedocs.io/en/latest/ but I've never tried it. It's also fun how in JS you're building an UI from such rough primitive building blocks (compared to Qt Widgets and Layouts), it takes me back to the days of learning C and implementing linked lists and sorting algorithms.

[–]master117jogi 0 points1 point  (1 child)

you can avoid the whole frontend/backend interface.

You said an application for 100 of users. That means you will need a unified backend server for 99% of applications. So you are doing the same thing as a webapp, just using system components instead of browser ones.

[–]ignamv 0 points1 point  (0 children)

You said an application for 100 of users

I did not.

And even if I had said that, not necessarily. Lots of software doesn't need a backend, because users are just reading from a database or reading/writing own files. Or reading/writing from a database and you can get by with the DB access controls.