On Wed, Mar 04, 2015 at 12:51:21AM +0000, Isaac Dunham wrote: [cut]
> > However, I recognize you probably won't get C done in less than 2 hours > like you do with Python. That's exactly my point :) And sometimes having a Python code ready in two hours is much more important for me than having a perfect, efficient and neat C code ready for the same thing but in one day. Evan if C would always be my preferred language, there are some tasks for which C is not just right, *for me* ;) [cut] > > Now, I've used Python a little bit, and I've used C a little bit. > I won't say that Python/$scripting_language "should not be used, period". > But there are a lot of the features that come at costs that sometimes > seem to be ignored. I have been writing a little bit of Python and a little bit of C as well, and I think I have a rough idea of the shortcomings of both. This is why when chosing between writing something in C or in Python I also take into account the time you need to get the code ready to run, the number of times that specific code is going to be ever used, and how much important efficiency is for that specific task. Sometimes the answer is "C. Fullstop", some other times it is "Python. Fullstop", and some other times it might be "well, either would be just fine", and I usually opt for C ;) My2Cents KatolaZ -- [ Enzo Nicosia aka KatolaZ --- GLUG Catania -- Freaknet Medialab ] [ me [at] katolaz.homeunix.net -- http://katolaz.homeunix.net -- ] [ GNU/Linux User:#325780/ICQ UIN: #258332181/GPG key ID 0B5F062F ] [ Fingerprint: 8E59 D6AA 445E FDB4 A153 3D5A 5F20 B3AE 0B5F 062F ] _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
