Re: [rvskmbr...@gmail.com: Re: Type-in programs using BASH]

2015-01-27 Thread Greg Wooledge
On Mon, Jan 26, 2015 at 04:12:45PM -0800, Ryan Cunningham wrote:
> One day we'll be able to type in programs like these that are encoded in
> machine code. But that day is not now.

That day was the early 1980s.  There WERE machine-code programs (small
games) in glossy magazines that you could type in.  There were checksums
on each chunk of code (usually every 16 bytes or so), and at least one
of these glossy magazines had a special program that you typed in
first (in BASIC), which you then used to type in the object code, with
the checksum feature on each chunk.

And yes, it was all done in 6502 machine code because the dominant
machines of that age were the Commodore 64, the Atari 400/800, and the
Apple II series.  The IBM PC had not yet reached its zenith.

This is ANCIENT technology.  It is not some new idea that you've
stumbled across which will change the face of computing.

And it has NOTHING AT ALL to do with bash or gcc.



Re: [rvskmbr...@gmail.com: Re: Type-in programs using BASH]

2015-01-27 Thread Ryan Cunningham
And by "type-in programs" in the message to which I am replying, I mean those 
published in source code form.

-- 
Sent from my iPod

> On Jan 26, 2015, at 10:19 PM, Ryan Cunningham  wrote:
> 
> These type-in programs can actually generate quicker rises in popularity of 
> the FSF and in total market share of GNU/Linux distributions as more and more 
> people are introduced by such programs (or the experience of typing them) to 
> the concept of free and open-source software. I mean, GNU/Linux's market 
> share could potentially beat Microsoft Windows' (which is actually what the 
> FSF hopes will happen, with "Upgrade from Windows 8").
> 
> -- 
> Sent from my iPod
> 
>> On Jan 26, 2015, at 4:12 PM, Ryan Cunningham  wrote:
>> 
>> I would also like the discussion on the GCC mailing list to end. The 
>> discussion on /source/ code, however, should remain alive and well.
>> 
>> Sorry for all the confusion.
>> 
>> And by "type-in programs", I don't mean example programs like "Hello world" 
>> programs. I mean real programs with real purpose.
>> 
>> Programs written by freelance authors that program for a living, to 
>> (hopefully) find a user base among even the newest of GNU/Linux users.
>> 
>> One day we'll be able to type in programs like these that are encoded in 
>> machine code. But that day is not now. For portability reasons, I'd prefer 
>> source code for print publication.
>> 
>> But, in case we ever reach that day, I won't modify my proposed GPL addendum 
>> on this topic.
>> 
>> This discussion is on a Bash mailing list, but for the same reason as above, 
>> it could be possible that a type-in program is published in a source code 
>> language, like C, that /compiles/ into machine language. In that case, it 
>> would have to be typed into a text editor instead of a here-document (unless 
>> your compiler supports reading input from here-documents).
>> 
>> As I pointed out to Mr. Stallman, I'd like to encourage everyone who reads 
>> these messages to spread the word about the idea.
>> 
>> -- 
>> Sent from my iPod
>> 
>>> On Jan 26, 2015, at 3:50 PM, Ryan Cunningham  wrote:
>>> 
>>> No, no, not on the Internet---I mean in a paper magazine, which Internet 
>>> users can also get.
>>> 
>>> I'd like the machine code discussion to end.
>>> 
>>> -- 
>>> Sent from my iPod
>>> 
>>> On Jan 26, 2015, at 3:03 PM, Eduardo A. Bustamante López 
>>>  wrote:
>>> 
> I am proposing this as a possible alternative or complement to publication
> on the Internet to take into account those without Internet access, though
> those *with* Internet access also get the benefit.
 So you want to publish stuff on the Internet for people that don't have 
 access
 to the Internet? Right.
 
 This all sounds like a waste of time. Don't type machine code. Also, in the
 remote case that people will type machine code into their terminal, what 
 does
 heredocs have to do with that? Bash doesn't understand machine code.



Re: [rvskmbr...@gmail.com: Re: Type-in programs using BASH]

2015-01-27 Thread Eduardo A . Bustamante López
On Tue, Jan 27, 2015 at 06:11:37AM -0800, Ryan Cunningham wrote:
> And by "type-in programs" in the message to which I am replying, I mean those 
> published in source code form.
Please, stop it. We're not interested in hearing about your get back to the
'80s stuff, and this discussion does NOT belong in a technical mailing list
like bug-bash.

Consider using other means to promote your ideas. So far, the only thing you've
managed is to spam this list with nonsense.



Re: [rvskmbr...@gmail.com: Re: Type-in programs using BASH]

2015-01-27 Thread Ryan Cunningham
All right, maybe I can discuss it with the right people when I have the time. 
But for now, let's stop the discussion here.

-- 
Sent from my iPod

> On Jan 27, 2015, at 7:46 AM, Eduardo A. Bustamante López  
> wrote:
> 
>> On Tue, Jan 27, 2015 at 06:11:37AM -0800, Ryan Cunningham wrote:
>> And by "type-in programs" in the message to which I am replying, I mean 
>> those published in source code form.
> Please, stop it. We're not interested in hearing about your get back to the
> '80s stuff, and this discussion does NOT belong in a technical mailing list
> like bug-bash.
> 
> Consider using other means to promote your ideas. So far, the only thing 
> you've
> managed is to spam this list with nonsense.