3 ms·
When Smalltalk methods are so short (averaging between 6-8 lines) it hardly makes sense to focus on its text editing aspects. This is part of the paradigm shif
by fractallyte 15y ago
When Smalltalk methods are so short (averaging between 6-8 lines) it hardly makes sense to focus on its text editing aspects.
This is part of the paradigm shift!
- kencausey 15y agoAbsolutely! This is why complex editing features don't thrive in the most Smalltalk environments; they simply aren't often used. Heck, 6-8 lines is a long Smalltalk method, time to consider refactoring. ;)
- gnosis 15y agoThat's nice. But I have a feeling there isn't just one method in your whole program. Having such short methods probably means that you'll wind up with many of them in most useful programs. That means that you'll be spending a fair bit of your time editing, which means that you'll want the ability to use your editor of choice, rather than being forced to use someone else's editor of choice.
- fractallyte 15y agoSmalltalk programs typically consist of many short methods woven together in a pure OO fashion. Thus the focus is more on program structure than actual editing. This has follow-on effects: refactoring, TDD and patterns are so much easier when the code resides in tiny snippets. It's a whole new world, where the code is 'live' rather than merely contained in static 'dead' text files...
- gecko 15y agoI also think it's important to point out that Pharo and Squeak do have a rich set of keybindings, so it's not as if you have to do mouse-based development if you don't want to. The editor may be a bit weak, but the general keyboard situation is pretty good.