Re:Modern Python Performance Considerations
by dataflow on Thursday May 05, 2022 @06:51PM
(#31279259)
I don't think "I could use tool X for job Y" implies "X was the right tool for job Y". You could commute with a truck to your workplace 300 feet away for 50 years straight and I would still argue you probably used the wrong tool for the job. "Wrong tool" doesn't imply "it is impossible to do this", it just means "there are better options".
[ Parent
| on HN ]
The main thing is that Python is often in the top 10 choices for almost every problem on top of being insanely easy to learn and write; it also doesn't fragment its community - its standard library is so ridiculously large there are very few fault lines to break upon.
It's rarely the best choice, or even the fifth best. But if it's OK at a dozen things, then it makes it all but impossible to ignore. The fact that it sucks to write a GUI in is fine as long as I can put some basic "go" buttons and text boxes in front of a web scraper.
Re:Modern Python Performance Considerations
by formerly_proven on Friday May 06, 2022 @05:09PM
(#31289630)
IME writing a GUI in Python is pretty easy in a whole bunch of different ways, shipping is the annoying part.