Re:Design of a Vim-like text editor
by agumonkey on Friday January 02, 2015 @12:31PM
(#8827591)
At one point, REPL first editors (ipython notebooks, etc) will meet edition based IDE (them) in an essential cosmic spark and nothing will ever be the same ever again.
[ Parent
| on HN ]
Isn't that LightTable? I think they discovered actually everything would remain largely the same.
Good point, how could I forgot LT...
IntelliJ sort of has this for Scala. Scala Worksheets. They are more useful than a REPL, but not quite to iPython in terms of features (mainly because they aren't browser based). But they also have some advantages over iPython (like integrating many of the IDE features).
PyCharm now offers the ability to open iPython notebooks inside itself - which gives you the nice IDE goodies, plus the notebook goodies.
The downside of course is that Python is very dynamic - so IDEs are of relatively limited use.
The downside of course is that Python is very dynamic - so IDEs are of relatively limited use.
I am surprised to hear you say that with "PyCharm" being the first word in your comment. We have had very good experiences with PyCharm + reStructuredText annotations to help it when the return type or arg type is not inferable. Just like its IJ friend, PyCharm has caught quite a few bugs and helps the team edit Python and not text.
PyCharm's usage is not optional on my team; we tried the "use whatever text editor you want" approach and it turns out that people are not as good at memorizing the type signatures of a complicated codebase as computers are.