scrubs

When fraud, theft occur and/or claims on insurance when fraud theft occurs a regulator must have a legal system to find facts, prove charges, make a judgement that can be enforced etc.. And that means, for one thing, anonymous users are an illusion. Identity to get accountability is required.

Absolutely agree. It's all awesome until it happens to oneself, then it gets real.

It's done its job? How tone deaf can you be?

Because of human nature fraud, theft, errors, disputes over assets etc. that go along with money whatever its form need to be properly dispositioned too. A block chain has no answer for that. And without dispute resolution methods the system will die or merely attract the underside or 1-off users of society.

Second, an automatic no to power is simplistic so as to distort solutions. Power is fine provided it's not corrupt and accountable. Getting that and keeping it is a hard problem, but there's no end-run either.

Finally, how many examples of frauds, thefts N must occur before crypto is associated with fraud, theft? That N was long ago surpassed.

Excuse me? The long history of success for nasa with and without the esa is staggering to the good.

I got more stories that jd salinger I (nasa) hold the title, and you're (spacex) just the challenger (paraphrase of beastie boy song shadrach et al)

More seriously, nasa has purposely focused on satellites and robots for scientific research on purpose for a multitude of reasons including cost.

I don't get the controversy over explicit allocators. C++ containers accept optional allocators since way back ... programmers making std like compatible containers have to deal with this aspect anyway.

I've spent quite a bit of time with zig after which I abandoned to rust despite starting with severe rust dislike. The switch was mainly due to:

- far better documented std lib. For example zig http stuff has bugs; and I could never find a public unzip inflate call despite the appearance of an impressive zig/unzip api.

- better library support esp for protocol. The zig stuff i found was few and had memory leaks.

- the fact struct fields are private by default (in zig all fields are public if you can get access to the struct). In complicated stuff the implementation has got to stay private

- the borrow checker was not a motivator, and rust compile times are nowhere annoying as I feared

- the zig i/o api i found too darn complicated and annoying

Things I still miss from zig:

- c/c++ ffi is solid. Gluing curl, zlib into zig was painless and worked day one. Rust takes more work.

- zig build and the ability to import a configuration as code is awesome.

- allocator story is good. It's darn simple to add custom allocators where performance matters

- Zig still has a couple of linker problems, or cross compliation bugs I immediately encountered when using it. One was fixed. One is still open.

Fawlty towers is one of the few 70s shows that still comes off well. Smartly written with great straight people (hotel custs) to play off, visual comedy (basil, manuel) with a fantastic mix of physical and spoken comedy.

There are many memorable lines. One I goto when I'm frustrated;

Basil: if he didn't order a cheese salad, poly, then why had he got one?

Poly: I ... I don't know

Basil: I know how he feels

So Basil is annoyed with the customer (who he thinks is a super uptight hotel inspector, but who only sells spoons) while sympathizing with him at the same time.

There are many more things to say, but it's worth pointing out how expertly it uses the British sense of manners to fake a lot of "misunderstandings." It's to politeness what Woody Allen does in Deconstructing Harry with guilt. It's both a formidable defense and weapon. If you haven't seen this movie, try it out. It's worth it. Plus you'll get to meet cookie who helps harry pull off his university speech.

I don't buy it. Data privacy is a customer concern that isn't going away nor will it be diminished.

Let's get a few things straight:

- I tell the supplier if I am satisfied with their service. They don't tell me.

- I decide if the cost in terms of time or dollars is worth it; they don't tell me nor may they infer I'm too stupid to know better.

- some customers are lazy or don't have a backbone. Suppliers can push them around. Btw - this happens a lot inside corporations where management explicitly or implicitly mandates internal suppliers. In some cases those internal suppliers lost bad because of their arrogance wit. migration to the cloud from on-prem. Ultimately tech+business knew they got a better tradeoffs elsewhere.

- the customer is right is not a straight jacket for suppliers; we are allowed to smartly exclude features we don't think we can compently do or are bad business.

The swarmy arrogance and laziness of the big three re: customer satisfaction cost them about 35% of the auto market in our own backyard to the Japanese they never really got back. Too many corporations are sliding into at times seeing customer feedback as a nuisance at their own peril.

Im a strong customer advocate. Know what your getting; hold the supplier to the line; be in charge of the relationship; never retreat from options.

I hate to agree the Chinese government is competent in foreign affairs, but it's true.

Fundamentally China isn't Russia or USA which both have a proclivity to become entangled in foreign problems. For the US (I'm american) the civil side has four strategic risks:

- weak to no show congress which has ceded war making to the executive branch

- civilian leadership who think bomb it and declare success which is naive

- the inability to stop being suckered in by our own hurbris when others say but we can't get it done without US involvement

- an economy post WWII built on cheap oil, which has tentacles into the mideast

Meanwhile after having pissed away 50 years of culture wars particularly since newt gingrich and the tea party, the US fiscal situation is deplorable.

Most maddening? We did this to ourselves. Blaming immigrants isn't the flex people think it is

When i read paragraphs of stuff about corporate culture from engineers --- thanks captain obvious for pointing out 180 employees isn't the same as 180,000 or that software has some of the same challenges in both environments --- I figure:

- this is sales and advertisement

- person has nothing serious going on

- can't be serious because people who care about company culture in a serious way are board members or senior managers at small companies not engineers giving anecdotes about what they think. Managers are accountable for decisions taken.

Their response attitude reminds me of basil from fawlty towers (paraphrasing):

I'm trying to run a business here. I can't get things done with you stupid customers bugging with me problems all the time. Go find something to do.

In the 80s and 90s customer satisfaction was important primarily in manufacturing. Today software treats customers like nyc realtors who know they have the balance of power:

that's too damn bad: the price is the price. Take it or i'll sell it to somebody else for wasting my time.

Well that's a long way of saying even in military offensive scenarios, Amazon is expected to have some zone up to use which is to say they're doing a decent job.

Contrast with no AZ now or in the next quarter. Then surely people would take precautions like switching to Google or equinix at a minimum.

A natural r&d project would be a high frequency oms or something like an nyse bid/ask/match book manager.

These apps tend to do kernel bypass anyway for net i/o after hard scrubbing the os to remove as many interrupts and other superfluous jitter the oms does not need.

However, I believe the low level kernel bypass code (eg dpdk, libfabric) depend on Linux to talk to the hw in a disciplined way.

Anybody know better?

A decently faster oms this way could be a practical alternative to fpgas we sometimes see in that space. (hw would be co-located of course)

Sad indeed. But very true though!

I've abandoned zig for rust. I expected to be annoyed by rust build times, but so far it's been quite good for my needs. To the contrary it has not been any impediment even when prost etc all drag in many deps from a cold build.

The zig compiler apart from a couple of cross build or linker issues is darn good. Switch to rust is a function of library support, private struct fields. Rust itself is better organized and far better documented compared to zig.

However, rust has got to get their allocators for container support straightened out soon. I do SAAS for fintech and low level packet transports. Both benefit greatly with allocators custom designed for job at hand.

45 mins strikes me as something else is amiss ...