On 24/01/19 9:47 PM, Sven Van Caekenberghe wrote:
On 24 Jan 2019, at 17:04, K K Subbu <kksubbu...@gmail.com> wrote:
On 24/01/19 7:23 PM, Sven Van Caekenberghe wrote:
Everybody is of course totally free to do whatever they want,
but really, why the hell would you want to do that ?
Because text has many uses other than just feeding into a compiler
for translation to machine code? People who come from Unix/Linux
world are used to using a rich collection of tools that deal with
text in various ways.
I am myself a server/linux guy, an emacs user, I know what is all
possible and what the unix philosophy is.
No offense intended. Just wanted to point out that text can have
different purposes. Historically, Smalltalk presented itself as a
OS+IDE. Today, that is no longer true. Pharo is just a multi-platform IDE.
I also know how to integrate Pharo into that world, and this is super
important.
Thanks. This is what I intended to bring out.
You lose so much by doing that, I do not even know where to
start.
Live coding (i.e. coding in the presence of instances) is
undoubtedly more powerful than edit-compile-run cycle. Text is used
to direct IDE to edit live objects. But text has many more uses
than just issuing commands. If beginners start using vim just to
edit code due to established habits, they will soon realize the
ease of live coding and remain in IDE. This is a self-correcting
error.
Well, I don't think so.
The users that you are going to attract in this way (the ones that
don't want to leave their own IDE/editor), will look at textual Pharo
and find it very strange and ill suited to textual editing (and they
are absolutely right), they will not discover the power, will not
learn (from this experience alone) what object
design/programming/power is, and will ask for more (e.g. give me ,
style compiler errors, better/easier structure of the file, fixed the
!! escape issue, etc, ...).
I am sure there will always be skeptics. But my own experience was
different. For me, the most weird thing about Squeak (and now Pharo) IDE
is its insistence in showing only one method at a time. A method is too
small a chunk of code. It is easy to miss the forest for the trees. In
Dimitris video, you see lots more code in one glance in vim session. So
there are pragmatic reasons why some coders fallback to using fileOuts
for browsing classes.
Regards .. Subbu
