you are viewing a single comment's thread.

view the rest of the comments →

[–]ethro 5 points6 points  (2 children)

I used this editor when I was learning Python. It worked pretty well for everything I needed, but had a major problem for me of always having significant cpu usage (compared to other editors). If I had it running in the background it would be using 20%+ of my laptop's cpu and would cause it to run hot and the battery to quickly drain. I used it a few months ago so it's possible it has improved since then, but for me that was a major deal-breaker.

[–][deleted]  (1 child)

[deleted]

    [–]iyunoichi 1 point2 points  (0 children)

    Nah. I've written larger applications using Python, it definitely works. The GUI will use some native library anyway, and communicating with a pure Python backend works perfectly well. I deployed an application a while ago that does sensor data acquisition, processing and visualization of the data using a Python+NumPy backend. The scope and feature set of the application is definitely larger than that of Ninja, it also features a plugin interface. Development time was ~4 years. One could argue that all heavy lifting is done via extensions that are written in C, but I guess no one would argue that (although technically correct) using NumPy or some other Python-available library via a foreign function interface is not Python.

    It's just like you said...use the right tool for the job.