magnawave

The best I can tell from talking with insiders at a couple of his properties, is that he did a beyond bad job at “succession planning”. The light exception being MoPOP of course but that’s a different beast. So without setting up foundations/entities to fund/run your projects and getting people aligned before you pass, odds are your estate won’t.

So want to blame the family. But really Paul Allen’s fault here.

It’s a shame, was such a great museum.

AFCI's feel like NEC's attempt to create tons of service calls under the guise of "safety". And eventually seems like they will be required for new builds everywhere as areas adopt the newer codes that require them slathered everywhere.

Of course its "for safety" but of course these breakers are famous for false tripping and causing expensive service calls.

anecdote: In my case, small server rack, on circuit a with an AFCI - since "bedroom". No problem.

Until washing machine on circuit b (no AFCI) runs, then trips circuit a's AFCI. Repeatedly, every time(debug on the breaker a returns ArcFault detection reason too). So... either a) don't wash your clothes b) don't have tech or c) quietly violate the code.

Indeed electrician quietly suggested(after a bunch of triage) I swap out the breaker with a normal one. But of course he wasn't allowed to do that... lol

Been here a decade - nary an issue since - so clearly the usual case of nuisance tripping and nothing more.

I suspect the switching power supplies were close to annoying the ACFI, and a beefy motor on an adjacent circuit was enough to push it over the line. Incidentally, swapped UPSes, power supplies(quality Seasonic), etc and nothing improved.

I guess the wildcard is price.

AWS's pricing model works kinda at their OMG eyewatering scale - aka all the custom hardware they design is highly cost optimized, but just doing custom hardware has a notable cost. This is easily covered by their scale, to make for their famous margins. [during their low scale times, they did use a good bit of HP/Dell, etc]

Oxide seems to be no different (super custom hardware) only major difference being the "in your datacenter" part. Since you own the cost of your datacenter, Oxide has to come in a lot cheaper to even compete with AWS, but how do you do that with low volume [and from the look of it not-cost optimized, but instead fairly tank-like] bespoke hardware? Feels like the pricing / customer fundamentals are going to be pretty rough here outside perhaps a few verticals.

Oh this is awesome. When I was a kid I really really attempted to write a Keen knock off (doctor who themed) on my 386 and it was ok although never really did enough level development to make it super playable. But TO THIS DAY, never knew how the heck they made it scroll so smoothly. I just ended up just jump scrolling. Figured it was some mad assembler skills, never imagined there was a hw register!

Did figure out the double buffering stuff on my own though ;)

Seems so obvious, learn something new everyday, even if it would have been more useful, say maybe ~30yrs ago ;)

…and sadly the doctors have been fleeing too, all my doctors have left. Their replacements aren’t bad, but not to the same top notch level of care. The Polyclinic was honestly off the charts excellent, and now it’s just “fine”. In a few more years who knows. The alternatives are unfortunately not better.

Indeed doing what they have done is impressive, and talented folks at play for sure. Not sure, even vaguely commercially viable(heck 0xide as a whole), but nerdy interesting for sure. But I can’t see practically why this is so much more useful than what society has built together and call the x86 platform over the last few decades.

One of the hard parts of quantifying that, is you have people who wear many hats. So sure you have Cassandra gurus, and probably a decent number of them. But this is in the league where really hardcore automation kicks in to keep staffing sane, and operations possible. But outside that, how do you count datacenter folks, client folks, networking folks, etc who only spend a little fraction of time on the database parts.

But I think I can say with sufficient knowledge, all things considered still, “way fewer than you might think”.

Correct, that’s what object stores are for. However, metadata on said files, is probably very handy to have in a database.

I’m quite sure not all this Cassandra capacity is just file/photo metadata storage either.

Thought the exact thing the first time I saw one in a Chicago full service parking garage. And they had very stern signs about being for employees only. So ya that’s likely how they solve the liability problem. But man they looked really cool. So wanted to try it out ;)

It’s definitely comically expensive. But I’ve had mine 15 years and it’s still the best least fuss humidifier I’ve ever owned. Oh and I never use their additive. Little dish soap (drop of two) in each refilling keep the water “sticking” to the disks nicely, nothing else to replace. Never had a mold problem with them either.

The declarative functionality comes from K8s not helm. (Of course K8s has imperative tooling too but that’s not the point here).

The main reason folks dislike helm are 2 fold: 1) using string templating on a space formatted language is just messy and ugly for no good reason. If you don’t do anything terribly complicated it’s not too bad but quickly can be pretty fragile and unreadable. 2) golang(which I like generally) but the templating is messy and adds to the hard to read later problem

Personally find helm’s opportunity for code reuse to be restrictive and folks just end up cut and pasting a lot of declarations all over which is ... so terrible. But the first bullet above is pretty a fundamental design flaw.

I think his point was about drives silently returning corrupt data, not that you shouldn’t have redundancy. Absolutely you should have redundancy and backups.

At the (tens of) thousands of drives scale (and where you treat drives as cattle) having some extra checks and balances for what you write is an excellent idea. Even better is doing that in a distributed way so multiple machines make that same decision. Occasionally you will run into a drive where the firmware has jumped the shark or some such. (Or CPUs or memory or bus issue for that matter).

But generally speaking drives DO know when they are returning bad data and will error before they will do that. The odds are about as good as other forms of hardware errors that will eat your data.

Not anymore. From what I’ve been told from an insider, the latest versions are derived from a common code base now, with platform specific bits separate for each platform.

The latest office for Mac looks quite a bit like the windows version now (for once) so it’s not too surprising.