3 ms·
> Sure the old terminal apps were crude bug god they were fast, processing AND ergonomy. The old terminal apps are mostly designed to run in batches, and it's
by mschuster91 9y ago
> Sure the old terminal apps were crude bug god they were fast, processing AND ergonomy.
The old terminal apps are mostly designed to run in batches, and it's horrifically difficult to implement (secure!) interfaces to any modern systems - which is expected from a government these days. There's a reason why many banks still don't offer instant payments in 2017 - not just because a tiny profit can be made by holding the money for a day, but also because the mainframe based batch processing stuff is not able to do realtime.
And to make stuff worse: many of these terminal apps have severe issues. They don't accept UTF8 (some only ANSI!), leading to data loss when you have customers/citizens with uncommon characters in their names - while e.g. a German system will often accept the Umlauts, it will struggle with French or Slavic diacritics and completely fail at Cyrillic or Japanese. Or they're hardcoded for example to encode gender as bool (0=male, 1=female), which breaks with intersexual people, or that a marriage may be between homosexual people (because the data fields are named as husband / wife)...
Sure, the same issues plague web-apps or native desktop apps too, but for these you can at least hire decent programmers pretty much anywhere while you will spend enormous amounts of money for mainframe experts.