General > General Technical Chat
How many people code in C these days, and if so, why?
Picuino:
--- Quote from: IDEngineer on May 13, 2020, 04:34:51 pm ---
--- Quote from: engrguy42 on May 13, 2020, 01:17:54 pm ---I have little tolerance for the command line as well as other user-unfriendly stuff
--- End quote ---
That's funny, the vast majority of the one-off tools I write are command line based because I'm simply trying to get some task done, and don't want to waste time on a "pretty" GUI. In my humble experience, creation (and the seemingly endless fine-tuning) of a fancy front end takes far more time than writing the code that actually does the work in question. If it's not a commercially shipping product, I don't care what it looks like... I care that it gets the job done, and the faster the better.
This is not meant as an insult to those with different priorities, just another data point to consider.
--- End quote ---
I can say the same of the tools that I program for few uses.
When I want to complicate things a bit more and add options, I usually add them in a separate file called options.ini with a list of options that are self-explaining or with comments. That is easier to use than the command line when there are many options and it is still easy to implement in languages like Python.
engrguy42:
Silicon Wizard,
Really, you don't like my humor? :D
If you have an unbiased reading of what I actually post (not what you want to read in between the lines) I've been merely mentioning an option to C (the original topic) that nobody else has mentioned, in order to provide reasons WHY C might not be the language of choice for everyone. But over and over I have been the one saying that whatever tool fits the job is fine. How is that bad?
I've actually (as I usually do) been giving examples to show WHY C might not be the go-to language for some in the engineering world. Real world examples. From an engineer. Others rely on vague generalizations and dismissals, and unsupported opinion on stuff I'm increasingly starting to believe they just have no experience with.
As I've said, I don't care about software. I don't "like" one tool or the other. I'm not a fanboy. I don't take this stuff personally. Unlike others who make personal attacks against those who disagree.
Some languages are more frustrating than others, but that doesn't mean I don't use them. Or at least try them. And I try not to dismiss stuff without trying it. And I try not to make blanket, unsupported dismissals, which seem to be common here. As do claims of "you derailed this thread" by those who couldn't actually care less about whether anyone stays on topic, they just need some mud to throw.
Picuino:
--- Quote from: SiliconWizard on May 13, 2020, 04:35:51 pm ---Unfortunately, this thread now is IMHO growing a significant probability of ending up locked due to it completely derailing. Nice job.
--- End quote ---
To focus the topic, the problem is not how good are other languages to make GUIs or other similar things.
The initial question is how many people still use C and why.
I no longer use C on the PC. I did it before, but now there are better languages for that environment.
But many programmers still make C programs for the PC (operating systems, office automation, programming languages, ...)
In the world of microcontrollers C it is still one of the best tools, not yet surpassed. Although there are those who program in C++, its advantages are not so many as to displace C.
Karel:
--- Quote from: Nominal Animal on May 13, 2020, 04:22:00 pm ---That said, PyQt5 documentation is annoyingly hard to locate;
--- End quote ---
https://doc.qt.io/qtforpython/
https://doc.qt.io/qtforpython/api.html
https://doc.qt.io/qtforpython/modules.html
Nominal Animal:
--- Quote from: Karel on May 13, 2020, 05:28:02 pm ---
--- Quote from: Nominal Animal on May 13, 2020, 04:22:00 pm ---That said, PyQt5 documentation is annoyingly hard to locate;
--- End quote ---
https://doc.qt.io/qtforpython/
https://doc.qt.io/qtforpython/api.html
https://doc.qt.io/qtforpython/modules.html
--- End quote ---
Those are for PySide2, not PyQt5, though. The Debian (and thus Ubuntu, Mint etc.) python3-pyqt5 still use the RiverbankComputing GPL (non-LGPL) Python bindings, not the official ones. The official ones are relatively recent; I believe the PySide2 packages were added to Debian in July 2018.
(For a long time, there were no "official" Qt bindings for Python at all. Debian and Debian-derived Linux distros used PyQt4 and PyQt5 bindings maintained by RiverbankComputing, under the GPL license. PySide2 is the relatively new, official set of Qt5 bindings for Python.)
There is a python3-qtpy compatibility module that automatically switches between PyQt4, PyQt5, and PySide using the PyQt5 "style".
Are the two bindings identical, or close enough? I do not know. But I didn't want to assume the two are identical, and get bit at some point.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version