News for hackers. Stuff that matters.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by strictfp on Friday May 03, 2019 @12:44PM (#19819972)
One idea I've been throwing around is to replace files with HTTP resources; everything is a resource. Effectively Plan9s idea, but the time might be right.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by worble on Friday May 03, 2019 @12:52PM (#19820051)
I don't know much about the OS and designs, but is that similar to how Redox is approaching it with "everything is a url"[0]?

[0]https://doc.redox-os.org/book/design/urls_schemes_resources....

Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by PeterCorless on Friday May 03, 2019 @03:30PM (#19821492)
If you go that route, bind unique objects to Uniform Resource Names (URN), and then have a mapping to instantiations (URLs), so that the same resource can be found in its multiple locations. Would help immeasurably for a distribution model.
Re:I/O Is Faster Than CPU – Let’s Partition Resources and El... by BGyss on Friday May 03, 2019 @01:03PM (#19820140)
Believe it or not there was a system at Sony Pictures Imageworks that worked like this - no idea what it was doing under the hood though. Worked great in practice though - every possible production resource was a URL that started with spref:// iirc.