3 ms·
"Blandly practical" is the reason I still use python as my go to language for almost everything I do. The language is nice and stable, support for it is wide s
by dagw 13y ago
"Blandly practical" is the reason I still use python as my go to language for almost everything I do. The language is nice and stable, support for it is wide spread, there are nice and stable libraries for everything I need and so on. Python is the only language where I feel comfortable that can sit down and know I'll only have to think about my problem. I like that.
I'm currently keeping my eyes on both Julia and Rust and regularly try to do things in Haskell and Clojure, but basically every time I start a new non-trivial project in a new language I often end up at a point where I'm facing a language problem not a problem domain problem. How do I deploy language X on platform Y and make it talk to application Z, why is there no library to read/write .foo files, how to I make these two incomplete, buggy, almost-but-not-quite-overlapping libraries I found on github play together.
And don't get me wrong, that can be a fun challenge in its own way, but I don't always have time or desire to take 2 weeks out of what was really supposed to be a 2 week project to write a library to do something that would take me 2 minutes using a stable well tested python library.
I don't know, maybe it's just me getting old, but these days I'd much rather spend my time solving problems using programming than solve programming problems, doubly so when people are paying me to solve problems.