[Info-vax] Intel proposal to simplify x86-64

Arne Vajhøj arne at vajhoej.dk
Wed Jun 7 19:20:44 EDT 2023


On 6/7/2023 5:50 AM, Jan-Erik Söderholm wrote:
> Den 2023-06-07 kl. 11:36, skrev Johnny Billquist:
>> On 2023-06-07 11:09, Jan-Erik Söderholm wrote:
>>> I must ask (since I have never used TECO).
>>>
>>> What is the unique feature of TECO that cannot be done
>>> with some other tool(s)?
>>
>> I don't think there is anything that is that unique.
>> However, depending on how you use it, you might need a bunch of other 
>> tools to accomplish the same.
>>
>> It obviously is an editor. But it's also a programming language that 
>> can be twisted into doing a lot of stuff. If you are familiar with sed 
>> (a Unix tool), it is somewhat similar. But I'd say TECO can do more. 
>> Obviously the original Emacs was written in TECO. There are other 
>> editors written in TECO as well. I sometimes use it when I want to do 
>> somewhat more complex operations over larger text files where the 
>> changes are a bit more complex than just search and replace.
>>
>> But writing code in TECO is arcane. It has been described (and not 
>> without merit) as a write-only language. Reading it, it looks mostly 
>> like line noise. So it's unlikely that most people know it, or want to 
>> learn it. So these days, it's mostly old and weird people who might 
>> ever use TECO. There might, of course, be various tools and programs 
>> existing that are written in TECO, that people use, without knowing 
>> how to write TECO themselves...
> 
> So I guess it boils down to what priority VSI should put on TECO.
> How many paying custumers are asking for TECO throught official channels.

How many existing customers or potential new customers will
determine to buy or not to buy VMS based on the availability
of TECO.

My guess: zero.

Arne




More information about the Info-vax mailing list