Path dependency failure is something i do wonder about (are enough kids learning low level assembly and ttl in schoo for example) and @Jonathan_Blow did a great talk about ithttps://www.youtube.com/watch?v=pW-SOdj4Kkk …
-
about it enough to be really sure. That said I feel like "the filesystem" is probably the problem. I am not sure why there should be a "the filesystem" as opposed to whatever filesystems applications maintain with user-level code (there is an overall disk space allocation
problem, but that is the kind of thing that would be in per-application permissions anyway -- how much disk is this program allowed to use?) This means programs are siloed off from each other's files and probably most system files, but this is what we want for security anyway.
-
-
(Well you also have to schedule, but I feel like by the time you get down to scheduling raw reads/writes, that is simple enough for the device to do without a kernel in the way).
-
And they already _do_ schedule them... all drives now have complicated controllers with caching on them, so it's not like the OS is doing the heavy lifting - the _drive_ is doing the heavy lifting.
-
Reinventing OS is one side of the story. But isn't the gaming targeted part like a small bootloader with an unikernel, with access to HDD, GPU and raw CPU (+threading & networking eventually). Like the Amiga OS in
@cmuratori talk? Boot into a game -
Many PC gamers are accustomed to running web browsers along side their games in another monitor for twitching viewing as an example. So that would work for the enthusiasts but the more general and more common scenario puts us back in the resource sharing problem again
-
But then we gain nothing. Isn't this why we have tablets, phones and the laptop etc. Plus: It's not like you can browse next to gaming on console either or back in the days in DOS. I'd say the enthusiasts are the target, else you don't need raw performance anyway IMHO
-
People can make it work by changing their behavior but people generally do not like that even if it's in their best interests. Make the path of least resistance the right and obvious path.
End of conversation
New conversation -
-
-
What do you think about using a different file format in which the application states how memory, RAM and maybe CPU time it would like to have and has fixed locations in memory, where the OS would write how much of each it can provide?
-
I meant a different file format instead of the .exe format.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.