Where can I have a discussion with other developers about storage?
Is here okay?
I want to have physical storage over here, and logical storage over there, and I want to control the mapping from one to the other. I want to talk about encryption, replication, latency. Make "time machine" available on this logical storage. And then I buy some new physical storage, and it joins the story. This physical storage is over at my friend's house for backup. This physical storage is slow and archival. This is a device for writing archival media, and there's a brand new media in it, go ahead and write to it. Show me the health report on all of the physical media, and show me what you've done to protect the logical storage. Graph my usage and make suggestions about when to add more physical storage.
Buying physical storage with power and wifi, and configuring it with a QR code that's on an e-ink display - seems like it should be the most obvious thing in the world, that we should all be really used to doing by now.
My experience has always been that the more you're trying to do, the messier the codebase is.
But that to clean up a codebase requires even more people.
So, at first blush, it looks like "more people = more problems," but if you actually give yourself some breathing room, the code can get cleaner with effort.
Right, this is where I'm at, in trying to 'strong-man' it. CT is great as a source and a detector, but when you add multiple detectors and can use scattering to your advantage, we're able to lower rad dosage for comparable images. So, yeah, what if each receiver is able to handle the ultrasound scattering better than we thought.
That's the only way this thing adds up in my head.
I tried to give that section of the doc a fair read.
Looks like operational transforms to me.
The doc claims it's the first with this technique. A 30 second search reminded me of Darcs, and taught me about Pijul, and Weave. And yes, Google Docs storage works the same way - there are probably papers documenting how efficient Google Docs storage is, but it's not wrapped up in a full VCS that folks can use.
The example in the doc uses text, and unfortunately I think it's for a reason. I think with large, binary game assets, the most common operation is going to be strings of "replace A with B", and depending on your chunk size relative to the distribution of changes you make on your assets, I see it as pretty close to a wash, for efficiency. Especially considering that content-addressable blocks also solves de-duplication, which for a multi-game studio is probably going to be significant. Especially if they're managing multiple releases, patches, development branches, etc.
I feel like, everyone near Git has decided, "Well, all abstractions leak - so we might as well stand in the rain like Andy Dufresne when he escaped from Shawshank Prison!"
I did laugh at how the Gravity built the Earth, with a tiny North America and all, and then as more mass was accumulated, North America got to get bigger and bigger and bigger!
The thought I've toyed with was forcing public companies in some industries to issue some percentage of stocks to the government... And then using incentives to get them to pay dividends.
I think someone has to be fairly elite to have a secondary, or tertiary home, in NY City, worth over $1 million.
Regardless, the entire point of this discussion is that people who have a secondary home can probably afford to pay more in taxes than other people can. I don't call that envy.
That's just a frank discussion of tax policy.
If you think taxes should be lower, because some government programs should be reduced, that's a perfectly fine discussion to have.
If you think governments shouldn't have to worry about a balanced budget, and maybe they should default on their debt (which is an argument the current President has insanely floated), that's a fine discussion to have.
At present, we're talking about secondary homes with a value over $1 million, in New York City, having an additional 4% tax.
And I was lamenting that home valuations appear to be unbelievably low, which would dramatically reduce the tax income of this law, and I was trying to propose a fix, for those homes.
If you think the only reason to have that discussion is because of envy, then I think you're not being fair to other people's motivations.