Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #76741 > unrolled thread
| Started by | David Palao <dpalao.python@gmail.com> |
|---|---|
| First post | 2014-08-21 17:26 +0200 |
| Last post | 2014-08-21 17:26 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Python vs C++ David Palao <dpalao.python@gmail.com> - 2014-08-21 17:26 +0200
| From | David Palao <dpalao.python@gmail.com> |
|---|---|
| Date | 2014-08-21 17:26 +0200 |
| Subject | Re: Python vs C++ |
| Message-ID | <mailman.13253.1408635277.18130.python-list@python.org> |
Thank you for the interesting answers. Just a clarification. Actually for the scope of this question, I consider C and C++ quite different. At least when they are "properly" used (eg, you could use C++ as a better C, but this is not C++ in its full glory). In my opinion, if all that you want is performance, coding critical parts in C or Frotran should be enough. Or even Cython. As far as the fraction of code that turns out to be critical is relatively small. But C++ is a monster compared to C. And I realize it requires a huge amount of time and practice to master it. The question is whether is it worth as a generic approach or not (*). I tend to think that it isn't that useful. Best, David (*) as some of you already mentioned, you could need C++ for joining a specific project, for instance. But that would not imply anything about how well suited is C++ for that particular project.
Back to top | Article view | comp.lang.python
csiph-web