| |||||||||||||
Sobotka: Why GIMP is inadequateSobotka: Why GIMP is inadequatePosted Jan 13, 2011 16:11 UTC (Thu) by mgedmin (subscriber, #34497)In reply to: Sobotka: Why GIMP is inadequate by HelloWorld Parent article: Sobotka: Why GIMP is inadequate
Why not go all the way and recommend something like Python then? *Much* cleaner, terser and simpler than C++.
(Of course there's a cost -- larger memory usage, slower running speed. Just like C++ has costs that C doesn't have -- gotchas in the language design, longer compilation times, increased memory usage, slower application startup due to eager linking overhead for vtables, etc.)
(Log in to post comments)
Sobotka: Why GIMP is inadequate Posted Jan 13, 2011 17:27 UTC (Thu) by HelloWorld (guest, #56129) [Link]
It's all about tradeoffs. Python is slow and uses more memory. I also dislike dynamic typing, and it's easier to use a C library in a C++ program than in Python. If these aren't problems for you - great, use Python.
If instead you're looking for a programming language that offers both flexibility and suitability for systems programming (perhaps even in the embedded world), then C++ is in my opinion a reasonable option.
|
|||||||||||||