I think that the difference is in every language. You do not just debug a c program executing it or compiling it for release, the same with c++ and java or python. I never debugged haskell, but when you execute something in the console you are even implicitly using print-it. instead of do it.��Profiling is not different neither, is not that you there is all the time something profiling your applications.��

I think that real difference is that is not usual to find a language that let you execute what ever you want almost everywhere, because the meaning of what execution is, is slightly different. ��Then, in other languages it just do not makes sense.��

You may want to change the menu to be different when you have something selected, i feel it will be more bureau, but it can be cool to try a prototype.




2014-07-15 22:50 GMT+02:00 Esteban A. Maringolo <emaringolo@gmail.com>:
2014-07-15 17:30 GMT-03:00 Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com>:
> 2014-07-15 20:27 GMT+02:00 Esteban A. Maringolo <emaringolo@gmail.com>:
>
>> I find the "... it" suffix obsolete. "Delete it", "Do it", "Print it",
>> etc.
>>
>> Maybe it made sense in the past, but today it feels weird.
>> There is no "Cut it", "Paste it", etc... nor similar in other software.
>> IMO, if the menu is contextual, the context already applies the "it"
>> (subject).

> Did you notice "it" is only mentionned when you will evaluate (do it / print
> it / debug it / ... )?
> Otherwise, if it's just text editing there is no it.
> So there is a sort of logic. IMO that makes sense, because evaluating is a
> special action.

I did notice.

And I believe the "print-it", "do-it" and similar are there because of
historical reasons I don't know, but were carried over without
questioning it, maybe since ST-80 . :)

Why make a distinction between copying text and
evaluating/profiling/debugging it? I only saw this in Smalltalk.

Esteban A. Maringolo