How would you design a (future-proof) OS?

​

There is only one OS and linux is its kernel
Takbir

>>2
Allahu akbar

I would debug an existing OS first, and then debug the architecture itself

There already is one. It's called Plan 9

>>5
Plan 9 is a meme OS and has no future, no present, no past.

>>6
But it's still in use.....

What I like the most about modern OS usability:
1. Autoplaying videos: you open a news site to read a text article about gold prices, and it starts playing some video about soccer or Putin in the corner.
2. Auto-updates, anti-viruses, auto-backups, indexing, garbage collection, cache flushing, runtime optimization/pre-compilation, and all that wonderful stuff happening in background, when you're trying to play a video game or do the work in Photoshop.
3. Myriad of ways to configure your OS. In Windows 10 we already have setting, control panel, regedit, msconfig, services.msc, and a lot more. Linux even manages to beat Windows 10 on that.
4. Basic functionality implemented in Python or Visual Basic, so a menu takes several seconds to pop-up in on a high end machines, while large data sets can easily eat up several gigabytes of memory, like the case with Linux package manager written in Python, which crashes with out of memory, when there are too many packages.

>>8

5. Sending your private info back to Microsoft, Google or Redhat, so they could sell it to interested parties, or just datamine it themselves.

>>8
What does the first one have to do with the OS?

>>4
Would that make it future-proof?

>>11
yes if I disable updates themselves

>>9
Redhat doesn't do that though

>>13

How do you know?

>>14
Because there's no evidence that they do

>>15
Why wouldn't a military contractor collect usage data on its product?

>>16
That's not hard evidence.

>>15
Not that I'm taking sides here, but absence of evidence isn't evidence of absence

>>18
Ok but his claim is baseless

Terry Davis already has.