Digital Revolution

There are two primary models for working with PDF files on the cloud with Apple devices. One is to store PDF files in iCloud Drive and use apps like Preview to access the PDF. Another is to store PDF files in Apple Books and read it directly. Supposedly, the former is more flexible, while the latter is more focused. However, due to implementation issues, both models work awkwardly. First the iCloud Drive model, it's really flexible to use iCloud Drive to store whatever PDF at wherever organization finds suitable. With Preview on the Mac, reading PDF files is really tidy. For example, consider bunch of research papers and books in various folders on iCloud Drive. Classification can be added with Finder. Annotation can be added with Preview. The problem is that Apple didn't ship Preview on the iPad. Viewing PDF files in the Files app on the iPad just sucks. Then the Apple Books model, due to limited organization functionalities, it's best used to store only important PDF file...

It's well-known that the entire Adobe Creative Cloud is made for designers, not coders. Adobe's early foray into business world with coding capabilities started and ended with Flash. Now, it's really hard for coders to work with Adobe, whether it's apps or web. However, the interesting programming model brought about by Flash deserves Adobe's attention, for it's a early designer-coder alliance that inspired HTML5 development. Adobe's focus on designers together with neglect of coders is detrimental to its own ambition in the business world. PDF doesn't scale if there is no enterprise application to back it up. Can Adobe win back the territory once conquered by Flash? Or will Adobe alienate coders to the effect of a near total retreat from the business world?

There was a time when interesting web front-end development was done on the Flash platform. It's a time when multimedia overtook dull static GUI and allowed artistic expressions to prosper. The end of Flash transformed a designer-centric GUI development culture into a collaborative HTML5 designer-coder relationship. For all its flaws, there is still no modern design tool as easy and expressive as Flash. Adobe didn't place much emphasis on Dreamweaver as a front-end development tool. JavaScript frameworks are coders' heaven and designers' bane. It's wise to speculate that the Flash development model also ended with the demise of Flash, for at least one reason: responsive web design. Flash was designed for fixed dimensions. When the multi-screen reality became clear around 2010, Adobe didn't upgrade Flash to address the challenge, but gave way to HTML5 responsive web design. Responsive web design allowed content to be specifically rendered according to user'...

Ebooks failed. Critics of ebook cite various reasons, including prices and the love for paper books, to explain why ebooks failed. While there is truth in these critiques, one can not but ask why ebooks failed to take off while research papers in electronic form became dominant. Although there is more to research publications that the digital revolution should promise, the raw digitization of papers already shows great advantage against printed papers. Digital copies are vastly easier to distribute, organize, and index. Web sites like arXiv are extremely popular for people to find papers. One reason is that ebooks are often technologically backward compared with the layout of printed content. Although Apple managed to revolutionize the ergonomics of reading through the iPad, the aesthetics didn't extend to Apple Books. It's worth noting that many beautiful interactive ebooks are published as apps, rather than ebooks, which demonstrates the versatility of the tablet platform...

Advantages of paperless office are numerous. Businesses may maintain digital operation records much more complete than paper-based workflow. Mobile work can be instantly issued without cumbersome mails and fax. Workplace automation improves business efficiency. Recently, due to pandemic, Work From Home (WFH) also proved the flexibility and resilience of paperless office. Many paperless office workflows build on Adobe Acrobat. PDF documents resemble printed forms may be digitally filled and signed. The disadvantage is that bulk operations on bunch of PDF documents tend to be difficult. Another solution is provided by custom ERP. ERP employs databases that can be easily programmed. Bulk operations and automation can be straightforwardly accomplished. The disadvantage is that ERP tends to be costly and poses portability problems. Perhaps ERP that automatically generates PDF documents for exchange may provide some progress.