OtterCoder

How is it any different in any way than any other async function? You just end up providing an unusually large number of parameters via headers and body, then at some point in the future the request completes with values and/or errors. What separates them?

Oh good. Surrendering the entire mythos of the English speaking world to a single, domineering company opposed to freedom of speech and information is totally worth a cleaner copy of Star Wars.

I've always held that the extremes of corporate power look a lot more like feudalism than anything else.

The main difference being that corporations divide up the different experiences of life, where fiefdoms divided the land. In the end we have absolute rulers in their own private domains who only have to pay a small tribute and lip service to the nation they are nominally aligned with.

It's possible. This bubble reminds me of the South Sea Company bubble. Whatever utility Bitcoin has is being massively dwarfed by the price speculation.

He is, but the rest of his former co-workers aren't, nor his replacement.

This article doesn't even touch the worst problem with SO. Code rot.

Answers are typically out of date and no longer good practice. Some claim that the ability to edit answers fixes this, but all it does is subvert the accept/vote functions. You end up with strange "Ship of Theseus" answers where what is written has nothing to do with what was so highly voted, or what solved the original problem.

Where SO goes wrong is that they have tried to create a definitive set of answers in a field where the real answers change yearly, or even monthly.

This sounds like a good starting solution for our team. Thanks!

The distinction is only artificial because we are in early stages of development. Our MVP will require a web client and an intermittently offline mobile client.

It is helpful, but certainly doesn't sound simple. Feature switches would require the messages to already be designed, which is most of the work already done. It also sounds like an edge-case nightmare.

I'm working on CD for a project I've been working on, but one difficulty I'm facing is that the clients and server are being developed on parallel tracks, and aren't always in feature parity at any given moment.

Which repo should own the integration tests? How do I synchronize the releases of matching front and back ends?

That's a very easily refutable claim.

I hate this model. I'm old fashioned, in that anything I rely on day to day, I want to own. My tools, my games, my pots and pans. Every service license you agree to adds another layer of external control to your life.

That is an incredibly difficult title to parse if you are from a certain background. I spent about a minute trying to imagine how someone might have made a human/cow chimera, and what that might have to do with harmonics.

In my defense, I had read the following article about rat/human chimeras earlier today:

https://www.thesun.co.uk/tech/4867891/scientists-give-rats-c...

So, it's lag, basically?

Yep. I'm a programmer. I can use any number of buzzy labels to describe my skill set, and I'll cheer for Rust all day, but I'm just a programmer.

Wait, what? I really want to see some links or papers about that. Care to share?

Even optimization for "good" is problematic. I'm fairly sure that you and I would have a long and loud argument over what "good" means if we really got down to brass tacks.

Trust, in the business sense of the word.

https://en.m.wikipedia.org/wiki/Trust_(business)

In the days of Rockefeller, these things were a little more formal. Nowadays companies know better than to put such silent agreements in writing.

Senator Lee, who happens to be on the Antitrust Subcommittee.

This is brilliant. I recently wrote in to my senator about net neutrality. His reply was a breathtakingly convoluted justification of not regulating companies like Comcast because antitrust laws would take care of it. I've never felt so insulted.

I used to work for a publishing company. No other platform or vendor made us bend over backwards like Amazon. We had to give them the usual non-competitive list pricing that other vendors demand, but we also had to give them a massive, absolutely disproportional cut of the sale price, regardless of profit margin. There were launch date rights they demanded, massive periods of exclusivity for audiobooks in order not to be a second class citizen, total refusal to negotiate terms, etc.

We were not a small publishing house, top 10% by volume nationwide, and (mostly) not paperback trash either. You've probably seen our cookbooks. Didn't matter. They treated us exactly the same as they would an amateur author writing unedited self-pub romance novels. No regard for quality, rating, volume, or any other metric, all must bow before Bezos. Amazon takes such a chunk out of the publishing industry, it actually has a bit of a chilling effect, because you can't afford risk a flop with the tight margins Amazon affords, and you probably need Amazon.

Then you haven't been an Amazon supplier dangling at the end of a rope as Bezos tries to wring blood from a stone.

[spoiler]

Eventually you end up in a self-replication phase. Replicas are sometimes imperfect, so you have to defend yourself from rogue-rogue AIs.

[/spoiler]

I've beaten this. It's a silly, insightful, weird, and repetitive cautionary tale. Without spoiling too much, the ending leaves you with a terrible sense of emptiness, but is still quite satisfying.

Idle games are usually not optimized for performance. It's running bigint style operations in a tight loop. Mobile phones are not what you should be playing these games on.

Sorry, I mean that ad revenue is only valid if it has a sufficient payout per visitor. Both crypto currency and ad revenue tend to be a race to the bottom.

I'd rather a site wasted my electricity than my time.

That's true of advertisement as well.

People don't care if their frontier is safe. The human drive to explore and stake out new lands has always been much stronger than their need for safety.

Delivery. A cloud provides worldwide availability at the cost of trust. A distributed site can survive any one entity failing, which includes you, and it can serve from anywhere your users want it to.

An amazingly effective model, if unglamorous.