So there is no technical limitation of HTML itself compared to XML (doc format)? That HTML would be a just as good replacement for XML (.doc format) if someone tried to make a word processor for it?
I meant if someone were to create a word processor in 2018, with the least amount of work, shouldn't they use HTML as the format of the document? Assuming no need to backwards compatibility with any other doc formats.
I think the issue will be that either your Mac will be unsupported for OSX Mojave or at most in an year or so while your machine physically will still be in good working condition.
Because in the space of open source operating systems, we realistically only have Linux Kernel.
With each new release of Linux kernel, the internal kernel interfaces that device drivers use, change. So whatever binary kernel driver the vendor released with kernel version x is not going to run with next kernel version y.
You only have 2 options:
1. Either you get the source of device drivers, which the vendors don't release because they want to protect their hardware IP
2. or the kernel keeps its interfaces stable so that drivers released can be reused again.
Right now, both are not happening and that is the real reason Android phones have a life of at most 2 years.
I think the idea of dumber phone introduces with it another notion, since the phone is seen more as a utilitarian tool(not for entertainment), then it should not have to be replaced frequently.
With the above concept the entire discussion then hinges on how updatable the phone software is? Because if the phone software is not updatable, even the minimum number of apps needed on the phone will stagnate and you'll have to buy a new phone anyhow.
The single biggest point of failure in the updatability of a phone is the devices drivers for the SOC. Linux fails in this regard because the driver ABI is not stable, so you can't run drivers that the vendor launched with the launch kernel. It is this problem of updatable drivers for SOC components that needs to be solved before any idea of a long lasting utility phone becomes practical.
Look into commoncrawl.org which provides a free web index which you can query against. Now that cloud is available, you could in theory download the index and load it into Google's big query or AWS and run your experiments.
This looks like a problem to be solved with something like a google search engine for all internal pages and wiki.
Perhaps we should start machine learning to start auto tagging discussions in Slack with the context they're being done in and then expose a search engine like interface to all of Slack conversations, wikis etc.