Post AxPwhWFpXqtpL19Qwa by ricci@discuss.systems
 (DIR) More posts by ricci@discuss.systems
 (DIR) Post #AxPwhTlcnBY7cl0HaK by rk@mastodon.well.com
       2025-08-22T03:17:41Z
       
       0 likes, 0 repeats
       
       @petrillic AS/400
       
 (DIR) Post #AxPwhVId5xXoNPS9fU by PeterLudemann@mathstodon.xyz
       2025-08-22T03:54:16Z
       
       0 likes, 0 repeats
       
       @rk @petrillic But the AS/400's main programming language was RPG (the exact opposite of "fit for purpose") and its command language was almost as bad as TSO's (although REXX eventually came along).See also: https://en.wikipedia.org/wiki/IBM_Future_Systems_project
       
 (DIR) Post #AxPwhWFpXqtpL19Qwa by ricci@discuss.systems
       2025-08-22T05:02:08Z
       
       0 likes, 0 repeats
       
       @PeterLudemann @rk @petrillic yo, my first job in high school was writing RPG on the AS/400What a god awful language but I did find the way it treated all files as databases interesting
       
 (DIR) Post #AxQPVa3EV4DSJEuzJo by burnitdown@beige.party
       2025-08-22T10:24:58Z
       
       0 likes, 0 repeats
       
       @ricci @PeterLudemann @rk @petrillic COBOL systems do the same, don't they? things are very different in the land of COBOL.
       
 (DIR) Post #AxQS91OswxO4KjyrNg by PeterLudemann@mathstodon.xyz
       2025-08-22T10:54:31Z
       
       0 likes, 0 repeats
       
       @ricci @rk @petrillic It turns out that a single-level store has performance problems when you're reading through it sequentially, so memory-access hints need to be added to the code. As someone said: "all abstractions leak".On the other hand, it's nice to be able to run SQL queries on flat files, and to treat database files and query results as flat files. (Even though SQL is another awful language)