On Saturday, May 6, 2023 at 12:09:32 AM UTC-7, Jurgen Pitaske wrote:

> Really looking forward to some more of your work.
> And I have a Lattice 7k board here.
> If I remember correctly and it has not changed, it is easy using just the Lattice Programmer -
> just to get started and see the LEDs flash and the Servos turn.
> One option would be to use dropbox to store the files,
> and a link here when news have happened.
> Github as well.
> The Forth facebook group would be an option to distribute the information..
> https://www.facebook.com/groups/PROGRAMMINGFORTH
> And the Minimalist group is very active
> https://www.facebook.com/groups/minimalistcomputing

We finally have a complete V file with all modules checked against the software simulation of a small set of 4th words.
Designing and getting Fpga4th to make the V file was more difficult than designing the 32bit 4th processor for our motion
control product. (16 cooridinated axis for our 7A 100V motor drivers, 2 cooridinated pwm outputs for lasers, printers etc,
a USB, SPI, rs485 and rs232 interface, 64Mb dram, 250Kb sram.)

It would be in our best interest for Fpga4th to become an open source project IF enough forth programers were interested
in continuing its development. Its based on an extension of Forth called 4thSets, which would also become
an open source project.

jrh

Reality is an information process, set in motion and sustained by God for a purpose.
Understanding the purpose is more important than knowing anything about anything.

On Saturday, 23 September 2023 at 01:52:41 UTC+1, John Hart wrote:
> On Saturday, May 6, 2023 at 12:09:32 AM UTC-7, Jurgen Pitaske wrote:
>
> > Really looking forward to some more of your work.
> > And I have a Lattice 7k board here.
> > If I remember correctly and it has not changed, it is easy using just the Lattice Programmer -
> > just to get started and see the LEDs flash and the Servos turn.
> > One option would be to use dropbox to store the files,
> > and a link here when news have happened.
> > Github as well.
> > The Forth facebook group would be an option to distribute the information.
> > https://www.facebook.com/groups/PROGRAMMINGFORTH
> > And the Minimalist group is very active
> > https://www.facebook.com/groups/minimalistcomputing
> We finally have a complete V file with all modules checked against the software simulation of a small set of 4th words.
> Designing and getting Fpga4th to make the V file was more difficult than designing the 32bit 4th processor for our motion
> control product. (16 cooridinated axis for our 7A 100V motor drivers, 2 cooridinated pwm outputs for lasers, printers etc,
> a USB, SPI, rs485 and rs232 interface, 64Mb dram, 250Kb sram.)
>
> It would be in our best interest for Fpga4th to become an open source project IF enough forth programers were interested
> in continuing its development. Its based on an extension of Forth called 4thSets, which would also become
> an open source project.
>
> jrh
>
> Reality is an information process, set in motion and sustained by God for a purpose.
> Understanding the purpose is more important than knowing anything about anything.

Thank you very much John for your work.

Tonight is the Forth online meeting.
Would it not be a good platform to present what you have achieved?
I assume there would be people there who would pick it up.

And I assume a platform might be as well the Robot group and CORE1
https://www.facebook.com/groups/1304548976637542

An application that people love might be another way to promote it.
Testra has been known for motor driving.
Would it not be intersting to have some examples here?
Option 1: control two simple Servos which drive around. There are many hardware kits around.
Option 2: Control 4 servos on OTTO - ok more fun but there should be a lot of ottos around.
Option 3: The MeArm needs to drive 4 servos.

And the same could be done using other motors.

And there are many mtorized @dogs@ around that need controllinhg ...

Is there any documentation available - even with a smaller prtion - tfor people to have a look and switch an LED on? ...

Forth Meeting:
September: SVFIG Zoom Meeting TODAY
go to: forth.org/zoom
**The Zoom Room is open 24-7, stop by and give it a try!
=+
There will be NO IN-PERSON meeting at Stanford! Zoom only!
=+
*** PLEASE NOTE 09:30 AM (Pacific Daylight Savings) START TIME
***All durations and descriptions are approximate or perhaps entirely inconsistent with what will eventually transpire.
=*

# AGENDA
=+
Ceremonial Starting of the Recorder
There will be a brief non-denominational observance of the beginning of the monthly recording of the Zoom session. Recordings will be posted to the SVFIG YouTube channel!

=+
A Slightly Different Forth Compiler Design --- Joseph O'Connor
The Creole Forth compiler has several unusual features which include the lack of a STATE variable. This presentation will discuss its design features and their advantages.
=+
Forth Day is Coming --- Kevin Appert
What will you talk about?!
Will it be all-zoom or shall we meet up?
=+
Demo Scene --- Bill Ragsdale
See eight demonstrations written in Forth ranging from high speed graphics, 16 way multitasking, video player to chess with an opening book
=+
A Day at the Vintage Computer Festival West - Dave Jaffe
"I will present a photo review of the exhibits at this year's West Coast Vintage Computer Festival." (postponed from last month)
=+
Single Mecrisp Core --- Christopher Lozinski
Hello. I did speak about "Review of Soft core Forth Processors" both at last months SVFIG meeting and at the Stockholm FPGA conference. I now have a single Mecrisp core running on the pico-ice, and would like to announce it.
=+
CORE I Update ---Don Golding
> boards are fabbed and delivered to the assembly house for stuffing. PCBWay forgot to make a stencil for the bottom side. I hope the assembly house can get one made locally (at greater cost) so I don't have to wait a week for PCBWay. Always something...
=+
Walk-ins, Rambles, Rumors, Reminiscences --- Everybody
=+
ADJOURNMENT
The recording will be stopped without ceremony. Good fellowship and conversation can continue in our tastefully furnished Zoom Room.
=+
COMING NEXT MONTH: (postponed from this month)
What I'm Currently Working On --- Samuel Falvo II
'A quick jaunt through Shoehorn and the project I'm using it on. A recap/status of ForthBox:20AE project.”
=+
Message Kevin Appert for more info! Send messages through Meetup-message, email, etc.
=*
Zoom meetings are recorded and presented on our YouTube channel:
https://www.youtube.com/c/SiliconValleyForthInterestGroup

On Saturday, 23 September 2023 at 01:52:41 UTC+1, John Hart wrote:
> On Saturday, May 6, 2023 at 12:09:32 AM UTC-7, Jurgen Pitaske wrote:
>
> > Really looking forward to some more of your work.
> > And I have a Lattice 7k board here.
> > If I remember correctly and it has not changed, it is easy using just the Lattice Programmer -
> > just to get started and see the LEDs flash and the Servos turn.
> > One option would be to use dropbox to store the files,
> > and a link here when news have happened.
> > Github as well.
> > The Forth facebook group would be an option to distribute the information.
> > https://www.facebook.com/groups/PROGRAMMINGFORTH
> > And the Minimalist group is very active
> > https://www.facebook.com/groups/minimalistcomputing
> We finally have a complete V file with all modules checked against the software simulation of a small set of 4th words.
> Designing and getting Fpga4th to make the V file was more difficult than designing the 32bit 4th processor for our motion
> control product. (16 cooridinated axis for our 7A 100V motor drivers, 2 cooridinated pwm outputs for lasers, printers etc,
> a USB, SPI, rs485 and rs232 interface, 64Mb dram, 250Kb sram.)
>
> It would be in our best interest for Fpga4th to become an open source project IF enough forth programers were interested
> in continuing its development. Its based on an extension of Forth called 4thSets, which would also become
> an open source project.
>
> jrh
>
> Reality is an information process, set in motion and sustained by God for a purpose.
> Understanding the purpose is more important than knowing anything about anything.

Is there any documentation available
- even just a smaller portion
- for people to have a look and switch an LED on? ...
Some of the people in the FIG Meeting might be very interested.
And it would be very interesting to know which FPGA Board could be used.
I hope it is a Lattice Board, as I have a few of those.
If that runs on some of the ones I have,
I would be glad to try it out and generate some documentation.

On Sunday, September 24, 2023 at 9:09:22 AM UTC-7, Jurgen Pitaske wrote:
<clip>
> Is there any documentation available
> - even just a smaller portion
> - for people to have a look and switch an LED on? ...
> Some of the people in the FIG Meeting might be very interested.
> And it would be very interesting to know which FPGA Board could be used.

The target fpga is a LCMX02-7000. It only has a few K of internal memory so
an external memory is necessary to run a significant forth program.
I'll email you a block diagram of the processor. I won't have time for anything
else until I get the v file to compile and Forth is up and running.

jrh

On Friday, September 22, 2023 at 5:52:41 PM UTC-7, John Hart wrote:
> On Saturday, May 6, 2023 at 12:09:32 AM UTC-7, Jurgen Pitaske wrote:
>
> > Really looking forward to some more of your work.
> We finally have a complete V file...

John Hart accepts Juergen Pintaske as his peer! LOL
That really says quite a lot about John Hart!

> It would be in our best interest for Fpga4th to become an open source project
> IF enough forth programers were interested in continuing its development.
> Its based on an extension of Forth called 4thSets, which would also become
> an open source project.

Why is it in the best interests of Testra to make FPGA4TH and 4THSETS
open-source? Is it because Testra's software is full of bugs and you hope
that somebody will debug it for you?

You aren't any good at programming!
This is why you needed me to write MFX (assembler, simulator and
Forth cross-compiler for the MiniForth) --- you weren't capable of writing this
yourself, and your employeed Steve Brault wasn't capable either --- but you were
also ashamed of the fact that you needed to hire outside help, so you refused
to admit afterward that I had written MFX. The liar Tom Hart says:
--------------------------------------------------------------
[Hugh] had nothing to do with the processor itself,
that was all designed by John Hart and Steve Brault.
The PLD version was based upon our original Forth Engine done long before we ever ran across Hugh.
--------------------------------------------------------------

> Reality is an information process, set in motion and sustained by God for a purpose.
> Understanding the purpose is more important than knowing anything about anything.

John Hart is still pretending that he understands God's purpose! LOL
John Hart doesn't know anything about anything --- he is an arrogant clown.

On Monday, 25 September 2023 at 00:44:58 UTC+1, Hugh Aguilar wrote:
> On Friday, September 22, 2023 at 5:52:41 PM UTC-7, John Hart wrote:
> > On Saturday, May 6, 2023 at 12:09:32 AM UTC-7, Jurgen Pitaske wrote:
> >
> > > Really looking forward to some more of your work.
> > We finally have a complete V file...
>
> John Hart accepts Juergen Pintaske as his peer! LOL
> That really says quite a lot about John Hart!
> > It would be in our best interest for Fpga4th to become an open source project
> > IF enough forth programers were interested in continuing its development.
> > Its based on an extension of Forth called 4thSets, which would also become
> > an open source project.
> Why is it in the best interests of Testra to make FPGA4TH and 4THSETS
> open-source? Is it because Testra's software is full of bugs and you hope
> that somebody will debug it for you?
>
> You aren't any good at programming!
> This is why you needed me to write MFX (assembler, simulator and
> Forth cross-compiler for the MiniForth) --- you weren't capable of writing this
> yourself, and your employeed Steve Brault wasn't capable either --- but you were
> also ashamed of the fact that you needed to hire outside help, so you refused
> to admit afterward that I had written MFX. The liar Tom Hart says:
> --------------------------------------------------------------
> [Hugh] had nothing to do with the processor itself,
> that was all designed by John Hart and Steve Brault.
> The PLD version was based upon our original Forth Engine done long before we ever ran across Hugh.
> --------------------------------------------------------------
> > Reality is an information process, set in motion and sustained by God for a purpose.
> > Understanding the purpose is more important than knowing anything about anything.
> John Hart is still pretending that he understands God's purpose! LOL
> John Hart doesn't know anything about anything --- he is an arrogant clown.

You find it all here,
all of the people that wanted to comment.

Please dump your shit elswhere.

On Monday, 25 September 2023 at 07:45:12 UTC+1, Jurgen Pitaske wrote:
> On Monday, 25 September 2023 at 00:44:58 UTC+1, Hugh Aguilar wrote:
> > On Friday, September 22, 2023 at 5:52:41 PM UTC-7, John Hart wrote:
> > > On Saturday, May 6, 2023 at 12:09:32 AM UTC-7, Jurgen Pitaske wrote:
> > >
> > > > Really looking forward to some more of your work.
> > > We finally have a complete V file...
> >
> > John Hart accepts Juergen Pintaske as his peer! LOL
> > That really says quite a lot about John Hart!
> > > It would be in our best interest for Fpga4th to become an open source project
> > > IF enough forth programers were interested in continuing its development.
> > > Its based on an extension of Forth called 4thSets, which would also become
> > > an open source project.
> > Why is it in the best interests of Testra to make FPGA4TH and 4THSETS
> > open-source? Is it because Testra's software is full of bugs and you hope
> > that somebody will debug it for you?
> >
> > You aren't any good at programming!
> > This is why you needed me to write MFX (assembler, simulator and
> > Forth cross-compiler for the MiniForth) --- you weren't capable of writing this
> > yourself, and your employeed Steve Brault wasn't capable either --- but you were
> > also ashamed of the fact that you needed to hire outside help, so you refused
> > to admit afterward that I had written MFX. The liar Tom Hart says:
> > --------------------------------------------------------------
> > [Hugh] had nothing to do with the processor itself,
> > that was all designed by John Hart and Steve Brault.
> > The PLD version was based upon our original Forth Engine done long before we ever ran across Hugh.
> > --------------------------------------------------------------
> > > Reality is an information process, set in motion and sustained by God for a purpose.
> > > Understanding the purpose is more important than knowing anything about anything.
> > John Hart is still pretending that he understands God's purpose! LOL
> > John Hart doesn't know anything about anything --- he is an arrogant clown.
> You find it all here,
> all of the people that wanted to comment.
>
> Please dump your shit elswhere.

https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0

John, after the hardship of going thought all the messages in this thread, I'm really interested in seen you work.

I was truing to look at the OP and make some sense of it, here is what I came up with for the following as an example:
1 1C >XBCS AD D - - H" DR_RRB_AC" ' EMU_DR_RRB_AC ' NOP SIMPLE-OP: DR_RRB_AC

1 1C: Parameter values of 1 1C can be understood as a single hex value 0x1C representing some kind of opcode or identifier for the operation.

>XBCS: This is likely a transformation or a command to convert the previous value.

AD D - -: These could be flags or additional parameters for the operation. They might indicate how the operation behaves, modifies data, or interacts with other parts of the system.

H" DR_RRB_AC": Looks like it's a label or identifier for the operation. It's named DR_RRB_AC and would be referenced elsewhere.

' EMU_DR_RRB_AC ': This is fetching the execution token (xt) of the word EMU_DR_RRB_AC. Possible a word for a subroutine or handler that gets called when the operation is executed.

NOP: No Opp.

SIMPLE-OP: DR_RRB_AC: This is the actual declaration of the operation. It's named DR_RRB_AC, and all the preceding parameters and values describe its behavior and properties.

Code Type: The type or category of the instruction.
src: Source operand (e.g., a register or memory location).
dst: Destination operand.
Dsrc and Ddst: Possibly deferred or delayed source and destination operands.
instr string: A human-readable string representation of the instruction.
emulation operation: This likely refers to how the instruction should be emulated. It could be used in a software emulator to mimic the behavior of the real hardware.
Register: They look allot like RISC Arm, so I based my self on that.

Here is my attempt to put this into some sort of verilog format:

// Define the registers and flags
reg [15:0] Treg; // 16-bit T register
reg [15:0] accumulator; // 16-bit accumulator
reg [15:0] data_reg; // 16-bit data register
....
reg carry_flag; // Carry flag
reg flag; // General flag
....

// Define the operations
always @(posedge clk) begin
case (operation_type)
`>XBCS`: begin
// Implement the >XBCS operation
// Example: data_reg = Treg + accumulator + carry_flag;
...
end

`>CS`: begin
// Implementw the >CS operation
...
end

`>MA`: begin
// Memory Addressing: Load the accumulator with the value at the memory address
accumulator = memory[address];
end

`AC>MA`: begin
// Memory Addressing: Store the accumulator value to the memory address
memory[address] = accumulator;
end

...

`TR>DR`: begin
// Move data from T register to data register ( assuming that is the meaning )
data_reg = Treg;
end

`AC>DR`: begin
// Move data from accumulator to data register
data_reg = accumulator;
end

`0>DR`: begin
// Set data register to 0
data_reg = 16'b0;
end

`AC_OR_TR>DR`: begin
// Logical OR between accumulator and T register, result to data register ( just making this up )
data_reg = accumulator | Treg;
end

`IF_CRY+JMP`: begin
// Conditional jump based on carry flag ( If that is correct )
if (carry_flag) begin
program_counter = jump_address;
end
end

...

// All the Ops form the code.

endcase
end

// Emulation functions
function EMU_TR>DR;
begin
// Emulate the TR>DR operation what ever that is.
...
end

function EMU_AC>DR;
begin
// Emulate the AC>DR operation what ever that is.
...
end

....

On Thursday, April 27, 2023 at 7:44:11 PM UTC-7, Hugh Aguilar wrote:
> On Wednesday, April 26, 2023 at 5:59:22 PM UTC-7, John Hart wrote:
> > On Tuesday, April 25, 2023 at 6:23:15 PM UTC-7, Lorem Ipsum wrote:
> > > I can't think of anything that is harder to do in an FPGA than in a CPLD,
<clip>
> > > There is nothing about FPGAs to preclude or make harder parallel operations.
<clip>
> > > Rick C.
> >
> > The basic logic unit of a FPGA is a LUT, typically 4 or 5 inputs.
> > The basic logic unit of a CPGA has 16 to 20 inputs.
> > A 5 input LUT can decode all possible inputs, the basic logic unit of a FPGA,
> > only 4 to 20.
> The Lattice isp1048 PLD had a lot more connectivity than a modern FPGA.
Not true!
> This is why a VLIW design on the PLD was possible, but is impossible on an FPGA.
I don't know what a VLIW is, but I know anything possible on a PLD can be done better on a modern FPGA.
<ad hominem & nonsense clipped>

> A VLIW processor is obsolete now (this might still be possible in an ASIC, though).

Our original MSI LSI based processor (4S32) used in thousands ofTicketMaster terminals,
was a Harvard architecture with a 32 bit instruction (not sure if that qualifies as VLIW),
a 16 bit data path and 4 bit ALU. [An emulation of an Intel 286 (virtual PC) on it would
run a little faster than it. An emulation of a customers 16 bit processor ran 5 times faster.]

The Forth multi-user system we manufactured using the same CPU supported 7 users.
When we moved the design to the PLD ,the instruction width was shrunk to 16 bits, which
I'm sure doesn't qualify as a Very Large Instruction Width. The arithmetic part of the ALU
remained 4 bits but the logic part became 16.

The instruction word for the RACE32 is 18 bits, so it's not a VLIW either,
but the ALU and internal data path have been expanded to 32 bits, enabled by
the fast ripple carry feature of FPGAs.

The power of modern FPGA would blow people's minds, if they understood them..
Advanced supercomputer have tens of thousands of chips with thousands of processes
running in each one with more computing power than a PC. The fear about AAI taking
over the world is based on the reality of what can be done with this power
and how dangerous it would be if abused.

Restrictions won't reduce the danger, they'll make it more dangerous, more concentrated.
The solution to Big Tech having too much power is to empower people. Enable small business
to use robotics and automation to compete. Something like an open source platform programed
in Forth for automation would be the ideal tool to enable it. Focusing on solutions is the
only way out of the mess we're in, Attacks and flame wars are a DEAD END, they accomplish
NOTHING, and the din drowns out rational discourse.

HUGH WROTE MFX, never said he didn't. He was quite creative at the time.

<clip more ad hominem crap>

On Friday, April 28, 2023 at 11:56:23 AM UTC-7, John Hart wrote:
> On Thursday, April 27, 2023 at 7:44:11 PM UTC-7, Hugh Aguilar wrote:
> > On Wednesday, April 26, 2023 at 5:59:22 PM UTC-7, John Hart wrote:
> > > On Tuesday, April 25, 2023 at 6:23:15 PM UTC-7, Lorem Ipsum wrote:
> > > > I can't think of anything that is harder to do in an FPGA than in a CPLD,
> <clip>
> > > > There is nothing about FPGAs to preclude or make harder parallel operations.
> <clip>
> > > > Rick C.
> > >
> > > The basic logic unit of a FPGA is a LUT, typically 4 or 5 inputs.
> > > The basic logic unit of a CPGA has 16 to 20 inputs.
> > > A 5 input LUT can decode all possible inputs, the basic logic unit of a FPGA,
> > > only 4 to 20.
> > The Lattice isp1048 PLD had a lot more connectivity than a modern FPGA.
> Not true!
> > This is why a VLIW design on the PLD was possible, but is impossible on an FPGA.
> I don't know what a VLIW is, but I know anything possible on a PLD can be done better on a modern FPGA.

If you don't know what a VLIW is, then you presumably don't know what out-of-ordering
is either --- out-of-ordering is the distinctive feature of a VLIW.

You didn't know what out-of-ordering was in 1994 either.
You told me to write the assembler with each line representing one opcode, and all
five instructions that would be embedded in that opcode (and would execute
concurrently in a single clock cycle) on that line.
That was stupid!!! I remember at the time being stunned by the stupidity of your advice.
What I did was write the assembler so that the user would write his source-code as if
the instructions were executed sequentially, and my assembler would out-of-order
the instructions to pack them into the opcodes to minimize the number of NOP
instructions that had to be inserted while yet guaranteeing that the program did
the same thing as if the instructions were executed sequentially as they had been
written in the source-code. I got this idea from the Pentium with its U and V pipes.
MFX did the out-of-ordering at compile-time rather than run-time, so that was easier,
but the MiniForth had five instructions executing concurrently whereas the Pentium
only had two instructions executing concurrently (U and V), so that was more difficult.

You aren't any good at computer programming. You didn't understand out-of-ordering
in 1994, and you apparently still don't. All of your advice was stupid. I wrote all of the
code without any help at all, but now you take credit for writing it.

> The power of modern FPGA would blow people's minds, if they understood them.
> Advanced supercomputer have tens of thousands of chips with thousands of processes
> running in each one with more computing power than a PC. The fear about AAI taking
> over the world is based on the reality of what can be done with this power
> and how dangerous it would be if abused.

Only idiots watch the Terminator movies and take that nonsense seriously.
Apparently you are also a fan of the "Groundhog Day" movie.
This is a pathetic life. I recommend that you throw away your DVD player.

> HUGH WROTE MFX, never said he didn't. He was quite creative at the time.

You are lying, of course.
This is the first time that you have ever admitted in public that I wrote MFX.

I remember going to a job interview and the personnel lady called Testra on the
phone, and put it on speaker-phone so I could hear. The person who answered
at Testra identified himself as John Hart. He said that I had done "nothing"
in my time working there, and that I was not eligible for rehire.
Since then, you have claimed that this was actually Tom Hart impersonating you.
Maybe so! It doesn't matter though because you are 100% loyal to Tom Hart, so
when he puts words in your mouth those are your words, because you don't complain.
Note that this was at a time when you were trying to talk me into coming back to
work at Testra, so I was eligible for rehire. I think that your plan was to prevent me
from finding work elsewhere so that low finances would force me to return to Testra.
You didn't expect me to find out about this. I wouldn't have found out except that the
personnel lady put you on speaker phone, but that was unusual. As an example, I applied
at Lockheed Martin because they had a VLIW processor that they were using for
processing radar images. I went through two interviews and everything looked good.
I was told that they needed to verify at Testra, and then they would get back to me.
They got back to me and told me that I was disqualified for any job at Lockheed Martin.
Apparently you knew that Lockheed Martin would pay me more than $10/hour, and that
I wouldn't return to Testra, so you undermined my effort to get ahead in life.

After the incident with the speaker-phone, I never applied for work as a programmer again.
Writing MFX was my claim to fame. I needed that to get a job as a programmer.

Testra began attacking me on comp.lang.forth in 2019.
Tom Hart refused to admit that I wrote MFX (assembler/simulator and Forth cross-compiler).
Now in 2023 you finally admit that I wrote MFX, but you claim that you never
said that I didn't. Bullshit! You have been saying that you and Steve Brault wrote MFX
for the last three decades.

On Friday, September 13, 2019 at 9:08:59 AM UTC-7, Jurgen Pitaske wrote:
> The official answer from Tom Hart, their president,
> who agreed to have his answer to me published on clf:
>
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [Hugh] wrote our Forth compiler for the processor
> that we implemented in a Lattice PLD.
>
> He did a good job on it,
> we are still using it with a few bug fixes and minor modifications.
>
> He had nothing to do with the processor itself,
> that was all designed by John Hart and Steve Brault.
>
> The PLD version was based upon our original Forth Engine done long before
> we ever ran across Hugh.

Tom Hart is saying that MFX was written long before Testra ever ran across me.
Obviously, the assembler/simulator is an integral part of the MiniForth, so Tom Hart
is saying that I was never anything more than a stupid little maintenance programmer
who used MFX that was written by real programmers before I hired on.
He is effectively accusing me of lying when I say that I wrote MFX.

Tom Hart is giving me credit for writing the interactive Forth compiler. Bullshit!
That was written in MFX after I left. That required all of the assembly-language
to already be done because you can't have an assembler on the MiniForth due
to not being able to write to code-memory. Writing the interactive Forth compiler
would have been trivial because I had already written all of the primitives in
assembly-language. I also wrote the assembler.
When people read Tom Hart's lies they believe that there is no evidence to
indicate that I programmed in assembly-language, much less wrote the assembler.
They believe that I ported figForth over to the MiniForth. This is a lie, and you have
never contradicted your brother --- you have never stood up and told the truth.

Why did Testra attack me on comp.lang.forth with lies and insults?
Tom Hart made this attack on the command of Juergen Pintaske, the MPE salesman.
Apparently you were in negotiation with Stephen Pelc for him to buy the RACE processor,
and you believed that you had to obey Juergen Pintaske's commands to stay on
Stephen Pelc's good side. It is unlikely that Stephen Pelc was going to buy your RACE
processor. He was most likely just tugging your chain for the entertainment value of
getting you to attack your own employee on comp.lang.forth. You think that you can
totally crush me here on comp.lang.forth, but you harm yourself as much or more
than you harm me. Testra won't be considered to be a reputable company any more.
You have more to lose than I do. People who live in glass houses shouldn't throw stones!
Attacking me on comp.lang.forth was a bad idea. Was alcohol involved in this decision?

On Friday, April 28, 2023 at 2:56:23 PM UTC-4, John Hart wrote:
> On Thursday, April 27, 2023 at 7:44:11 PM UTC-7, Hugh Aguilar wrote:
> > On Wednesday, April 26, 2023 at 5:59:22 PM UTC-7, John Hart wrote:
> > > On Tuesday, April 25, 2023 at 6:23:15 PM UTC-7, Lorem Ipsum wrote:
> > > > I can't think of anything that is harder to do in an FPGA than in a CPLD,
> <clip>
> > > > There is nothing about FPGAs to preclude or make harder parallel operations.
> <clip>
> > > > Rick C.
> > >
> > > The basic logic unit of a FPGA is a LUT, typically 4 or 5 inputs.
> > > The basic logic unit of a CPGA has 16 to 20 inputs.
> > > A 5 input LUT can decode all possible inputs, the basic logic unit of a FPGA,
> > > only 4 to 20.
> > The Lattice isp1048 PLD had a lot more connectivity than a modern FPGA.
> Not true!
> > This is why a VLIW design on the PLD was possible, but is impossible on an FPGA.
> I don't know what a VLIW is, but I know anything possible on a PLD can be done better on a modern FPGA.

Hugh won't agree on this, but a VLIW (Very Long Instruction Word) processor has very little encoding of fields, with many control points in the processor having individual bits in the instruction word. This provides tons of flexibility in each instruction, rather than being limited to a fixed instruction set. In particular, this allows the maximum parallelism to be exploited.

TI used "VLIW" in their TMS320C6xxx DSP line, but it's not quite the same thing. They had multiple CPUs in the chip, which all had a core functionality, with enhanced features in a few. They simply aggregated the 32 bit instructions into a 256 bit main instruction word. The earlier versions of the processor were bandwidth limited because of the need for external program storage. Eventually, as semiconductor processing provide more and more, on-chip memory, they could keep all the processors running. They were essentially used with a few doing math operations, while others were DMA engines keeping the data moving. Still, not exactly, VLIW, in the traditional sense.

I worked on attached array processors, which were VLIW in the real sense, with over 100 bits in the ALU control store. There was a separate "storage-move" processor that managed moving the data between main memory, cache and the compute head register file. Lots of ECL gate arrays, and lots of power.

> <ad hominem & nonsense clipped>
> > A VLIW processor is obsolete now (this might still be possible in an ASIC, though).
> Our original MSI LSI based processor (4S32) used in thousands ofTicketMaster terminals,
> was a Harvard architecture with a 32 bit instruction (not sure if that qualifies as VLIW),

That's a standard processor design, I expect, with encoded fields.

> a 16 bit data path and 4 bit ALU. [An emulation of an Intel 286 (virtual PC) on it would
> run a little faster than it. An emulation of a customers 16 bit processor ran 5 times faster.]

Maybe I spoke too soon. To say if it was along the concept of VLIW would require considering what the fields in the instruction were doing. If they mostly directly controlled various functions in the CPU, rather than being encoded, that would be VLIW.

> The Forth multi-user system we manufactured using the same CPU supported 7 users.
> When we moved the design to the PLD ,the instruction width was shrunk to 16 bits, which
> I'm sure doesn't qualify as a Very Large Instruction Width. The arithmetic part of the ALU
> remained 4 bits but the logic part became 16.

It's not the number of bits in the instruction word, really. It's how they are used. If it has to be decoded, that's not VLIW. If individual bits directly control things like a mux select line or the selection of carry, etc, that's VLIW.

> The instruction word for the RACE32 is 18 bits, so it's not a VLIW either,
> but the ALU and internal data path have been expanded to 32 bits, enabled by
> the fast ripple carry feature of FPGAs.
>
> The power of modern FPGA would blow people's minds, if they understood them.
> Advanced supercomputer have tens of thousands of chips with thousands of processes
> running in each one with more computing power than a PC. The fear about AAI taking
> over the world is based on the reality of what can be done with this power
> and how dangerous it would be if abused.
>
> Restrictions won't reduce the danger, they'll make it more dangerous, more concentrated.
> The solution to Big Tech having too much power is to empower people. Enable small business
> to use robotics and automation to compete. Something like an open source platform programed
> in Forth for automation would be the ideal tool to enable it. Focusing on solutions is the
> only way out of the mess we're in, Attacks and flame wars are a DEAD END, they accomplish
> NOTHING, and the din drowns out rational discourse.

What mess??? I must have missed something.

> HUGH WROTE MFX, never said he didn't. He was quite creative at the time.
>
> <clip more ad hominem crap>

Yeah, he's definitely off the deep end these days. He used to be a regular ranter here... I mean, a regular contributor here. But he disappeared for some time. He's not back in full force. He used to go out of his way to argue with people. He seems much more restrained now.

--

Rick C.

-+-- Get 1,000 miles of free Supercharging
-+-- Tesla referral code - https://ts.la/richard11209

>
> Why did Testra attack me on comp.lang.forth with lies and insults?
> Tom Hart made this attack on the command of Juergen Pintaske, the MPE salesman.
> Apparently you were in negotiation with Stephen Pelc for him to buy the RACE processor,
> and you believed that you had to obey Juergen Pintaske's commands to stay on
> Stephen Pelc's good side. It is unlikely that Stephen Pelc was going to buy your RACE
> processor. He was most likely just tugging your chain for the entertainment value of
> getting you to attack your own employee on comp.lang.forth. You think that you can
> totally crush me here on comp.lang.forth, but you harm yourself as much or more
> than you harm me. Testra won't be considered to be a reputable company any more.
> You have more to lose than I do. People who live in glass houses shouldn't throw stones!
> Attacking me on comp.lang.forth was a bad idea. Was alcohol involved in this decision?

TYPICAL HUCK AQUILUX BULLSHIT AGAIN.

He insinuates things that were never planned nor happened,
just to be able to attack people again.
All of these attacked are professionals - in contrast to him and his behaviour here.
And to waste everybody's time.

HE IS INSANE AND PROBABLY A DANGER FOR THE PEOPLE AROUND HIM.

I had just asked Testra to kindly state his activities with Testra
as an answer to all of his accusations here.
- which they did under the condition their email is published in full - which I did.
If there are some differences in perceptions 30 years later - so what.
This is how life works.

On Friday, April 28, 2023 at 10:41:09 PM UTC-7, Jurgen Pitaske wrote:
> >
> > Why did Testra attack me on comp.lang.forth with lies and insults?

No one from Testra ever attacked anyone on comp.lang.forth
or any other news group ever.

A gifted programmer, with no experience was given a chance,
succeeded and was let go after he finished because there was
nothing for him to do.

> I had just asked Testra to kindly state his activities with Testra
Which indicated he was a creative individual and like many creative
individuals, might be difficult to work with. A truth that's easily verified
by reading posts on this and many other tech newsgroups.

Not referring to anyone specific, some people not only burn their bridges
they spend years taking the foundation down to bedrock with a jackhammer
until no evidence of what they accomplished remains.

Flame wars are not only counterproductive they're destructive. Most
people, if they knew then what they know now, would have done things
differently. It's also true that if wishes were horses, beggers would ride.

Learning from past mistakes is good, getting mired in them is not.

My purpose for writing is NOT to get sucked into a flame war,
it's to have a discussion about Forth being the ideal language for a
Reconfigurable Architecture Computation Engine, specifically the
RACE32, which we are in the process of completing,

A thousand such processors could run on one of the new FPGA chips,
but the main applications, automation and robotics, would require
only one and run on a low cost device.
jrh

On Friday, April 28, 2023 at 5:06:51 PM UTC-7, Lorem Ipsum wrote:
> On Friday, April 28, 2023 at 2:56:23 PM UTC-4, John Hart wrote:
> > On Thursday, April 27, 2023 at 7:44:11 PM UTC-7, Hugh Aguilar wrote:
> > > On Wednesday, April 26, 2023 at 5:59:22 PM UTC-7, John Hart wrote:
> > > > On Tuesday, April 25, 2023 at 6:23:15 PM UTC-7, Lorem Ipsum wrote:
> > > > > I can't think of anything that is harder to do in an FPGA than in a CPLD,
> > > > ><clip>

> What mess??? I must have missed something.
> Rick C.
Not your fault if you still rely on MSM for your news.
America is in sharp decline on many fronts and MSM has been working overtime
hiding it. The parts of our social economic system are strongly linked and
a series of errors by the current administration, as serious as the Titanic
hittting an iceberg, have occured. The only solution is to get productivity
growing faster than debt to prevent runaway inflation, and that's going
to require an autiomation revolution at the roots. The concentration of
wealth by the Elite, not only stifles innovation it's extremely dangerous.
After all, power corrupts and absolute power corrupts absolutely.

On Saturday, 29 April 2023 at 07:47:36 UTC+1, John Hart wrote:
> On Friday, April 28, 2023 at 10:41:09 PM UTC-7, Jurgen Pitaske wrote:
> > >
> > > Why did Testra attack me on comp.lang.forth with lies and insults?
> No one from Testra ever attacked anyone on comp.lang.forth
> or any other news group ever.
>
> A gifted programmer, with no experience was given a chance,
> succeeded and was let go after he finished because there was
> nothing for him to do.
> > I had just asked Testra to kindly state his activities with Testra
> Which indicated he was a creative individual and like many creative
> individuals, might be difficult to work with. A truth that's easily verified
> by reading posts on this and many other tech newsgroups.
>
> Not referring to anyone specific, some people not only burn their bridges
> they spend years taking the foundation down to bedrock with a jackhammer
> until no evidence of what they accomplished remains.
>
> Flame wars are not only counterproductive they're destructive. Most
> people, if they knew then what they know now, would have done things
> differently. It's also true that if wishes were horses, beggers would ride.
>
> Learning from past mistakes is good, getting mired in them is not.
>
> My purpose for writing is NOT to get sucked into a flame war,
> it's to have a discussion about Forth being the ideal language for a
> Reconfigurable Architecture Computation Engine, specifically the
> RACE32, which we are in the process of completing,
>
> A thousand such processors could run on one of the new FPGA chips,
> but the main applications, automation and robotics, would require
> only one and run on a low cost device.
> jrh

A great post - Thank You

On Saturday, April 29, 2023 at 3:07:22 AM UTC-4, John Hart wrote:
> On Friday, April 28, 2023 at 5:06:51 PM UTC-7, Lorem Ipsum wrote:
> > On Friday, April 28, 2023 at 2:56:23 PM UTC-4, John Hart wrote:
> > > On Thursday, April 27, 2023 at 7:44:11 PM UTC-7, Hugh Aguilar wrote:
> > > > On Wednesday, April 26, 2023 at 5:59:22 PM UTC-7, John Hart wrote:
> > > > > On Tuesday, April 25, 2023 at 6:23:15 PM UTC-7, Lorem Ipsum wrote:
> > > > > > I can't think of anything that is harder to do in an FPGA than in a CPLD,
> > > > > ><clip>
> > What mess??? I must have missed something.
> > Rick C.
> Not your fault if you still rely on MSM for your news.
> America is in sharp decline on many fronts and MSM has been working overtime
> hiding it. The parts of our social economic system are strongly linked and
> a series of errors by the current administration, as serious as the Titanic
> hittting an iceberg, have occured. The only solution is to get productivity
> growing faster than debt to prevent runaway inflation, and that's going
> to require an autiomation revolution at the roots. The concentration of
> wealth by the Elite, not only stifles innovation it's extremely dangerous..
> After all, power corrupts and absolute power corrupts absolutely.

Got it. I completely understand now. Thanks

--

Rick C.

-+-+ Get 1,000 miles of free Supercharging
-+-+ Tesla referral code - https://ts.la/richard11209

On Friday, April 28, 2023 at 11:47:36 PM UTC-7, John Hart wrote:
> On Friday, April 28, 2023 at 10:41:09 PM UTC-7, Jurgen Pitaske wrote:
> > >
> > > Why did Testra attack me on comp.lang.forth with lies and insults?
> No one from Testra ever attacked anyone on comp.lang.forth
> or any other news group ever.

Bullshit!
This entire thread was an unprovoked attack on me:
https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0

Tom Hart was totally lying:
> I let him go myself,
> after I had given him a project to write a DXF converter to HPGL code.
> He would not take any direction.
> I scrapped the project.

I never even heard of HPGL before this attack. There was no HPGL project.
Also, I never got any direction in any of my work.
When I wrote the DXF to GCODE converter nobody told me about how
Bezier Splines might work. I didn't know about Bezier Splines, and I assume
that the reason I wasn't told about Bezier Splines is that Tom and John Hart
don't know about them either. Tom Hart would just angrily tell me:
"Just make a smooth line through all the tiny line segments!"
There was just a mish-mash of tiny line segments ranging from 1/1000 of an inch
to 20/1000 of an inch, and some longer. They pointed in every which direction. Some
weren't touching any other line segment and some touched other line segments.
I had no idea how to make a smooth line through this mess. I wished that I did
have some direction, but I never did. I wished that I had mind-reading ability
so that I could know what image the artist had intended with this mish-mash..
Tom Hart says that I'm too stupid to write a data-conversion program.
This isn't true. I was converting DXF code to GCODE within a couple of weeks
of starting the project. The problem was that the result was a mess.
When I started the project I was told that this was a simple data-conversion
program, so I felt confident that I could finish in a few weeks. If I had been told
that I had to make a smooth line through a big mess of tiny line-segments,
I would have refused the job. If I had been told that I needed Bezier Splines
I would have refused the job because I don't know anything about the subject.
(This is where the comp.lang.forth trolls can spring into action and say that
they could easily implement Bezier Splines, so they get to be big internet experts
without writing any code, as usual).

Tom Hart was totally lying:
> [Hugh] had nothing to do with the processor itself,
> that was all designed by John Hart and Steve Brault.
>
> The PLD version was based upon our original Forth Engine done long before
> we ever ran across Hugh.

The original Forth Engine was a bit-slice processor.
This is unrelated to the MiniForth that was a VLIW processor.
Tom Hart is saying that MFX was written for the bit-slice processor and then
was used on the MiniForth. Bullshit! I wrote MFX for the MiniForth (MFX means
Mini Forth Xcompiler). I never saw any of the code from the original Forth Engine.
All of that was written by John Perona who later wrote Multi-Edit. Even if there
had been some similarity between the original Forth Engine and the MiniForth,
I still wouldn't have looked at John Perona's code because I never look at other
people's code (that is like peering through a bedroom window to look at your
neighbor's wife). Also, as a practical matter John Perona is a typical C programmer
who writes multi-page functions. He doesn't factor code at all.

Testra was originally called Hartronics and they advertised their "Forth Engine"
in Forth Dimensions, in case anybody cares (I don't).

It was obvious that Juergen Pintaske wanted to denounce me on comp.lang.forth,
by saying that I am lying about writing MFX at Testra. Tom Hart totally complied by
providing Juergen Pintaske with support for this attack. All of Juergen Pintaske's
attacks on me over the last four years have been based on him obtaining 100%
support from Tom Hart.
It is very disingenuous for John Hart to now say:
> No one from Testra ever attacked anyone on comp.lang.forth
> or any other news group ever.
Bullshit! You could have ignored Juergen Pintaske. Everybody else in the world does!
Instead you provided Juergen Pintaske with 100% support for attacking me.
Juergen Pintaske is now Testra's mouthpiece, and he has Tom Hart's support in this.

> Not referring to anyone specific, some people not only burn their bridges
> they spend years taking the foundation down to bedrock with a jackhammer
> until no evidence of what they accomplished remains.

It was in the 1990s, less than five years after I left Testra, when I heard John Hart
(possibly Tom Hart doing an impersonation) say on speaker-phone that I had
accomplished "nothing" and that I was not eligible for rehire. Presumably Testra had
been saying this starting immediately after I left Testra but it was a few years later
when I caught them at this. So, it didn't take Tom Hart long to burn his bridge with me,
and jackhammer the foundation, to ensure that no evidence of accomplishment remains.
Tom Hart cares about loyalty! He expects employees to remain employed forever,
never asking for a raise or health insurance or anything else. Loyalty is a one-way street;
Tom Hart has no sense of loyalty to his employees and will attack them in public.

Why didn't Testra just tell me when I left that leaving was an act of disloyalty
and that I would never get a reference? I made a fool out of myself by going to
job interviews, such as at Lockheed Martin, and saying that I wrote MFX at Testra.
Most likely, Testra wanted me to go to these job interviews and describe MFX,
not for my benefit, but just as an advertisement for Testra's MiniForth processor.
They may have been hoping that Lockheed Martin would buy the MiniForth so
they could become wealthy, but they had no way to get Lockheed Martin's attention.
You can't just show up in the lobby of Lockheed Martin and tell the receptionist:
"Hi! I've got a super-awesome processor! Would you like to buy it?"
They may have believed (correctly) that for me to go to a job interview at
Lockheed Martin and describe MFX would be the only way that Lockheed Martin
would find out about the MiniForth --- but they would pull the rug out from under me
by telling Lockheed Martin that they wrote MFX --- they would explain to
Lockheed Martin that they are geniuses who deserve to get rich!

On Sunday, 30 April 2023 at 00:34:09 UTC+1, Hugh Aguilar wrote:
> On Friday, April 28, 2023 at 11:47:36 PM UTC-7, John Hart wrote:
> > On Friday, April 28, 2023 at 10:41:09 PM UTC-7, Jurgen Pitaske wrote:
> > > >
> > > > Why did Testra attack me on comp.lang.forth with lies and insults?
> > No one from Testra ever attacked anyone on comp.lang.forth
> > or any other news group ever.
> Bullshit!
> This entire thread was an unprovoked attack on me:
> https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0
>
> Tom Hart was totally lying:
> > I let him go myself,
> > after I had given him a project to write a DXF converter to HPGL code.
> > He would not take any direction.
> > I scrapped the project.
>
> I never even heard of HPGL before this attack. There was no HPGL project.
> Also, I never got any direction in any of my work.
> When I wrote the DXF to GCODE converter nobody told me about how
> Bezier Splines might work. I didn't know about Bezier Splines, and I assume
> that the reason I wasn't told about Bezier Splines is that Tom and John Hart
> don't know about them either. Tom Hart would just angrily tell me:
> "Just make a smooth line through all the tiny line segments!"
> There was just a mish-mash of tiny line segments ranging from 1/1000 of an inch
> to 20/1000 of an inch, and some longer. They pointed in every which direction. Some
> weren't touching any other line segment and some touched other line segments.
> I had no idea how to make a smooth line through this mess. I wished that I did
> have some direction, but I never did. I wished that I had mind-reading ability
> so that I could know what image the artist had intended with this mish-mash.
> Tom Hart says that I'm too stupid to write a data-conversion program.
> This isn't true. I was converting DXF code to GCODE within a couple of weeks
> of starting the project. The problem was that the result was a mess.
> When I started the project I was told that this was a simple data-conversion
> program, so I felt confident that I could finish in a few weeks. If I had been told
> that I had to make a smooth line through a big mess of tiny line-segments,
> I would have refused the job. If I had been told that I needed Bezier Splines
> I would have refused the job because I don't know anything about the subject.
> (This is where the comp.lang.forth trolls can spring into action and say that
> they could easily implement Bezier Splines, so they get to be big internet experts
> without writing any code, as usual).
>
> Tom Hart was totally lying:
> > [Hugh] had nothing to do with the processor itself,
> > that was all designed by John Hart and Steve Brault.
> >
> > The PLD version was based upon our original Forth Engine done long before
> > we ever ran across Hugh.
> The original Forth Engine was a bit-slice processor.
> This is unrelated to the MiniForth that was a VLIW processor.
> Tom Hart is saying that MFX was written for the bit-slice processor and then
> was used on the MiniForth. Bullshit! I wrote MFX for the MiniForth (MFX means
> Mini Forth Xcompiler). I never saw any of the code from the original Forth Engine.
> All of that was written by John Perona who later wrote Multi-Edit. Even if there
> had been some similarity between the original Forth Engine and the MiniForth,
> I still wouldn't have looked at John Perona's code because I never look at other
> people's code (that is like peering through a bedroom window to look at your
> neighbor's wife). Also, as a practical matter John Perona is a typical C programmer
> who writes multi-page functions. He doesn't factor code at all.
>
> Testra was originally called Hartronics and they advertised their "Forth Engine"
> in Forth Dimensions, in case anybody cares (I don't).
>
> It was obvious that Juergen Pintaske wanted to denounce me on comp.lang.forth,
> by saying that I am lying about writing MFX at Testra. Tom Hart totally complied by
> providing Juergen Pintaske with support for this attack. All of Juergen Pintaske's
> attacks on me over the last four years have been based on him obtaining 100%
> support from Tom Hart.
> It is very disingenuous for John Hart to now say:
> > No one from Testra ever attacked anyone on comp.lang.forth
> > or any other news group ever.
> Bullshit! You could have ignored Juergen Pintaske. Everybody else in the world does!
> Instead you provided Juergen Pintaske with 100% support for attacking me.
> Juergen Pintaske is now Testra's mouthpiece, and he has Tom Hart's support in this.
> > Not referring to anyone specific, some people not only burn their bridges
> > they spend years taking the foundation down to bedrock with a jackhammer
> > until no evidence of what they accomplished remains.
> It was in the 1990s, less than five years after I left Testra, when I heard John Hart
> (possibly Tom Hart doing an impersonation) say on speaker-phone that I had
> accomplished "nothing" and that I was not eligible for rehire. Presumably Testra had
> been saying this starting immediately after I left Testra but it was a few years later
> when I caught them at this. So, it didn't take Tom Hart long to burn his bridge with me,
> and jackhammer the foundation, to ensure that no evidence of accomplishment remains.
> Tom Hart cares about loyalty! He expects employees to remain employed forever,
> never asking for a raise or health insurance or anything else. Loyalty is a one-way street;
> Tom Hart has no sense of loyalty to his employees and will attack them in public.
>
> Why didn't Testra just tell me when I left that leaving was an act of disloyalty
> and that I would never get a reference? I made a fool out of myself by going to
> job interviews, such as at Lockheed Martin, and saying that I wrote MFX at Testra.
> Most likely, Testra wanted me to go to these job interviews and describe MFX,
> not for my benefit, but just as an advertisement for Testra's MiniForth processor.
> They may have been hoping that Lockheed Martin would buy the MiniForth so
> they could become wealthy, but they had no way to get Lockheed Martin's attention.
> You can't just show up in the lobby of Lockheed Martin and tell the receptionist:
> "Hi! I've got a super-awesome processor! Would you like to buy it?"
> They may have believed (correctly) that for me to go to a job interview at
> Lockheed Martin and describe MFX would be the only way that Lockheed Martin
> would find out about the MiniForth --- but they would pull the rug out from under me
> by telling Lockheed Martin that they wrote MFX --- they would explain to
> Lockheed Martin that they are geniuses who deserve to get rich!

WHAT A MENTAL DESASTER AGAIN.

Everybody is a liar - which automatically leads to
HUGH AGUILAR IS an AGUILIAR as he is part of everybody.
GO BACK TO YOUR CAGE AND BARK OR NOT.

Another made up piece of lies - just to make you feel good.

I did my job at MPE as consultant,
which triggered tmy FORTH BOOKSHELF on amazon
https://www.amazon.co.uk/Juergen-Pintaske/e/B00N8HVEZM%3Fref=dbs_a_mng_rwt_scns_share
I convinced Steve to do the 1802 in FPGA and the FIG-Forth that goees with it on github.
And he did as well the MISC PROCESSOR I HAD INITIATED in FPGA plus a Forth that goes with it.
What have you contributed over the last 30 years
- except of often dayly rants and
accusations of probably everybody here.

On Sunday, 30 April 2023 at 07:14:16 UTC+1, Jurgen Pitaske wrote:
> On Sunday, 30 April 2023 at 00:34:09 UTC+1, Hugh Aguilar wrote:
> > On Friday, April 28, 2023 at 11:47:36 PM UTC-7, John Hart wrote:
> > > On Friday, April 28, 2023 at 10:41:09 PM UTC-7, Jurgen Pitaske wrote:
> > > > >
> > > > > Why did Testra attack me on comp.lang.forth with lies and insults?
> > > No one from Testra ever attacked anyone on comp.lang.forth
> > > or any other news group ever.
> > Bullshit!
> > This entire thread was an unprovoked attack on me:
> > https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0
> >
> > Tom Hart was totally lying:
> > > I let him go myself,
> > > after I had given him a project to write a DXF converter to HPGL code..
> > > He would not take any direction.
> > > I scrapped the project.
> >
> > I never even heard of HPGL before this attack. There was no HPGL project.
> > Also, I never got any direction in any of my work.
> > When I wrote the DXF to GCODE converter nobody told me about how
> > Bezier Splines might work. I didn't know about Bezier Splines, and I assume
> > that the reason I wasn't told about Bezier Splines is that Tom and John Hart
> > don't know about them either. Tom Hart would just angrily tell me:
> > "Just make a smooth line through all the tiny line segments!"
> > There was just a mish-mash of tiny line segments ranging from 1/1000 of an inch
> > to 20/1000 of an inch, and some longer. They pointed in every which direction. Some
> > weren't touching any other line segment and some touched other line segments.
> > I had no idea how to make a smooth line through this mess. I wished that I did
> > have some direction, but I never did. I wished that I had mind-reading ability
> > so that I could know what image the artist had intended with this mish-mash.
> > Tom Hart says that I'm too stupid to write a data-conversion program.
> > This isn't true. I was converting DXF code to GCODE within a couple of weeks
> > of starting the project. The problem was that the result was a mess.
> > When I started the project I was told that this was a simple data-conversion
> > program, so I felt confident that I could finish in a few weeks. If I had been told
> > that I had to make a smooth line through a big mess of tiny line-segments,
> > I would have refused the job. If I had been told that I needed Bezier Splines
> > I would have refused the job because I don't know anything about the subject.
> > (This is where the comp.lang.forth trolls can spring into action and say that
> > they could easily implement Bezier Splines, so they get to be big internet experts
> > without writing any code, as usual).
> >
> > Tom Hart was totally lying:
> > > [Hugh] had nothing to do with the processor itself,
> > > that was all designed by John Hart and Steve Brault.
> > >
> > > The PLD version was based upon our original Forth Engine done long before
> > > we ever ran across Hugh.
> > The original Forth Engine was a bit-slice processor.
> > This is unrelated to the MiniForth that was a VLIW processor.
> > Tom Hart is saying that MFX was written for the bit-slice processor and then
> > was used on the MiniForth. Bullshit! I wrote MFX for the MiniForth (MFX means
> > Mini Forth Xcompiler). I never saw any of the code from the original Forth Engine.
> > All of that was written by John Perona who later wrote Multi-Edit. Even if there
> > had been some similarity between the original Forth Engine and the MiniForth,
> > I still wouldn't have looked at John Perona's code because I never look at other
> > people's code (that is like peering through a bedroom window to look at your
> > neighbor's wife). Also, as a practical matter John Perona is a typical C programmer
> > who writes multi-page functions. He doesn't factor code at all.
> >
> > Testra was originally called Hartronics and they advertised their "Forth Engine"
> > in Forth Dimensions, in case anybody cares (I don't).
> >
> > It was obvious that Juergen Pintaske wanted to denounce me on comp.lang..forth,
> > by saying that I am lying about writing MFX at Testra. Tom Hart totally complied by
> > providing Juergen Pintaske with support for this attack. All of Juergen Pintaske's
> > attacks on me over the last four years have been based on him obtaining 100%
> > support from Tom Hart.
> > It is very disingenuous for John Hart to now say:
> > > No one from Testra ever attacked anyone on comp.lang.forth
> > > or any other news group ever.
> > Bullshit! You could have ignored Juergen Pintaske. Everybody else in the world does!
> > Instead you provided Juergen Pintaske with 100% support for attacking me.
> > Juergen Pintaske is now Testra's mouthpiece, and he has Tom Hart's support in this.
> > > Not referring to anyone specific, some people not only burn their bridges
> > > they spend years taking the foundation down to bedrock with a jackhammer
> > > until no evidence of what they accomplished remains.
> > It was in the 1990s, less than five years after I left Testra, when I heard John Hart
> > (possibly Tom Hart doing an impersonation) say on speaker-phone that I had
> > accomplished "nothing" and that I was not eligible for rehire. Presumably Testra had
> > been saying this starting immediately after I left Testra but it was a few years later
> > when I caught them at this. So, it didn't take Tom Hart long to burn his bridge with me,
> > and jackhammer the foundation, to ensure that no evidence of accomplishment remains.
> > Tom Hart cares about loyalty! He expects employees to remain employed forever,
> > never asking for a raise or health insurance or anything else. Loyalty is a one-way street;
> > Tom Hart has no sense of loyalty to his employees and will attack them in public.
> >
> > Why didn't Testra just tell me when I left that leaving was an act of disloyalty
> > and that I would never get a reference? I made a fool out of myself by going to
> > job interviews, such as at Lockheed Martin, and saying that I wrote MFX at Testra.
> > Most likely, Testra wanted me to go to these job interviews and describe MFX,
> > not for my benefit, but just as an advertisement for Testra's MiniForth processor.
> > They may have been hoping that Lockheed Martin would buy the MiniForth so
> > they could become wealthy, but they had no way to get Lockheed Martin's attention.
> > You can't just show up in the lobby of Lockheed Martin and tell the receptionist:
> > "Hi! I've got a super-awesome processor! Would you like to buy it?"
> > They may have believed (correctly) that for me to go to a job interview at
> > Lockheed Martin and describe MFX would be the only way that Lockheed Martin
> > would find out about the MiniForth --- but they would pull the rug out from under me
> > by telling Lockheed Martin that they wrote MFX --- they would explain to
> > Lockheed Martin that they are geniuses who deserve to get rich!
> WHAT A MENTAL DESASTER AGAIN.
>
> Everybody is a liar - which automatically leads to
> HUGH AGUILAR IS an AGUILIAR as he is part of everybody.
> GO BACK TO YOUR CAGE AND BARK OR NOT.
>
> Another made up piece of lies - just to make you feel good.
>
> I did my job at MPE as consultant,
> which triggered tmy FORTH BOOKSHELF on amazon
> https://www.amazon.co.uk/Juergen-Pintaske/e/B00N8HVEZM%3Fref=dbs_a_mng_rwt_scns_share
> I convinced Steve to do the 1802 in FPGA and the FIG-Forth that goees with it on github.
> And he did as well the MISC PROCESSOR I HAD INITIATED in FPGA plus a Forth that goes with it.
> What have you contributed over the last 30 years
> - except of often dayly rants and
> accusations of probably everybody here.

LIAR LIAR LIAR - YOU ARE DOING WELL.
To state that my letter to Testra and the kind answer from there was started without reason
is the biggest lie you ever told.

You have attacked me over the last 10 years for no real reason
- it is all here on CLF so you can check
for no real reason.
So I wondered what Testra would say about you,
and it ended up in the probably most read post of CLF with about 4400 reads now.
https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0
It will be 4444 soon -
You cannot get closer to fours.
Have a nice day,
and May The Fours Be With You.

On Sunday, 30 April 2023 at 07:22:12 UTC+1, Jurgen Pitaske wrote:
> On Sunday, 30 April 2023 at 07:14:16 UTC+1, Jurgen Pitaske wrote:
> > On Sunday, 30 April 2023 at 00:34:09 UTC+1, Hugh Aguilar wrote:
> > > On Friday, April 28, 2023 at 11:47:36 PM UTC-7, John Hart wrote:
> > > > On Friday, April 28, 2023 at 10:41:09 PM UTC-7, Jurgen Pitaske wrote:
> > > > > >
> > > > > > Why did Testra attack me on comp.lang.forth with lies and insults?
> > > > No one from Testra ever attacked anyone on comp.lang.forth
> > > > or any other news group ever.
> > > Bullshit!
> > > This entire thread was an unprovoked attack on me:
> > > https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0
> > >
> > > Tom Hart was totally lying:
> > > > I let him go myself,
> > > > after I had given him a project to write a DXF converter to HPGL code.
> > > > He would not take any direction.
> > > > I scrapped the project.
> > >
> > > I never even heard of HPGL before this attack. There was no HPGL project.
> > > Also, I never got any direction in any of my work.
> > > When I wrote the DXF to GCODE converter nobody told me about how
> > > Bezier Splines might work. I didn't know about Bezier Splines, and I assume
> > > that the reason I wasn't told about Bezier Splines is that Tom and John Hart
> > > don't know about them either. Tom Hart would just angrily tell me:
> > > "Just make a smooth line through all the tiny line segments!"
> > > There was just a mish-mash of tiny line segments ranging from 1/1000 of an inch
> > > to 20/1000 of an inch, and some longer. They pointed in every which direction. Some
> > > weren't touching any other line segment and some touched other line segments.
> > > I had no idea how to make a smooth line through this mess. I wished that I did
> > > have some direction, but I never did. I wished that I had mind-reading ability
> > > so that I could know what image the artist had intended with this mish-mash.
> > > Tom Hart says that I'm too stupid to write a data-conversion program.
> > > This isn't true. I was converting DXF code to GCODE within a couple of weeks
> > > of starting the project. The problem was that the result was a mess.
> > > When I started the project I was told that this was a simple data-conversion
> > > program, so I felt confident that I could finish in a few weeks. If I had been told
> > > that I had to make a smooth line through a big mess of tiny line-segments,
> > > I would have refused the job. If I had been told that I needed Bezier Splines
> > > I would have refused the job because I don't know anything about the subject.
> > > (This is where the comp.lang.forth trolls can spring into action and say that
> > > they could easily implement Bezier Splines, so they get to be big internet experts
> > > without writing any code, as usual).
> > >
> > > Tom Hart was totally lying:
> > > > [Hugh] had nothing to do with the processor itself,
> > > > that was all designed by John Hart and Steve Brault.
> > > >
> > > > The PLD version was based upon our original Forth Engine done long before
> > > > we ever ran across Hugh.
> > > The original Forth Engine was a bit-slice processor.
> > > This is unrelated to the MiniForth that was a VLIW processor.
> > > Tom Hart is saying that MFX was written for the bit-slice processor and then
> > > was used on the MiniForth. Bullshit! I wrote MFX for the MiniForth (MFX means
> > > Mini Forth Xcompiler). I never saw any of the code from the original Forth Engine.
> > > All of that was written by John Perona who later wrote Multi-Edit. Even if there
> > > had been some similarity between the original Forth Engine and the MiniForth,
> > > I still wouldn't have looked at John Perona's code because I never look at other
> > > people's code (that is like peering through a bedroom window to look at your
> > > neighbor's wife). Also, as a practical matter John Perona is a typical C programmer
> > > who writes multi-page functions. He doesn't factor code at all.
> > >
> > > Testra was originally called Hartronics and they advertised their "Forth Engine"
> > > in Forth Dimensions, in case anybody cares (I don't).
> > >
> > > It was obvious that Juergen Pintaske wanted to denounce me on comp.lang.forth,
> > > by saying that I am lying about writing MFX at Testra. Tom Hart totally complied by
> > > providing Juergen Pintaske with support for this attack. All of Juergen Pintaske's
> > > attacks on me over the last four years have been based on him obtaining 100%
> > > support from Tom Hart.
> > > It is very disingenuous for John Hart to now say:
> > > > No one from Testra ever attacked anyone on comp.lang.forth
> > > > or any other news group ever.
> > > Bullshit! You could have ignored Juergen Pintaske. Everybody else in the world does!
> > > Instead you provided Juergen Pintaske with 100% support for attacking me.
> > > Juergen Pintaske is now Testra's mouthpiece, and he has Tom Hart's support in this.
> > > > Not referring to anyone specific, some people not only burn their bridges
> > > > they spend years taking the foundation down to bedrock with a jackhammer
> > > > until no evidence of what they accomplished remains.
> > > It was in the 1990s, less than five years after I left Testra, when I heard John Hart
> > > (possibly Tom Hart doing an impersonation) say on speaker-phone that I had
> > > accomplished "nothing" and that I was not eligible for rehire. Presumably Testra had
> > > been saying this starting immediately after I left Testra but it was a few years later
> > > when I caught them at this. So, it didn't take Tom Hart long to burn his bridge with me,
> > > and jackhammer the foundation, to ensure that no evidence of accomplishment remains.
> > > Tom Hart cares about loyalty! He expects employees to remain employed forever,
> > > never asking for a raise or health insurance or anything else. Loyalty is a one-way street;
> > > Tom Hart has no sense of loyalty to his employees and will attack them in public.
> > >
> > > Why didn't Testra just tell me when I left that leaving was an act of disloyalty
> > > and that I would never get a reference? I made a fool out of myself by going to
> > > job interviews, such as at Lockheed Martin, and saying that I wrote MFX at Testra.
> > > Most likely, Testra wanted me to go to these job interviews and describe MFX,
> > > not for my benefit, but just as an advertisement for Testra's MiniForth processor.
> > > They may have been hoping that Lockheed Martin would buy the MiniForth so
> > > they could become wealthy, but they had no way to get Lockheed Martin's attention.
> > > You can't just show up in the lobby of Lockheed Martin and tell the receptionist:
> > > "Hi! I've got a super-awesome processor! Would you like to buy it?"
> > > They may have believed (correctly) that for me to go to a job interview at
> > > Lockheed Martin and describe MFX would be the only way that Lockheed Martin
> > > would find out about the MiniForth --- but they would pull the rug out from under me
> > > by telling Lockheed Martin that they wrote MFX --- they would explain to
> > > Lockheed Martin that they are geniuses who deserve to get rich!
> > WHAT A MENTAL DESASTER AGAIN.
> >
> > Everybody is a liar - which automatically leads to
> > HUGH AGUILAR IS an AGUILIAR as he is part of everybody.
> > GO BACK TO YOUR CAGE AND BARK OR NOT.
> >
> > Another made up piece of lies - just to make you feel good.
> >
> > I did my job at MPE as consultant,
> > which triggered tmy FORTH BOOKSHELF on amazon
> > https://www.amazon.co.uk/Juergen-Pintaske/e/B00N8HVEZM%3Fref=dbs_a_mng_rwt_scns_share
> > I convinced Steve to do the 1802 in FPGA and the FIG-Forth that goees with it on github.
> > And he did as well the MISC PROCESSOR I HAD INITIATED in FPGA plus a Forth that goes with it.
> > What have you contributed over the last 30 years
> > - except of often dayly rants and
> > accusations of probably everybody here.
> LIAR LIAR LIAR - YOU ARE DOING WELL.
> To state that my letter to Testra and the kind answer from there was started without reason
> is the biggest lie you ever told.
>
> You have attacked me over the last 10 years for no real reason
> - it is all here on CLF so you can check
> for no real reason.
> So I wondered what Testra would say about you,
> and it ended up in the probably most read post of CLF with about 4400 reads now.
> https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0
> It will be 4444 soon -
> You cannot get closer to fours.
> Have a nice day,
> and May The Fours Be With You.

On Sunday, 30 April 2023 at 07:22:12 UTC+1, Jurgen Pitaske wrote:
> On Sunday, 30 April 2023 at 07:14:16 UTC+1, Jurgen Pitaske wrote:
> > On Sunday, 30 April 2023 at 00:34:09 UTC+1, Hugh Aguilar wrote:
> > > On Friday, April 28, 2023 at 11:47:36 PM UTC-7, John Hart wrote:
> > > > On Friday, April 28, 2023 at 10:41:09 PM UTC-7, Jurgen Pitaske wrote:
> > > > > >
> > > > > > Why did Testra attack me on comp.lang.forth with lies and insults?
> > > > No one from Testra ever attacked anyone on comp.lang.forth
> > > > or any other news group ever.
> > > Bullshit!
> > > This entire thread was an unprovoked attack on me:
> > > https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0
> > >
> > > Tom Hart was totally lying:
> > > > I let him go myself,
> > > > after I had given him a project to write a DXF converter to HPGL code.
> > > > He would not take any direction.
> > > > I scrapped the project.
> > >
> > > I never even heard of HPGL before this attack. There was no HPGL project.
> > > Also, I never got any direction in any of my work.
> > > When I wrote the DXF to GCODE converter nobody told me about how
> > > Bezier Splines might work. I didn't know about Bezier Splines, and I assume
> > > that the reason I wasn't told about Bezier Splines is that Tom and John Hart
> > > don't know about them either. Tom Hart would just angrily tell me:
> > > "Just make a smooth line through all the tiny line segments!"
> > > There was just a mish-mash of tiny line segments ranging from 1/1000 of an inch
> > > to 20/1000 of an inch, and some longer. They pointed in every which direction. Some
> > > weren't touching any other line segment and some touched other line segments.
> > > I had no idea how to make a smooth line through this mess. I wished that I did
> > > have some direction, but I never did. I wished that I had mind-reading ability
> > > so that I could know what image the artist had intended with this mish-mash.
> > > Tom Hart says that I'm too stupid to write a data-conversion program.
> > > This isn't true. I was converting DXF code to GCODE within a couple of weeks
> > > of starting the project. The problem was that the result was a mess.
> > > When I started the project I was told that this was a simple data-conversion
> > > program, so I felt confident that I could finish in a few weeks. If I had been told
> > > that I had to make a smooth line through a big mess of tiny line-segments,
> > > I would have refused the job. If I had been told that I needed Bezier Splines
> > > I would have refused the job because I don't know anything about the subject.
> > > (This is where the comp.lang.forth trolls can spring into action and say that
> > > they could easily implement Bezier Splines, so they get to be big internet experts
> > > without writing any code, as usual).
> > >
> > > Tom Hart was totally lying:
> > > > [Hugh] had nothing to do with the processor itself,
> > > > that was all designed by John Hart and Steve Brault.
> > > >
> > > > The PLD version was based upon our original Forth Engine done long before
> > > > we ever ran across Hugh.
> > > The original Forth Engine was a bit-slice processor.
> > > This is unrelated to the MiniForth that was a VLIW processor.
> > > Tom Hart is saying that MFX was written for the bit-slice processor and then
> > > was used on the MiniForth. Bullshit! I wrote MFX for the MiniForth (MFX means
> > > Mini Forth Xcompiler). I never saw any of the code from the original Forth Engine.
> > > All of that was written by John Perona who later wrote Multi-Edit. Even if there
> > > had been some similarity between the original Forth Engine and the MiniForth,
> > > I still wouldn't have looked at John Perona's code because I never look at other
> > > people's code (that is like peering through a bedroom window to look at your
> > > neighbor's wife). Also, as a practical matter John Perona is a typical C programmer
> > > who writes multi-page functions. He doesn't factor code at all.
> > >
> > > Testra was originally called Hartronics and they advertised their "Forth Engine"
> > > in Forth Dimensions, in case anybody cares (I don't).
> > >
> > > It was obvious that Juergen Pintaske wanted to denounce me on comp.lang.forth,
> > > by saying that I am lying about writing MFX at Testra. Tom Hart totally complied by
> > > providing Juergen Pintaske with support for this attack. All of Juergen Pintaske's
> > > attacks on me over the last four years have been based on him obtaining 100%
> > > support from Tom Hart.
> > > It is very disingenuous for John Hart to now say:
> > > > No one from Testra ever attacked anyone on comp.lang.forth
> > > > or any other news group ever.
> > > Bullshit! You could have ignored Juergen Pintaske. Everybody else in the world does!
> > > Instead you provided Juergen Pintaske with 100% support for attacking me.
> > > Juergen Pintaske is now Testra's mouthpiece, and he has Tom Hart's support in this.
> > > > Not referring to anyone specific, some people not only burn their bridges
> > > > they spend years taking the foundation down to bedrock with a jackhammer
> > > > until no evidence of what they accomplished remains.
> > > It was in the 1990s, less than five years after I left Testra, when I heard John Hart
> > > (possibly Tom Hart doing an impersonation) say on speaker-phone that I had
> > > accomplished "nothing" and that I was not eligible for rehire. Presumably Testra had
> > > been saying this starting immediately after I left Testra but it was a few years later
> > > when I caught them at this. So, it didn't take Tom Hart long to burn his bridge with me,
> > > and jackhammer the foundation, to ensure that no evidence of accomplishment remains.
> > > Tom Hart cares about loyalty! He expects employees to remain employed forever,
> > > never asking for a raise or health insurance or anything else. Loyalty is a one-way street;
> > > Tom Hart has no sense of loyalty to his employees and will attack them in public.
> > >
> > > Why didn't Testra just tell me when I left that leaving was an act of disloyalty
> > > and that I would never get a reference? I made a fool out of myself by going to
> > > job interviews, such as at Lockheed Martin, and saying that I wrote MFX at Testra.
> > > Most likely, Testra wanted me to go to these job interviews and describe MFX,
> > > not for my benefit, but just as an advertisement for Testra's MiniForth processor.
> > > They may have been hoping that Lockheed Martin would buy the MiniForth so
> > > they could become wealthy, but they had no way to get Lockheed Martin's attention.
> > > You can't just show up in the lobby of Lockheed Martin and tell the receptionist:
> > > "Hi! I've got a super-awesome processor! Would you like to buy it?"
> > > They may have believed (correctly) that for me to go to a job interview at
> > > Lockheed Martin and describe MFX would be the only way that Lockheed Martin
> > > would find out about the MiniForth --- but they would pull the rug out from under me
> > > by telling Lockheed Martin that they wrote MFX --- they would explain to
> > > Lockheed Martin that they are geniuses who deserve to get rich!
> > WHAT A MENTAL DESASTER AGAIN.
> >
> > Everybody is a liar - which automatically leads to
> > HUGH AGUILAR IS an AGUILIAR as he is part of everybody.
> > GO BACK TO YOUR CAGE AND BARK OR NOT.
> >
> > Another made up piece of lies - just to make you feel good.
> >
> > I did my job at MPE as consultant,
> > which triggered tmy FORTH BOOKSHELF on amazon
> > https://www.amazon.co.uk/Juergen-Pintaske/e/B00N8HVEZM%3Fref=dbs_a_mng_rwt_scns_share
> > I convinced Steve to do the 1802 in FPGA and the FIG-Forth that goees with it on github.
> > And he did as well the MISC PROCESSOR I HAD INITIATED in FPGA plus a Forth that goes with it.
> > What have you contributed over the last 30 years
> > - except of often dayly rants and
> > accusations of probably everybody here.
> LIAR LIAR LIAR - YOU ARE DOING WELL.
> To state that my letter to Testra and the kind answer from there was started without reason
> is the biggest lie you ever told.
>
> You have attacked me over the last 10 years for no real reason
> - it is all here on CLF so you can check
> for no real reason.
> So I wondered what Testra would say about you,
> and it ended up in the probably most read post of CLF with about 4400 reads now.
> https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0
> It will be 4444 soon -
> You cannot get closer to fours.
> Have a nice day,
> and May The Fours Be With You.

On Sunday, April 30, 2023 at 4:26:49 AM UTC-4, Jurgen Pitaske wrote:
> On Sunday, 30 April 2023 at 07:22:12 UTC+1, Jurgen Pitaske wrote:
> > On Sunday, 30 April 2023 at 07:14:16 UTC+1, Jurgen Pitaske wrote:
> > > On Sunday, 30 April 2023 at 00:34:09 UTC+1, Hugh Aguilar wrote:
> > > > On Friday, April 28, 2023 at 11:47:36 PM UTC-7, John Hart wrote:
> > > > > On Friday, April 28, 2023 at 10:41:09 PM UTC-7, Jurgen Pitaske wrote:
> > > > > > >
> > > > > > > Why did Testra attack me on comp.lang.forth with lies and insults?
> > > > > No one from Testra ever attacked anyone on comp.lang.forth
> > > > > or any other news group ever.
> > > > Bullshit!
> > > > This entire thread was an unprovoked attack on me:
> > > > https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0
> > > >
> > > > Tom Hart was totally lying:
> > > > > I let him go myself,
> > > > > after I had given him a project to write a DXF converter to HPGL code.
> > > > > He would not take any direction.
> > > > > I scrapped the project.
> > > >
> > > > I never even heard of HPGL before this attack. There was no HPGL project.
> > > > Also, I never got any direction in any of my work.
> > > > When I wrote the DXF to GCODE converter nobody told me about how
> > > > Bezier Splines might work. I didn't know about Bezier Splines, and I assume
> > > > that the reason I wasn't told about Bezier Splines is that Tom and John Hart
> > > > don't know about them either. Tom Hart would just angrily tell me:
> > > > "Just make a smooth line through all the tiny line segments!"
> > > > There was just a mish-mash of tiny line segments ranging from 1/1000 of an inch
> > > > to 20/1000 of an inch, and some longer. They pointed in every which direction. Some
> > > > weren't touching any other line segment and some touched other line segments.
> > > > I had no idea how to make a smooth line through this mess. I wished that I did
> > > > have some direction, but I never did. I wished that I had mind-reading ability
> > > > so that I could know what image the artist had intended with this mish-mash.
> > > > Tom Hart says that I'm too stupid to write a data-conversion program.
> > > > This isn't true. I was converting DXF code to GCODE within a couple of weeks
> > > > of starting the project. The problem was that the result was a mess..
> > > > When I started the project I was told that this was a simple data-conversion
> > > > program, so I felt confident that I could finish in a few weeks. If I had been told
> > > > that I had to make a smooth line through a big mess of tiny line-segments,
> > > > I would have refused the job. If I had been told that I needed Bezier Splines
> > > > I would have refused the job because I don't know anything about the subject.
> > > > (This is where the comp.lang.forth trolls can spring into action and say that
> > > > they could easily implement Bezier Splines, so they get to be big internet experts
> > > > without writing any code, as usual).
> > > >
> > > > Tom Hart was totally lying:
> > > > > [Hugh] had nothing to do with the processor itself,
> > > > > that was all designed by John Hart and Steve Brault.
> > > > >
> > > > > The PLD version was based upon our original Forth Engine done long before
> > > > > we ever ran across Hugh.
> > > > The original Forth Engine was a bit-slice processor.
> > > > This is unrelated to the MiniForth that was a VLIW processor.
> > > > Tom Hart is saying that MFX was written for the bit-slice processor and then
> > > > was used on the MiniForth. Bullshit! I wrote MFX for the MiniForth (MFX means
> > > > Mini Forth Xcompiler). I never saw any of the code from the original Forth Engine.
> > > > All of that was written by John Perona who later wrote Multi-Edit. Even if there
> > > > had been some similarity between the original Forth Engine and the MiniForth,
> > > > I still wouldn't have looked at John Perona's code because I never look at other
> > > > people's code (that is like peering through a bedroom window to look at your
> > > > neighbor's wife). Also, as a practical matter John Perona is a typical C programmer
> > > > who writes multi-page functions. He doesn't factor code at all.
> > > >
> > > > Testra was originally called Hartronics and they advertised their "Forth Engine"
> > > > in Forth Dimensions, in case anybody cares (I don't).
> > > >
> > > > It was obvious that Juergen Pintaske wanted to denounce me on comp.lang.forth,
> > > > by saying that I am lying about writing MFX at Testra. Tom Hart totally complied by
> > > > providing Juergen Pintaske with support for this attack. All of Juergen Pintaske's
> > > > attacks on me over the last four years have been based on him obtaining 100%
> > > > support from Tom Hart.
> > > > It is very disingenuous for John Hart to now say:
> > > > > No one from Testra ever attacked anyone on comp.lang.forth
> > > > > or any other news group ever.
> > > > Bullshit! You could have ignored Juergen Pintaske. Everybody else in the world does!
> > > > Instead you provided Juergen Pintaske with 100% support for attacking me.
> > > > Juergen Pintaske is now Testra's mouthpiece, and he has Tom Hart's support in this.
> > > > > Not referring to anyone specific, some people not only burn their bridges
> > > > > they spend years taking the foundation down to bedrock with a jackhammer
> > > > > until no evidence of what they accomplished remains.
> > > > It was in the 1990s, less than five years after I left Testra, when I heard John Hart
> > > > (possibly Tom Hart doing an impersonation) say on speaker-phone that I had
> > > > accomplished "nothing" and that I was not eligible for rehire. Presumably Testra had
> > > > been saying this starting immediately after I left Testra but it was a few years later
> > > > when I caught them at this. So, it didn't take Tom Hart long to burn his bridge with me,
> > > > and jackhammer the foundation, to ensure that no evidence of accomplishment remains.
> > > > Tom Hart cares about loyalty! He expects employees to remain employed forever,
> > > > never asking for a raise or health insurance or anything else. Loyalty is a one-way street;
> > > > Tom Hart has no sense of loyalty to his employees and will attack them in public.
> > > >
> > > > Why didn't Testra just tell me when I left that leaving was an act of disloyalty
> > > > and that I would never get a reference? I made a fool out of myself by going to
> > > > job interviews, such as at Lockheed Martin, and saying that I wrote MFX at Testra.
> > > > Most likely, Testra wanted me to go to these job interviews and describe MFX,
> > > > not for my benefit, but just as an advertisement for Testra's MiniForth processor.
> > > > They may have been hoping that Lockheed Martin would buy the MiniForth so
> > > > they could become wealthy, but they had no way to get Lockheed Martin's attention.
> > > > You can't just show up in the lobby of Lockheed Martin and tell the receptionist:
> > > > "Hi! I've got a super-awesome processor! Would you like to buy it?"
> > > > They may have believed (correctly) that for me to go to a job interview at
> > > > Lockheed Martin and describe MFX would be the only way that Lockheed Martin
> > > > would find out about the MiniForth --- but they would pull the rug out from under me
> > > > by telling Lockheed Martin that they wrote MFX --- they would explain to
> > > > Lockheed Martin that they are geniuses who deserve to get rich!
> > > WHAT A MENTAL DESASTER AGAIN.
> > >
> > > Everybody is a liar - which automatically leads to
> > > HUGH AGUILAR IS an AGUILIAR as he is part of everybody.
> > > GO BACK TO YOUR CAGE AND BARK OR NOT.
> > >
> > > Another made up piece of lies - just to make you feel good.
> > >
> > > I did my job at MPE as consultant,
> > > which triggered tmy FORTH BOOKSHELF on amazon
> > > https://www.amazon.co.uk/Juergen-Pintaske/e/B00N8HVEZM%3Fref=dbs_a_mng_rwt_scns_share
> > > I convinced Steve to do the 1802 in FPGA and the FIG-Forth that goees with it on github.
> > > And he did as well the MISC PROCESSOR I HAD INITIATED in FPGA plus a Forth that goes with it.
> > > What have you contributed over the last 30 years
> > > - except of often dayly rants and
> > > accusations of probably everybody here.
> > LIAR LIAR LIAR - YOU ARE DOING WELL.
> > To state that my letter to Testra and the kind answer from there was started without reason
> > is the biggest lie you ever told.
> >
> > You have attacked me over the last 10 years for no real reason
> > - it is all here on CLF so you can check
> > for no real reason.
> > So I wondered what Testra would say about you,
> > and it ended up in the probably most read post of CLF with about 4400 reads now.
> > https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0
> > It will be 4444 soon -
> > You cannot get closer to fours.
> > Have a nice day,
> > and May The Fours Be With You.
> ... and 1444 views here now

On Sunday, 30 April 2023 at 10:41:45 UTC+1, Lorem Ipsum wrote:
> On Sunday, April 30, 2023 at 4:26:49 AM UTC-4, Jurgen Pitaske wrote:
> > On Sunday, 30 April 2023 at 07:22:12 UTC+1, Jurgen Pitaske wrote:
> > > On Sunday, 30 April 2023 at 07:14:16 UTC+1, Jurgen Pitaske wrote:
> > > > On Sunday, 30 April 2023 at 00:34:09 UTC+1, Hugh Aguilar wrote:
> > > > > On Friday, April 28, 2023 at 11:47:36 PM UTC-7, John Hart wrote:
> > > > > > On Friday, April 28, 2023 at 10:41:09 PM UTC-7, Jurgen Pitaske wrote:
> > > > > > > >
> > > > > > > > Why did Testra attack me on comp.lang.forth with lies and insults?
> > > > > > No one from Testra ever attacked anyone on comp.lang.forth
> > > > > > or any other news group ever.
> > > > > Bullshit!
> > > > > This entire thread was an unprovoked attack on me:
> > > > > https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0
> > > > >
> > > > > Tom Hart was totally lying:
> > > > > > I let him go myself,
> > > > > > after I had given him a project to write a DXF converter to HPGL code.
> > > > > > He would not take any direction.
> > > > > > I scrapped the project.
> > > > >
> > > > > I never even heard of HPGL before this attack. There was no HPGL project.
> > > > > Also, I never got any direction in any of my work.
> > > > > When I wrote the DXF to GCODE converter nobody told me about how
> > > > > Bezier Splines might work. I didn't know about Bezier Splines, and I assume
> > > > > that the reason I wasn't told about Bezier Splines is that Tom and John Hart
> > > > > don't know about them either. Tom Hart would just angrily tell me:
> > > > > "Just make a smooth line through all the tiny line segments!"
> > > > > There was just a mish-mash of tiny line segments ranging from 1/1000 of an inch
> > > > > to 20/1000 of an inch, and some longer. They pointed in every which direction. Some
> > > > > weren't touching any other line segment and some touched other line segments.
> > > > > I had no idea how to make a smooth line through this mess. I wished that I did
> > > > > have some direction, but I never did. I wished that I had mind-reading ability
> > > > > so that I could know what image the artist had intended with this mish-mash.
> > > > > Tom Hart says that I'm too stupid to write a data-conversion program.
> > > > > This isn't true. I was converting DXF code to GCODE within a couple of weeks
> > > > > of starting the project. The problem was that the result was a mess.
> > > > > When I started the project I was told that this was a simple data-conversion
> > > > > program, so I felt confident that I could finish in a few weeks. If I had been told
> > > > > that I had to make a smooth line through a big mess of tiny line-segments,
> > > > > I would have refused the job. If I had been told that I needed Bezier Splines
> > > > > I would have refused the job because I don't know anything about the subject.
> > > > > (This is where the comp.lang.forth trolls can spring into action and say that
> > > > > they could easily implement Bezier Splines, so they get to be big internet experts
> > > > > without writing any code, as usual).
> > > > >
> > > > > Tom Hart was totally lying:
> > > > > > [Hugh] had nothing to do with the processor itself,
> > > > > > that was all designed by John Hart and Steve Brault.
> > > > > >
> > > > > > The PLD version was based upon our original Forth Engine done long before
> > > > > > we ever ran across Hugh.
> > > > > The original Forth Engine was a bit-slice processor.
> > > > > This is unrelated to the MiniForth that was a VLIW processor.
> > > > > Tom Hart is saying that MFX was written for the bit-slice processor and then
> > > > > was used on the MiniForth. Bullshit! I wrote MFX for the MiniForth (MFX means
> > > > > Mini Forth Xcompiler). I never saw any of the code from the original Forth Engine.
> > > > > All of that was written by John Perona who later wrote Multi-Edit.. Even if there
> > > > > had been some similarity between the original Forth Engine and the MiniForth,
> > > > > I still wouldn't have looked at John Perona's code because I never look at other
> > > > > people's code (that is like peering through a bedroom window to look at your
> > > > > neighbor's wife). Also, as a practical matter John Perona is a typical C programmer
> > > > > who writes multi-page functions. He doesn't factor code at all.
> > > > >
> > > > > Testra was originally called Hartronics and they advertised their "Forth Engine"
> > > > > in Forth Dimensions, in case anybody cares (I don't).
> > > > >
> > > > > It was obvious that Juergen Pintaske wanted to denounce me on comp.lang.forth,
> > > > > by saying that I am lying about writing MFX at Testra. Tom Hart totally complied by
> > > > > providing Juergen Pintaske with support for this attack. All of Juergen Pintaske's
> > > > > attacks on me over the last four years have been based on him obtaining 100%
> > > > > support from Tom Hart.
> > > > > It is very disingenuous for John Hart to now say:
> > > > > > No one from Testra ever attacked anyone on comp.lang.forth
> > > > > > or any other news group ever.
> > > > > Bullshit! You could have ignored Juergen Pintaske. Everybody else in the world does!
> > > > > Instead you provided Juergen Pintaske with 100% support for attacking me.
> > > > > Juergen Pintaske is now Testra's mouthpiece, and he has Tom Hart's support in this.
> > > > > > Not referring to anyone specific, some people not only burn their bridges
> > > > > > they spend years taking the foundation down to bedrock with a jackhammer
> > > > > > until no evidence of what they accomplished remains.
> > > > > It was in the 1990s, less than five years after I left Testra, when I heard John Hart
> > > > > (possibly Tom Hart doing an impersonation) say on speaker-phone that I had
> > > > > accomplished "nothing" and that I was not eligible for rehire. Presumably Testra had
> > > > > been saying this starting immediately after I left Testra but it was a few years later
> > > > > when I caught them at this. So, it didn't take Tom Hart long to burn his bridge with me,
> > > > > and jackhammer the foundation, to ensure that no evidence of accomplishment remains.
> > > > > Tom Hart cares about loyalty! He expects employees to remain employed forever,
> > > > > never asking for a raise or health insurance or anything else. Loyalty is a one-way street;
> > > > > Tom Hart has no sense of loyalty to his employees and will attack them in public.
> > > > >
> > > > > Why didn't Testra just tell me when I left that leaving was an act of disloyalty
> > > > > and that I would never get a reference? I made a fool out of myself by going to
> > > > > job interviews, such as at Lockheed Martin, and saying that I wrote MFX at Testra.
> > > > > Most likely, Testra wanted me to go to these job interviews and describe MFX,
> > > > > not for my benefit, but just as an advertisement for Testra's MiniForth processor.
> > > > > They may have been hoping that Lockheed Martin would buy the MiniForth so
> > > > > they could become wealthy, but they had no way to get Lockheed Martin's attention.
> > > > > You can't just show up in the lobby of Lockheed Martin and tell the receptionist:
> > > > > "Hi! I've got a super-awesome processor! Would you like to buy it?"
> > > > > They may have believed (correctly) that for me to go to a job interview at
> > > > > Lockheed Martin and describe MFX would be the only way that Lockheed Martin
> > > > > would find out about the MiniForth --- but they would pull the rug out from under me
> > > > > by telling Lockheed Martin that they wrote MFX --- they would explain to
> > > > > Lockheed Martin that they are geniuses who deserve to get rich!
> > > > WHAT A MENTAL DESASTER AGAIN.
> > > >
> > > > Everybody is a liar - which automatically leads to
> > > > HUGH AGUILAR IS an AGUILIAR as he is part of everybody.
> > > > GO BACK TO YOUR CAGE AND BARK OR NOT.
> > > >
> > > > Another made up piece of lies - just to make you feel good.
> > > >
> > > > I did my job at MPE as consultant,
> > > > which triggered tmy FORTH BOOKSHELF on amazon
> > > > https://www.amazon.co.uk/Juergen-Pintaske/e/B00N8HVEZM%3Fref=dbs_a_mng_rwt_scns_share
> > > > I convinced Steve to do the 1802 in FPGA and the FIG-Forth that goees with it on github.
> > > > And he did as well the MISC PROCESSOR I HAD INITIATED in FPGA plus a Forth that goes with it.
> > > > What have you contributed over the last 30 years
> > > > - except of often dayly rants and
> > > > accusations of probably everybody here.
> > > LIAR LIAR LIAR - YOU ARE DOING WELL.
> > > To state that my letter to Testra and the kind answer from there was started without reason
> > > is the biggest lie you ever told.
> > >
> > > You have attacked me over the last 10 years for no real reason
> > > - it is all here on CLF so you can check
> > > for no real reason.
> > > So I wondered what Testra would say about you,
> > > and it ended up in the probably most read post of CLF with about 4400 reads now.
> > > https://groups.google.com/g/comp.lang.forth/c/wydQr643gX0
> > > It will be 4444 soon -
> > > You cannot get closer to fours.
> > > Have a nice day,
> > > and May The Fours Be With You.
> > ... and 1444 views here now
>
> This is without a doubt, the weirdest group I've ever seen.
>
> --
>
> Rick C.
>
> -++- Get 1,000 miles of free Supercharging
> -++- Tesla referral code - https://ts.la/richard11209

On 30/04/2023 11:52 pm, Jurgen Pitaske wrote:
> On Sunday, 30 April 2023 at 10:41:45 UTC+1, Lorem Ipsum wrote:
>
>> This is without a doubt, the weirdest group I've ever seen.
>>
>> --
>>
>> Rick C.
>>
>> -++- Get 1,000 miles of free Supercharging
>> -++- Tesla referral code - https://ts.la/richard11209
>
> And you are a much contributing member

LOL. The devil knows his own even when they don't.

On Monday, 1 May 2023 at 02:46:01 UTC+1, dxforth wrote:
> On 30/04/2023 11:52 pm, Jurgen Pitaske wrote:
> > On Sunday, 30 April 2023 at 10:41:45 UTC+1, Lorem Ipsum wrote:
> >
> >> This is without a doubt, the weirdest group I've ever seen.
> >>
> >> --
> >>
> >> Rick C.
> >>
> >> -++- Get 1,000 miles of free Supercharging
> >> -++- Tesla referral code - https://ts.la/richard11209
> >
> > And you are a much contributing member
> LOL. The devil knows his own even when they don't.
you forgot to give us the link, but google helps
https://www.biblegateway.com/verse/en/Revelation%2012%3A12