"We elected right-wing parties who are against sane wages and unions and often use/exploit immigrants to depress wages while funneling billions into companies and away from infrastructure projects. So we decided to elect an even more right-wing party to blame immigrants while doing even more funneling away. It will definitely solve all the infrastructure problems that those penniless brown people and weird speaking ones caused."
What is the issue with receiving tickets as PDF? It is the most flexible yet digital option. PDFs work regardless of the medium. You can show it in the phone or you can always add them to DB Navigator App anyways or if you would like to be old school, just print them.
NFC is limited access for phones. You need to pay Google and Apple tax. Android does allow independent communication but it is not widespread and you'll lose a big chunk of Apple users. You basically tie yourself to a platform that way.
You can scan and add your QRs (or more correctly Aztec barcodes) in DB Navigator app already. If you bought it via your own account (instead of your company buying it), you don't even need to do it. The tickets automatically appear.
DB Navigator is one of the best transport apps and already implements some caching. However you're ultimately tied to cell network or WiFi in train for certain othet apps and the quality of implementation. PDFs don't expire.
You still have to unroll the circle from the anchor point, so once you have the circle to start with, you may as well finish there. A half-circle is more visually intuitive than a half-interval
And if you want to go farther back, even if it wasn't called "mmap" or a specific function you had to invoke -- there were operating systems that used a "single-level store" (notably MULTICS and IBM's AS/400..err OS/400... err i5 OS... err today IBM i [seriously, IBM, pick a name and stick with it]) where the interface to disk storage on the platform is that the entire disk storage/filesystem is always mapped into the same address space as the rest of your process's memory. Memory-mapped files were basically the only interface there was, and the operating system "magically" persisted certain areas of your memory to permanent storage.
I guess the author didn't use that many other programming languages or OSes. You can do the same even in garbage collected languages like Java and C# and on Windows too.
I'd be careful though, as they all have quirks due to how tricky it is handling mmap faults. The Java API mentions both unique garbage collection behavior and throwing unspecified exceptions at unspecified times.
reply