#hp200lx — Public Fediverse posts

Thinking I will do this year's #adventOfCode in #muLISP on HP #200LX for initial style points, then in #SBCL on modern desktop for later problems that require substantial grunt.

#HP200LX

Thinking I will do this year's #adventOfCode in #muLISP on HP #200LX for initial style points, then in #SBCL on modern desktop for later problems that require substantial grunt.

#HP200LX

Thinking I will do this year's #adventOfCode in #muLISP on HP #200LX for initial style points, then in #SBCL on modern desktop for later problems that require substantial grunt.

#HP200LX

Thinking I will do this year's #adventOfCode in #muLISP on HP #200LX for initial style points, then in #SBCL on modern desktop for later problems that require substantial grunt.

#HP200LX

Thinking I will do this year's #adventOfCode in #muLISP on HP #200LX for initial style points, then in #SBCL on modern desktop for later problems that require substantial grunt.

#HP200LX

I’m making a video series where I solve 2025 Advent of Code problems on different devices. Watch me solve Day 3 on the HP 200LX, a DOS palmtop from 1994! https://youtu.be/afK5AkqlkfQ #adventofcode #hp200lx #dos #retrocomputing

I’m making a video series where I solve 2025 Advent of Code problems on different devices. Watch me solve Day 3 on the HP 200LX, a DOS palmtop from 1994! https://youtu.be/afK5AkqlkfQ #adventofcode #hp200lx #dos #retrocomputing

I’m making a video series where I solve 2025 Advent of Code problems on different devices. Watch me solve Day 3 on the HP 200LX, a DOS palmtop from 1994! https://youtu.be/afK5AkqlkfQ #adventofcode #hp200lx #dos #retrocomputing

I’m making a video series where I solve 2025 Advent of Code problems on different devices. Watch me solve Day 3 on the HP 200LX, a DOS palmtop from 1994! https://youtu.be/afK5AkqlkfQ #adventofcode #hp200lx #dos #retrocomputing

I’m making a video series where I solve 2025 Advent of Code problems on different devices. Watch me solve Day 3 on the HP 200LX, a DOS palmtop from 1994! https://youtu.be/afK5AkqlkfQ #adventofcode #hp200lx #dos #retrocomputing

@stonetoolsblog Your #AppleWorks and #Hypercard posts, and to a lesser extent the #dBase and #VisualBasic posts, are giving me a bit of a brainwave... could it be that the recipe for a retro sleeper hit is to glue just a bit of automation onto a flat file #database?

Earlier I wrote about owners of the HP #200LX performing daring feats of automation using only the machine's ROM applications (word processor, spreadsheet, database) and a system macro recorder. Their workflows strongly remind me of the workflow you devised for laying out your text adventure game in AppleWorks. Then, HyperCard took things a step further by adding a scripting language and graphics. All these tools feel like members of the same category, with the #HP200LX perhaps the least capable (but most approachable), and HyperCard the most capable (but requiring the most programming to unlock its power).

VB departs from the category by neglecting to ship a built-in database, as you mentioned. dBase departs from the category (subjectively) by being CLI-focused and stodgy enough that it doesn't provide the feeling of sculpting a living medium with one's hands.

I'm obsessed with the category, whatever name one might choose to attach to it. (RAD? Too code-focused. Nocode? Has become its own thing bearing little resemblance to the progenitors.) Regardless, flat-file databases seem to be a sweet spot, simple enough to be readily grasped regardless of technical background but powerful enough to get work done.

@stonetoolsblog Your #AppleWorks and #Hypercard posts, and to a lesser extent the #dBase and #VisualBasic posts, are giving me a bit of a brainwave... could it be that the recipe for a retro sleeper hit is to glue just a bit of automation onto a flat file #database?

Earlier I wrote about owners of the HP #200LX performing daring feats of automation using only the machine's ROM applications (word processor, spreadsheet, database) and a system macro recorder. Their workflows strongly remind me of the workflow you devised for laying out your text adventure game in AppleWorks. Then, HyperCard took things a step further by adding a scripting language and graphics. All these tools feel like members of the same category, with the #HP200LX perhaps the least capable (but most approachable), and HyperCard the most capable (but requiring the most programming to unlock its power).

VB departs from the category by neglecting to ship a built-in database, as you mentioned. dBase departs from the category (subjectively) by being CLI-focused and stodgy enough that it doesn't provide the feeling of sculpting a living medium with one's hands.

I'm obsessed with the category, whatever name one might choose to attach to it. (RAD? Too code-focused. Nocode? Has become its own thing bearing little resemblance to the progenitors.) Regardless, flat-file databases seem to be a sweet spot, simple enough to be readily grasped regardless of technical background but powerful enough to get work done.

@stonetoolsblog Your #AppleWorks and #Hypercard posts, and to a lesser extent the #dBase and #VisualBasic posts, are giving me a bit of a brainwave... could it be that the recipe for a retro sleeper hit is to glue just a bit of automation onto a flat file #database?

Earlier I wrote about owners of the HP #200LX performing daring feats of automation using only the machine's ROM applications (word processor, spreadsheet, database) and a system macro recorder. Their workflows strongly remind me of the workflow you devised for laying out your text adventure game in AppleWorks. Then, HyperCard took things a step further by adding a scripting language and graphics. All these tools feel like members of the same category, with the #HP200LX perhaps the least capable (but most approachable), and HyperCard the most capable (but requiring the most programming to unlock its power).

VB departs from the category by neglecting to ship a built-in database, as you mentioned. dBase departs from the category (subjectively) by being CLI-focused and stodgy enough that it doesn't provide the feeling of sculpting a living medium with one's hands.

I'm obsessed with the category, whatever name one might choose to attach to it. (RAD? Too code-focused. Nocode? Has become its own thing bearing little resemblance to the progenitors.) Regardless, flat-file databases seem to be a sweet spot, simple enough to be readily grasped regardless of technical background but powerful enough to get work done.

@stonetoolsblog Your #AppleWorks and #Hypercard posts, and to a lesser extent the #dBase and #VisualBasic posts, are giving me a bit of a brainwave... could it be that the recipe for a retro sleeper hit is to glue just a bit of automation onto a flat file #database?

Earlier I wrote about owners of the HP #200LX performing daring feats of automation using only the machine's ROM applications (word processor, spreadsheet, database) and a system macro recorder. Their workflows strongly remind me of the workflow you devised for laying out your text adventure game in AppleWorks. Then, HyperCard took things a step further by adding a scripting language and graphics. All these tools feel like members of the same category, with the #HP200LX perhaps the least capable (but most approachable), and HyperCard the most capable (but requiring the most programming to unlock its power).

VB departs from the category by neglecting to ship a built-in database, as you mentioned. dBase departs from the category (subjectively) by being CLI-focused and stodgy enough that it doesn't provide the feeling of sculpting a living medium with one's hands.

I'm obsessed with the category, whatever name one might choose to attach to it. (RAD? Too code-focused. Nocode? Has become its own thing bearing little resemblance to the progenitors.) Regardless, flat-file databases seem to be a sweet spot, simple enough to be readily grasped regardless of technical background but powerful enough to get work done.

@stonetoolsblog Your #AppleWorks and #Hypercard posts, and to a lesser extent the #dBase and #VisualBasic posts, are giving me a bit of a brainwave... could it be that the recipe for a retro sleeper hit is to glue just a bit of automation onto a flat file #database?

Earlier I wrote about owners of the HP #200LX performing daring feats of automation using only the machine's ROM applications (word processor, spreadsheet, database) and a system macro recorder. Their workflows strongly remind me of the workflow you devised for laying out your text adventure game in AppleWorks. Then, HyperCard took things a step further by adding a scripting language and graphics. All these tools feel like members of the same category, with the #HP200LX perhaps the least capable (but most approachable), and HyperCard the most capable (but requiring the most programming to unlock its power).

VB departs from the category by neglecting to ship a built-in database, as you mentioned. dBase departs from the category (subjectively) by being CLI-focused and stodgy enough that it doesn't provide the feeling of sculpting a living medium with one's hands.

I'm obsessed with the category, whatever name one might choose to attach to it. (RAD? Too code-focused. Nocode? Has become its own thing bearing little resemblance to the progenitors.) Regardless, flat-file databases seem to be a sweet spot, simple enough to be readily grasped regardless of technical background but powerful enough to get work done.

Separated at birth: The HP #200LX NoteTaker application, and Microsoft Cardfile from Windows 3.11 (and earlier).

• Simulates a stack of index cards.
• Each note has an index line.
• Notes are auto alphabetized by index. No other sort order is possible.

Cardfile has separate card and index views. NoteTaker shows both at once.

This is the simplest class of application that I believe is justified in calling itself a #database.

#HP200LX #retrocomputing

Separated at birth: The HP #200LX NoteTaker application, and Microsoft Cardfile from Windows 3.11 (and earlier).

• Simulates a stack of index cards.
• Each note has an index line.
• Notes are auto alphabetized by index. No other sort order is possible.

Cardfile has separate card and index views. NoteTaker shows both at once.

This is the simplest class of application that I believe is justified in calling itself a #database.

#HP200LX #retrocomputing

Separated at birth: The HP #200LX NoteTaker application, and Microsoft Cardfile from Windows 3.11 (and earlier).

• Simulates a stack of index cards.
• Each note has an index line.
• Notes are auto alphabetized by index. No other sort order is possible.

Cardfile has separate card and index views. NoteTaker shows both at once.

This is the simplest class of application that I believe is justified in calling itself a #database.

#HP200LX #retrocomputing

Separated at birth: The HP #200LX NoteTaker application, and Microsoft Cardfile from Windows 3.11 (and earlier).

• Simulates a stack of index cards.
• Each note has an index line.
• Notes are auto alphabetized by index. No other sort order is possible.

Cardfile has separate card and index views. NoteTaker shows both at once.

This is the simplest class of application that I believe is justified in calling itself a #database.

#HP200LX #retrocomputing

Separated at birth: The HP #200LX NoteTaker application, and Microsoft Cardfile from Windows 3.11 (and earlier).

• Simulates a stack of index cards.
• Each note has an index line.
• Notes are auto alphabetized by index. No other sort order is possible.

Cardfile has separate card and index views. NoteTaker shows both at once.

This is the simplest class of application that I believe is justified in calling itself a #database.

#HP200LX #retrocomputing

@flyingsaceur MS-DOS 5.0 in ROM in a HP #200LX on a sunny park bench.

#hp200lx

@flyingsaceur MS-DOS 5.0 in ROM in a HP #200LX on a sunny park bench.

#hp200lx

@flyingsaceur MS-DOS 5.0 in ROM in a HP #200LX on a sunny park bench.

#hp200lx

@flyingsaceur MS-DOS 5.0 in ROM in a HP #200LX on a sunny park bench.

#hp200lx

@flyingsaceur MS-DOS 5.0 in ROM in a HP #200LX on a sunny park bench.

#hp200lx

I'm reading a book about French mountain-climbers and the HP #200LX is doing a good job maintaining a cast of characters for me thanks to its NoteTaker application, which is just a thin wrapper around the flat file #database engine shared by most of its PIM apps. The database features both quick browsing by note title (in left-hand column) and a full-text search of all note contents (slower but sometimes necessary to recall a nickname or other trivia).

This is a very basic example of how a flatfile database can frequently be the "right tool for the job" in a way that is now underappreciated:

• Plain text would work, but it's a lot of vertical scrolling, and doesn't have any equivalent of "quick browsing by note title".
• A hierarchical organizer would work well but will suffer the same search problems as plain text unless thoughtfully designed.
• A spreadsheet would need lots of horizontal scrolling to read the character's biographies.

The database is effectively just a "frontend on a spreadsheet" but this is a frontend that does a lot of practical work.

#HP200LX #retrocomputing

I'm reading a book about French mountain-climbers and the HP #200LX is doing a good job maintaining a cast of characters for me thanks to its NoteTaker application, which is just a thin wrapper around the flat file #database engine shared by most of its PIM apps. The database features both quick browsing by note title (in left-hand column) and a full-text search of all note contents (slower but sometimes necessary to recall a nickname or other trivia).

This is a very basic example of how a flatfile database can frequently be the "right tool for the job" in a way that is now underappreciated:

• Plain text would work, but it's a lot of vertical scrolling, and doesn't have any equivalent of "quick browsing by note title".
• A hierarchical organizer would work well but will suffer the same search problems as plain text unless thoughtfully designed.
• A spreadsheet would need lots of horizontal scrolling to read the character's biographies.

The database is effectively just a "frontend on a spreadsheet" but this is a frontend that does a lot of practical work.

#HP200LX #retrocomputing

I'm reading a book about French mountain-climbers and the HP #200LX is doing a good job maintaining a cast of characters for me thanks to its NoteTaker application, which is just a thin wrapper around the flat file #database engine shared by most of its PIM apps. The database features both quick browsing by note title (in left-hand column) and a full-text search of all note contents (slower but sometimes necessary to recall a nickname or other trivia).

This is a very basic example of how a flatfile database can frequently be the "right tool for the job" in a way that is now underappreciated:

• Plain text would work, but it's a lot of vertical scrolling, and doesn't have any equivalent of "quick browsing by note title".
• A hierarchical organizer would work well but will suffer the same search problems as plain text unless thoughtfully designed.
• A spreadsheet would need lots of horizontal scrolling to read the character's biographies.

The database is effectively just a "frontend on a spreadsheet" but this is a frontend that does a lot of practical work.

#HP200LX #retrocomputing

I'm reading a book about French mountain-climbers and the HP #200LX is doing a good job maintaining a cast of characters for me thanks to its NoteTaker application, which is just a thin wrapper around the flat file #database engine shared by most of its PIM apps. The database features both quick browsing by note title (in left-hand column) and a full-text search of all note contents (slower but sometimes necessary to recall a nickname or other trivia).

This is a very basic example of how a flatfile database can frequently be the "right tool for the job" in a way that is now underappreciated:

• Plain text would work, but it's a lot of vertical scrolling, and doesn't have any equivalent of "quick browsing by note title".
• A hierarchical organizer would work well but will suffer the same search problems as plain text unless thoughtfully designed.
• A spreadsheet would need lots of horizontal scrolling to read the character's biographies.

The database is effectively just a "frontend on a spreadsheet" but this is a frontend that does a lot of practical work.

#HP200LX #retrocomputing

I'm reading a book about French mountain-climbers and the HP #200LX is doing a good job maintaining a cast of characters for me thanks to its NoteTaker application, which is just a thin wrapper around the flat file #database engine shared by most of its PIM apps. The database features both quick browsing by note title (in left-hand column) and a full-text search of all note contents (slower but sometimes necessary to recall a nickname or other trivia).

This is a very basic example of how a flatfile database can frequently be the "right tool for the job" in a way that is now underappreciated:

• Plain text would work, but it's a lot of vertical scrolling, and doesn't have any equivalent of "quick browsing by note title".
• A hierarchical organizer would work well but will suffer the same search problems as plain text unless thoughtfully designed.
• A spreadsheet would need lots of horizontal scrolling to read the character's biographies.

The database is effectively just a "frontend on a spreadsheet" but this is a frontend that does a lot of practical work.

#HP200LX #retrocomputing

@interstar I liked your fishing trip database example, so here's a wine database on HP #200LX. Two facing pages in the manual were enough to fully demonstrate how to create it. No need for a LLM helper.

https://archive.org/details/manualsbase-id-189652/page/n89/mode/2up

#retrocomputing #hp200lx

@interstar I liked your fishing trip database example, so here's a wine database on HP #200LX. Two facing pages in the manual were enough to fully demonstrate how to create it. No need for a LLM helper.

https://archive.org/details/manualsbase-id-189652/page/n89/mode/2up

#retrocomputing #hp200lx

@interstar I liked your fishing trip database example, so here's a wine database on HP #200LX. Two facing pages in the manual were enough to fully demonstrate how to create it. No need for a LLM helper.

https://archive.org/details/manualsbase-id-189652/page/n89/mode/2up

#retrocomputing #hp200lx

@interstar I liked your fishing trip database example, so here's a wine database on HP #200LX. Two facing pages in the manual were enough to fully demonstrate how to create it. No need for a LLM helper.

https://archive.org/details/manualsbase-id-189652/page/n89/mode/2up

#retrocomputing #hp200lx

@interstar I liked your fishing trip database example, so here's a wine database on HP #200LX. Two facing pages in the manual were enough to fully demonstrate how to create it. No need for a LLM helper.

https://archive.org/details/manualsbase-id-189652/page/n89/mode/2up

#retrocomputing #hp200lx

An auto mechanic uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/36/pt360028.htm

Whenever I finish working on a customer's car, I use Calc to total the customer's bill. Then I run a macro that I've created which automatically does a number of things: First, it adds the amount of today's bill to the total cost of all bills in the past (it gets this figure from the MEMO file for that customer). Then the macro takes this new sum and replaces the old "Total cost of Maintenance" in the MEMO file with the new figure. The macro then saves the MEMO file, returns to ApptBook and clears the time from the appointment, saves the appointment, then backs up the file to the flash card. Finally, the macro closes the appointment and moves down to the next appointment for the day. When I open the ApptBook again, it is already highlighted on the next appointment.

(cont'd) 🧵 (8/?)

#hp200lx #retrocomputing

An auto mechanic uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/36/pt360028.htm

Whenever I finish working on a customer's car, I use Calc to total the customer's bill. Then I run a macro that I've created which automatically does a number of things: First, it adds the amount of today's bill to the total cost of all bills in the past (it gets this figure from the MEMO file for that customer). Then the macro takes this new sum and replaces the old "Total cost of Maintenance" in the MEMO file with the new figure. The macro then saves the MEMO file, returns to ApptBook and clears the time from the appointment, saves the appointment, then backs up the file to the flash card. Finally, the macro closes the appointment and moves down to the next appointment for the day. When I open the ApptBook again, it is already highlighted on the next appointment.

(cont'd) 🧵 (8/?)

#hp200lx #retrocomputing

An auto mechanic uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/36/pt360028.htm

Whenever I finish working on a customer's car, I use Calc to total the customer's bill. Then I run a macro that I've created which automatically does a number of things: First, it adds the amount of today's bill to the total cost of all bills in the past (it gets this figure from the MEMO file for that customer). Then the macro takes this new sum and replaces the old "Total cost of Maintenance" in the MEMO file with the new figure. The macro then saves the MEMO file, returns to ApptBook and clears the time from the appointment, saves the appointment, then backs up the file to the flash card. Finally, the macro closes the appointment and moves down to the next appointment for the day. When I open the ApptBook again, it is already highlighted on the next appointment.

(cont'd) 🧵 (8/?)

#hp200lx #retrocomputing

An auto mechanic uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/36/pt360028.htm

Whenever I finish working on a customer's car, I use Calc to total the customer's bill. Then I run a macro that I've created which automatically does a number of things: First, it adds the amount of today's bill to the total cost of all bills in the past (it gets this figure from the MEMO file for that customer). Then the macro takes this new sum and replaces the old "Total cost of Maintenance" in the MEMO file with the new figure. The macro then saves the MEMO file, returns to ApptBook and clears the time from the appointment, saves the appointment, then backs up the file to the flash card. Finally, the macro closes the appointment and moves down to the next appointment for the day. When I open the ApptBook again, it is already highlighted on the next appointment.

(cont'd) 🧵 (8/?)

#hp200lx #retrocomputing

An auto mechanic uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/36/pt360028.htm

Whenever I finish working on a customer's car, I use Calc to total the customer's bill. Then I run a macro that I've created which automatically does a number of things: First, it adds the amount of today's bill to the total cost of all bills in the past (it gets this figure from the MEMO file for that customer). Then the macro takes this new sum and replaces the old "Total cost of Maintenance" in the MEMO file with the new figure. The macro then saves the MEMO file, returns to ApptBook and clears the time from the appointment, saves the appointment, then backs up the file to the flash card. Finally, the macro closes the appointment and moves down to the next appointment for the day. When I open the ApptBook again, it is already highlighted on the next appointment.

(cont'd) 🧵 (8/?)

#hp200lx #retrocomputing

An engineer uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/29/pt290038.htm

In my work I write many letters and memos, create technical drawings and provide estimates on projects. I send and receive many faxes and cc:Mail and compose most of them right on my Palmtop in WordPerfect 5.1. To organize my correspondence I've created an archive database with the built-in Database program shown below. […]

(cont'd) 🧵 (7/?)

#hp200lx #retrocomputing

An engineer uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/29/pt290038.htm

In my work I write many letters and memos, create technical drawings and provide estimates on projects. I send and receive many faxes and cc:Mail and compose most of them right on my Palmtop in WordPerfect 5.1. To organize my correspondence I've created an archive database with the built-in Database program shown below. […]

(cont'd) 🧵 (7/?)

#hp200lx #retrocomputing

An engineer uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/29/pt290038.htm

In my work I write many letters and memos, create technical drawings and provide estimates on projects. I send and receive many faxes and cc:Mail and compose most of them right on my Palmtop in WordPerfect 5.1. To organize my correspondence I've created an archive database with the built-in Database program shown below. […]

(cont'd) 🧵 (7/?)

#hp200lx #retrocomputing

An engineer uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/29/pt290038.htm

In my work I write many letters and memos, create technical drawings and provide estimates on projects. I send and receive many faxes and cc:Mail and compose most of them right on my Palmtop in WordPerfect 5.1. To organize my correspondence I've created an archive database with the built-in Database program shown below. […]

(cont'd) 🧵 (7/?)

#hp200lx #retrocomputing

An engineer uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/29/pt290038.htm

In my work I write many letters and memos, create technical drawings and provide estimates on projects. I send and receive many faxes and cc:Mail and compose most of them right on my Palmtop in WordPerfect 5.1. To organize my correspondence I've created an archive database with the built-in Database program shown below. […]

(cont'd) 🧵 (7/?)

#hp200lx #retrocomputing

A real estate professional uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/25/pt250026.htm

[My] macros work in conjunction with Memo and Appt. to facilitate my follow up and advertising. Each macro enters a To Do item for sending something to a prospect; a follow up letter, a draft lease, a letter of intent, or a brochure, respectively. They also make an entry in a Memo file called LIST.DOC. Each entry shows name, address, property interested in, and type of business. The LIST.DOC file is printed at the end of the day and handed to my secretary. Finally, each macro skips a week from the current day and enters a follow up To Do to remind me keep in touch with the prospect. LIST.DOC is then merged into SENT.DOC so that it is empty for the next day and SENT.DOC archives every mailing I've done for the month.

(cont'd) 🧵 (6/?)

#HP200LX #retrocomputing

A real estate professional uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/25/pt250026.htm

[My] macros work in conjunction with Memo and Appt. to facilitate my follow up and advertising. Each macro enters a To Do item for sending something to a prospect; a follow up letter, a draft lease, a letter of intent, or a brochure, respectively. They also make an entry in a Memo file called LIST.DOC. Each entry shows name, address, property interested in, and type of business. The LIST.DOC file is printed at the end of the day and handed to my secretary. Finally, each macro skips a week from the current day and enters a follow up To Do to remind me keep in touch with the prospect. LIST.DOC is then merged into SENT.DOC so that it is empty for the next day and SENT.DOC archives every mailing I've done for the month.

(cont'd) 🧵 (6/?)

#HP200LX #retrocomputing

A real estate professional uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/25/pt250026.htm

[My] macros work in conjunction with Memo and Appt. to facilitate my follow up and advertising. Each macro enters a To Do item for sending something to a prospect; a follow up letter, a draft lease, a letter of intent, or a brochure, respectively. They also make an entry in a Memo file called LIST.DOC. Each entry shows name, address, property interested in, and type of business. The LIST.DOC file is printed at the end of the day and handed to my secretary. Finally, each macro skips a week from the current day and enters a follow up To Do to remind me keep in touch with the prospect. LIST.DOC is then merged into SENT.DOC so that it is empty for the next day and SENT.DOC archives every mailing I've done for the month.

(cont'd) 🧵 (6/?)

#HP200LX #retrocomputing

A real estate professional uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/25/pt250026.htm

[My] macros work in conjunction with Memo and Appt. to facilitate my follow up and advertising. Each macro enters a To Do item for sending something to a prospect; a follow up letter, a draft lease, a letter of intent, or a brochure, respectively. They also make an entry in a Memo file called LIST.DOC. Each entry shows name, address, property interested in, and type of business. The LIST.DOC file is printed at the end of the day and handed to my secretary. Finally, each macro skips a week from the current day and enters a follow up To Do to remind me keep in touch with the prospect. LIST.DOC is then merged into SENT.DOC so that it is empty for the next day and SENT.DOC archives every mailing I've done for the month.

(cont'd) 🧵 (6/?)

#HP200LX #retrocomputing

A real estate professional uses the HP 200LX in the 1990s

https://www.palmtoppaper.com/ptphtml/25/pt250026.htm

[My] macros work in conjunction with Memo and Appt. to facilitate my follow up and advertising. Each macro enters a To Do item for sending something to a prospect; a follow up letter, a draft lease, a letter of intent, or a brochure, respectively. They also make an entry in a Memo file called LIST.DOC. Each entry shows name, address, property interested in, and type of business. The LIST.DOC file is printed at the end of the day and handed to my secretary. Finally, each macro skips a week from the current day and enters a follow up To Do to remind me keep in touch with the prospect. LIST.DOC is then merged into SENT.DOC so that it is empty for the next day and SENT.DOC archives every mailing I've done for the month.

(cont'd) 🧵 (6/?)

#HP200LX #retrocomputing

Object lessons

In the 1990s, there was a newsletter called “The Palmtop Paper” which was later condensed into a book called “PC in Your Pocket”. One of its recurring themes was success stories of how everyday people used the HP 200LX palmtop computer to organize their work. Realtors used it to track ongoing negotiations, salespeople to digitize their “tickler” files, and doctors to calculate dosages. These were not programmers! Nor, in most cases, were they using specialized software, or were they supported by an IT department! Somehow, all of the use-cases above were handled by a half-dozen applications in ROM.

• A file browser
• A text editor
• A spreadsheet
• A flat-file #database with several pre-configured views (calendar, to-do, phone-book, notes) and the ability to create custom views
• A calculator with numeric solver

And the following cross-application automation features

• A keyboard macro recorder
• A task scheduler that could run a specified program or macro at a given time

Following are a few examples drawn from the Palmtop Paper archives. Bear in mind that these examples were not concocted by career programmers, but by professionals in unrelated fields.

(cont'd) 🧵 (5/?)

#HP200LX #retrocomputing

Object lessons

In the 1990s, there was a newsletter called “The Palmtop Paper” which was later condensed into a book called “PC in Your Pocket”. One of its recurring themes was success stories of how everyday people used the HP 200LX palmtop computer to organize their work. Realtors used it to track ongoing negotiations, salespeople to digitize their “tickler” files, and doctors to calculate dosages. These were not programmers! Nor, in most cases, were they using specialized software, or were they supported by an IT department! Somehow, all of the use-cases above were handled by a half-dozen applications in ROM.

• A file browser
• A text editor
• A spreadsheet
• A flat-file #database with several pre-configured views (calendar, to-do, phone-book, notes) and the ability to create custom views
• A calculator with numeric solver

And the following cross-application automation features

• A keyboard macro recorder
• A task scheduler that could run a specified program or macro at a given time

Following are a few examples drawn from the Palmtop Paper archives. Bear in mind that these examples were not concocted by career programmers, but by professionals in unrelated fields.

(cont'd) 🧵 (5/?)

#HP200LX #retrocomputing

Object lessons

In the 1990s, there was a newsletter called “The Palmtop Paper” which was later condensed into a book called “PC in Your Pocket”. One of its recurring themes was success stories of how everyday people used the HP 200LX palmtop computer to organize their work. Realtors used it to track ongoing negotiations, salespeople to digitize their “tickler” files, and doctors to calculate dosages. These were not programmers! Nor, in most cases, were they using specialized software, or were they supported by an IT department! Somehow, all of the use-cases above were handled by a half-dozen applications in ROM.

• A file browser
• A text editor
• A spreadsheet
• A flat-file #database with several pre-configured views (calendar, to-do, phone-book, notes) and the ability to create custom views
• A calculator with numeric solver

And the following cross-application automation features

• A keyboard macro recorder
• A task scheduler that could run a specified program or macro at a given time

Following are a few examples drawn from the Palmtop Paper archives. Bear in mind that these examples were not concocted by career programmers, but by professionals in unrelated fields.

(cont'd) 🧵 (5/?)

#HP200LX #retrocomputing

Object lessons

In the 1990s, there was a newsletter called “The Palmtop Paper” which was later condensed into a book called “PC in Your Pocket”. One of its recurring themes was success stories of how everyday people used the HP 200LX palmtop computer to organize their work. Realtors used it to track ongoing negotiations, salespeople to digitize their “tickler” files, and doctors to calculate dosages. These were not programmers! Nor, in most cases, were they using specialized software, or were they supported by an IT department! Somehow, all of the use-cases above were handled by a half-dozen applications in ROM.

• A file browser
• A text editor
• A spreadsheet
• A flat-file #database with several pre-configured views (calendar, to-do, phone-book, notes) and the ability to create custom views
• A calculator with numeric solver

And the following cross-application automation features

• A keyboard macro recorder
• A task scheduler that could run a specified program or macro at a given time

Following are a few examples drawn from the Palmtop Paper archives. Bear in mind that these examples were not concocted by career programmers, but by professionals in unrelated fields.

(cont'd) 🧵 (5/?)

#HP200LX #retrocomputing

Object lessons

In the 1990s, there was a newsletter called “The Palmtop Paper” which was later condensed into a book called “PC in Your Pocket”. One of its recurring themes was success stories of how everyday people used the HP 200LX palmtop computer to organize their work. Realtors used it to track ongoing negotiations, salespeople to digitize their “tickler” files, and doctors to calculate dosages. These were not programmers! Nor, in most cases, were they using specialized software, or were they supported by an IT department! Somehow, all of the use-cases above were handled by a half-dozen applications in ROM.

• A file browser
• A text editor
• A spreadsheet
• A flat-file #database with several pre-configured views (calendar, to-do, phone-book, notes) and the ability to create custom views
• A calculator with numeric solver

And the following cross-application automation features

• A keyboard macro recorder
• A task scheduler that could run a specified program or macro at a given time

Following are a few examples drawn from the Palmtop Paper archives. Bear in mind that these examples were not concocted by career programmers, but by professionals in unrelated fields.

(cont'd) 🧵 (5/?)

#HP200LX #retrocomputing

Update: Now I've solved sixteen Project Euler problems in muLISP on the #hp200lx. Sometimes I'm not mathy enough to find a closed-form solution to certain puzzles involving millions of terms. For those I am limited by only having 640KB RAM and 8 MHz processor, and it's necessary to send the program to a desktop (or even my phone!) running SBCL. Even though muLISP is not a Common Lisp, the porting is straightforward. One particular program that would have taken a full 24 hours on the palmtop completed in 0.3 seconds on my desktop.

As a #retrocomputing head I am attracted to the pre-Common Lisp dialects which were in use when Lisp actually experienced its heydey. CL was a good compromise, forward compatible with most of these dialects, but imo lacks the small size and conceptual unity that make a language easy to learn. I've found it easier to learn muLISP and gradually pick up CL features where appropriate when I'm on a modern PC. And I greatly appreciate CL for existing and being as stable as it is.

As much as I admire the purity of Scheme, the fragmentation hurts it a lot. Every implementation has some flaw or another that drives me away.

#lisp

Update: Now I've solved sixteen Project Euler problems in muLISP on the #hp200lx. Sometimes I'm not mathy enough to find a closed-form solution to certain puzzles involving millions of terms. For those I am limited by only having 640KB RAM and 8 MHz processor, and it's necessary to send the program to a desktop (or even my phone!) running SBCL. Even though muLISP is not a Common Lisp, the porting is straightforward. One particular program that would have taken a full 24 hours on the palmtop completed in 0.3 seconds on my desktop.

As a #retrocomputing head I am attracted to the pre-Common Lisp dialects which were in use when Lisp actually experienced its heydey. CL was a good compromise, forward compatible with most of these dialects, but imo lacks the small size and conceptual unity that make a language easy to learn. I've found it easier to learn muLISP and gradually pick up CL features where appropriate when I'm on a modern PC. And I greatly appreciate CL for existing and being as stable as it is.

As much as I admire the purity of Scheme, the fragmentation hurts it a lot. Every implementation has some flaw or another that drives me away.

#lisp

Update: Now I've solved sixteen Project Euler problems in muLISP on the #hp200lx. Sometimes I'm not mathy enough to find a closed-form solution to certain puzzles involving millions of terms. For those I am limited by only having 640KB RAM and 8 MHz processor, and it's necessary to send the program to a desktop (or even my phone!) running SBCL. Even though muLISP is not a Common Lisp, the porting is straightforward. One particular program that would have taken a full 24 hours on the palmtop completed in 0.3 seconds on my desktop.

As a #retrocomputing head I am attracted to the pre-Common Lisp dialects which were in use when Lisp actually experienced its heydey. CL was a good compromise, forward compatible with most of these dialects, but imo lacks the small size and conceptual unity that make a language easy to learn. I've found it easier to learn muLISP and gradually pick up CL features where appropriate when I'm on a modern PC. And I greatly appreciate CL for existing and being as stable as it is.

As much as I admire the purity of Scheme, the fragmentation hurts it a lot. Every implementation has some flaw or another that drives me away.

#lisp

Update: Now I've solved sixteen Project Euler problems in muLISP on the #hp200lx. Sometimes I'm not mathy enough to find a closed-form solution to certain puzzles involving millions of terms. For those I am limited by only having 640KB RAM and 8 MHz processor, and it's necessary to send the program to a desktop (or even my phone!) running SBCL. Even though muLISP is not a Common Lisp, the porting is straightforward. One particular program that would have taken a full 24 hours on the palmtop completed in 0.3 seconds on my desktop.

As a #retrocomputing head I am attracted to the pre-Common Lisp dialects which were in use when Lisp actually experienced its heydey. CL was a good compromise, forward compatible with most of these dialects, but imo lacks the small size and conceptual unity that make a language easy to learn. I've found it easier to learn muLISP and gradually pick up CL features where appropriate when I'm on a modern PC. And I greatly appreciate CL for existing and being as stable as it is.

As much as I admire the purity of Scheme, the fragmentation hurts it a lot. Every implementation has some flaw or another that drives me away.

#lisp

Update: Now I've solved sixteen Project Euler problems in muLISP on the #hp200lx. Sometimes I'm not mathy enough to find a closed-form solution to certain puzzles involving millions of terms. For those I am limited by only having 640KB RAM and 8 MHz processor, and it's necessary to send the program to a desktop (or even my phone!) running SBCL. Even though muLISP is not a Common Lisp, the porting is straightforward. One particular program that would have taken a full 24 hours on the palmtop completed in 0.3 seconds on my desktop.

As a #retrocomputing head I am attracted to the pre-Common Lisp dialects which were in use when Lisp actually experienced its heydey. CL was a good compromise, forward compatible with most of these dialects, but imo lacks the small size and conceptual unity that make a language easy to learn. I've found it easier to learn muLISP and gradually pick up CL features where appropriate when I'm on a modern PC. And I greatly appreciate CL for existing and being as stable as it is.

As much as I admire the purity of Scheme, the fragmentation hurts it a lot. Every implementation has some flaw or another that drives me away.

#lisp