Comment Re:Sounds like a good problem to have (Score 1) 129
Colour Classic...yeah maybe, and again as a retro machine I like them. As a contemporary machine though they were way overpriced for what they were.
That would defeat the entire purpose of keeping that machine alive.
You are welcome to continue development on support for the 486 if you need continued support for it. The kernel is open source and you can easily clone yourself a local repo and continue 486 support maintenance while merging in new features as time goes on.
My very first linux box, which I still have and is still running today, is still on RedHat 3.0.3 that I got on a CD in a book from the Media Play in Poughkeepsie NY in 1996. Granted it is completely useless except as a samba server sharing the 1.6GB hard disk that is still in it (and still works). But, I keep it for posterity, and because I like having a monitor with xearth on it.
I could probably put a newer distribution on it but with only 24MB of RAM, the newer stuff would choke out on it.
Yeah well, we can't all be a person who doesn't understand how things work. Kudos to you for being simple minded!
" The Kathmandu Post"
Ah we don't to pay for journalism, says a planet of suckers
Oh, that's pretty neat. Microsoft is definitely the right level to address this at - they already have permission to enumerate the HW, own the hardware and software infra to tackle this, enjoy economy of scale other players are not privvy too, and can deliver a solution in a vendor agnostic way. Thanks for the heads up. It's the right thing to happen.
Of course there are. Tragedy of the commons. My point is that no single entity is likely to absorb the costs unless they're already enjoying economy of scale advantages and there are business experience/optic benefits to doing so. The poster above you pointed out that Microsoft seems to be addressing this, which makes a lot more sense to me than doing it at the 3d HW vendor level.
Sure, but many people would opt in, especially if you explained that they would benefit.
Maybe. Maybe not. Before committing to developing such a thing, you'd have to at least do some research and analysis to find out if that's true and how the likely opt in/out ratios would impact the business case. Remember, this is hosting content in a daemon on your machine
It can't be only when the game is open - this is when gamers are most sensitive to their computers doing other work, and the available of such a network would be far more limited.
Also a torrent like network would be absolute loaded with cache misses. You need to fetch a shader from somebody who has the exact same hardware/drive/game version combination as you do, and they need to have opted in. I highly suspect the majority case for many would be to cache miss and end up compiling locally.
Asking people to host and serve a non-trivial amount of content to other players is a non-starter. (The size of compiling all the shaders for CoD can range from a couple gigs to 10 gigs.) Opting in to a torrent-like network would have to be opt in - many people would just opt out (justifiably or not) minimizing the point of such a network.
You can probably assume that if you've thought of something, they've thought of it too. They simply have constraints and considerations - both technical and business oriented - you don't need or want to account for.
It's worth noting that many game studios/engines do support shared shader caches in their local studio pipelines, but the hardware config spread is much more limited, and the costs for lost productivity waiting for shaders is far greater than hosting a shader cache on premises.
Yes, this. There are many *many* combinations. Distributed compilation and a remotely hosted shader cache would cost a lot of money to host. I don't think it's the technical considerations that are as preventative as simply the cost of hosting the service.
Particularly for PvP competitive games that require constant FPS (think CoD, Battlefield, Fortnite, etc) runtime shader compilation is a nonstarter. CoD won't even let you matchmake without compiled shaders, even tho the engine supports compiling them on demand.
Information is the inverse of entropy.