this post was submitted on 02 Aug 2023
60 points (100.0% liked)

Programming

13373 readers
3 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 1 year ago
MODERATORS
alyaza@beehaw.org
Hexorg@beehaw.org
remington@beehaw.org
60
Tailwind CSS, and the death of web craftsmanship (pdx.su)
submitted 1 year ago by Paradox@lemdro.id to c/programming@beehaw.org
60 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] argv_minus_one@beehaw.org 1 points 1 year ago

QT, writing C++, or both?

Qt.

Paying for a good technology can be cheaper in the long run if you save development time.

Only until the price gets jacked up beyond what you can afford, and then you're scrambling to rewrite your entire application to use something else that's still affordable.

And sure, developing in C++ is more expensive than JavaScript, because you can’t let cheap web code monkeys do it.

An awful lot of code is written in C++, so I'm not sure that was ever a serious constraint.

I think I made it quite clear, that I set the scope for the desktop. There are several.

Sure, if we're targeting desktop only, then there are lots of options: GTK, wxWidgets, Swing…

But what does it matter? You can't ignore mobile in 2023.