ken9

I am Interested in new friends, and possibly a long - term with a Mutually compatible female. I value Reliability and Dependability, Trustworthiness.

(1) I want to make my relevant position clear to minimize wasting time in working at cross purposes.

(a) I am interested in new friends and possibly a long term with a mutually compatible female.

(b) I am not interested in any marriage or cohabitation.

(c) You need your own money.

(d) I will not financially support anyone, nor pay for any free meal tickets for any freeloader moochers, nor sponsor anyone for any immigration.

(2) If you still want to meet in person, then only it makes logical (and reasonable) sense to proceed further.

(3) I prefer Not to waste hundreds of hours of each other's time in trading multiple text messages back and forth. Talking beats typing for me.

(4) I suggest that we first talk on the phone (via a mutually convenient appointment) to determine if there is continued mutual interest, that even warrants- necessitates an in-person meeting (at a mutually convenient rendezvous).

(5) Connotations of "long-term relationship" (SIC) AT THE OUTSET, have been known to be followed by theatrical- drama, bickering- acrimony, and controlling the other individual (interpersonal power dynamics). I do NOT need ANY such aggravation from another entity.

(a) Analogy - It appears to mimic the paradigm shift, as in (approximately) 1995, when event-driven programming (Visual Basic) and object-oriented software development (OOAD) became the norm (with the superficial "point and click") over the traditional mainframe-based (with the superficial "type - away") software development (the earlier Cobol, Prolog, C).

(b) technology .... event-driven-programming. .... : "

- (i) Event-driven programming is a programming paradigm in which the flow of program execution is determined by events - for example a user action such as a mouse click, key press, or a message from the operating system or another program. An event-driven application is designed to detect events as they occur, and then deal with them using an appropriate event-handling procedure. The idea is an extension of interrupt-driven programming of the kind found in early command-line environments such as DOS, and in embedded systems (where the application is implemented as firmware).'' (SIC).

- (ii) " In a typical modern event-driven program, there is no discernible flow of control. The main routine is an event-loop that waits for an event to occur, and then invokes the appropriate event-handling routine. Since the code for this event loop is usually provided by the event-driven development environment or framework, and largely invisible to the programmer, the programmer’s perception of the application is that of a collection of event handling routines. Programmers used to working with procedural programming languages sometimes find that the transition to an event-driven environment requires a CONSIDERABLE MENTAL ADJUSTMENT ." (SIC).