A google account is not required to use an Android device.

So if you don't tie all your contacts, sync and backup to your google account, you can have a phone that they won't lock you out of.

Snaps are yet again at the center of the problem. It's been more than 10 years and they still cause issues, are generally hated by the community and a PR disaster.

Ulid have a short representation that uuid7 could use but doesn't define. Also, has UUID7 been standardized already? I thought it was still in the pipeline.

Statistically, being successful on accident with paypal, tesla, starlink and space x each individually is pretty improbable given the complexity of each.

All of them? That's doesn't seem rational.

Musk is a visionary, no question. Driven? Absolutely.

I feel however, that many of his successes including most you mention are in spite of him rather than because of him. I respect that you might feel differently.

Employees always say it's management, management always say it's employees.

But in most companies, it's both.

And people suck at discipline.

Hopefully their country doesn't outlow watching porn itself, because in that case they are just accumulating evidences against them.

Nassim Taleb was right again.

I have dumb phone for that. If they pressure me to install something on it, I just bring them that phone (with my real sim), and ask them how we shall proceed.

You don't offer alternatives. Either a product or service is valuable enought to get customers, or it's not and it dies.

It will actually benefit small structures that have no money for marketting anyway.

And big ones won't be able to rely on their treasure chest to generate more of it, they will have to earn it.

Yep, also GraphQL and all those data lakes.

That reminds me "XML is the future": https://www.bitecode.dev/p/hype-cycles

Data lakes are still the standard in the industry.

And that won't change so long as object stores like S3 are so much cheaper.

And what exactly is wrong with GraphQL ? It is better than REST for a number of use cases.

> And what exactly is wrong with GraphQL ? It is better than REST for a number of use cases.

When a response is a representation of a single resource, that response has a definitive caching lifetime. When a response represents a synthesis of a bunch of random crap the user asked for, the response has no clear caching lifetime, and so is uncacheable.

Most of the scalability the web has achieved, rides on the back of response caching at one level or another. Even low-level business-backend vendor APIs can—and are often designed under the assumption and requirement of—being cached. GraphQL throws that property away.

GraphQL seems like a great idea if you're a massive social media company looking for ways to empower devs to stamp out flavor of the week social media widgets without being tied to existing APIs. I'd bet most companies doing GraphQL are just doing uncacheable things that REST APIs could do fine.

Almost all graphQL clients implement a custom caching layer (for example using indexeddb in the browser) that can cache resources with different timelines, also when they’re returned in a single response.

Yeah, but that's client-side caching, which doesn't get you much in terms of scalability. Scalability comes from transparent backend reverse-proxy caching — Varnish and the like. You can cache the resources that go into a GraphQL response, but you still have to build the GraphQL response each time — and that can become a problem, as various should-be-trivial parts of each request's backend lifecycle start living long enough during high concurrency request loads to destroy request-queue clearance rates.

Yes in the same way micro services are a standard in the industry.

What's wrong with graphql is what's wrong with k8: people use it in the wrong context, and the right context is not most projects.

The future was better, but also worse: JSON.